Well, the question is a little vague, and a tad misleading first off I'm not really sure what CIDR notation has to do with continuous deployments in this context. So I will assume it's asking for both. CIDR is a notation used to express a variety of network conditions, using convenient slash notation. A class A/B/C would be represented with either 10.x.x.x./8 - a , 172.168.x.x/16, or 192.168.1.x/24. You can set a range of IPs or Network Ranges using slash notation to split networks even further, so you could sub-class a C subnet into a small subset, i.e. 192.168.1.3/32 would denote a single address, The conversion - Subtracting the number of network bits from 32. Raise 2 to that power and subtract 2 for the network and broadcast addresses. For example, a /24 network has 232-24 - 2 addresses available for host assignment. CI/CD is Continuous Integration and Delivery - simply put this is how the code lifecycle follows thru from maturity. It starts in the repo, and it gets run through a gauntlet through something like Jenkins, Travis or CircleCI. Until it's finally merged and committed for deployment. This can refer to any component before the delivery, and up to the deployment of the product.