Design an address plan that survives a merger

short · 35 min · Objective 1.3

Task

Choose an address range for three environments in two regions, plus room for a partner network you may one day have to peer with. The constraint that makes this hard is the one from the lesson: overlapping ranges cannot be peered, and the decision is effectively permanent.

Steps

  1. In lab/addressing.md, allocate a range for production, staging and development, in two regions each -- six virtual networks. State the CIDR for each and the number of usable addresses.
  2. Inside the production network, carve public and private subnets across three availability zones. Remember the provider reserves several addresses per subnet and show the usable count AFTER that reservation.
  3. Deliberately avoid 10.0.0.0/16, and write the sentence explaining why the most popular default is the worst choice for a network you may need to peer.
  4. Reserve a range for a future partner or acquisition, and state what you would do if their network overlapped yours anyway.
  5. Calculate how many more instances each production subnet can hold before address exhaustion, and note that this is the number to monitor.

Verify

grep -Ec '/(1[6-9]|2[0-8])' lab/addressing.md
grep -Eci 'reserv' lab/addressing.md
grep -c '10\.0\.0\.0/16' lab/addressing.md

The last count should be 1 -- the single line explaining why you avoided it. More than one suggests you used it anyway.

This is an independent study companion for CompTIA Cloud+ CV0-004 and is not produced by or endorsed by CompTIA.