Bitzu

SAA-C03 ยท High-performing networks and edge

VPC addressing and subnet tiers

Sizing VPC and subnet CIDR blocks, reserved addresses per subnet, avoiding overlapping ranges for future peering, IPv6 and multi-tier subnet layouts across AZs.

Key points

  • VPC IPv4 CIDR: /16 (65,536) to /28 (16); subnets same range, no overlap.
  • Use RFC 1918 (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16); never overlap VPCs, accounts or on-premises (peering, Direct Connect).
  • 5 reserved per subnet: network, .1 router, .2 DNS, .3 future, broadcast; /24 = 251 usable.
  • Cannot resize a CIDR; add secondary blocks.
  • IPv6: e.g. Amazon /56 per VPC, /64 per subnet.

Source: https://docs.aws.amazon.com/vpc/latest/userguide/subnet-sizing.html

Practice questions

Single choice

What is the allowed size range for an IPv4 CIDR block of a VPC?

  1. From /8 to /24
  2. From /16 to /28
  3. From /16 to /30
  4. From /20 to /32
Show answer

Answer: B. From /16 to /28

A VPC IPv4 block must be between /16 (65,536 addresses) and /28 (16 addresses). A /8 is too large, and /30 or /32 blocks are below the smallest allowed size.

Select all that apply

Which practices help keep a VPC address plan ready for future peering and hybrid connectivity?

  1. Give every VPC and environment its own non-overlapping RFC 1918 range
  2. Use 10.0.0.0/16 in every account so the setup is identical
  3. Keep VPC ranges clear of the on-premises address space
  4. Leave unallocated space in the VPC for future subnets
  5. Always choose a /28 VPC to conserve addresses
Show answer

Answer: A. Give every VPC and environment its own non-overlapping RFC 1918 range, C. Keep VPC ranges clear of the on-premises address space, D. Leave unallocated space in the VPC for future subnets

Allocating unique RFC 1918 ranges per VPC and per environment, and keeping them clear of on-premises ranges, avoids overlaps that would block peering or a Direct Connect gateway. Leaving room in the VPC lets you add tiers or AZs later. Reusing 10.0.0.0/16 everywhere creates exactly the overlap to avoid, and the smallest possible block leaves no room to grow.

True or false

If a VPC runs out of addresses, you can enlarge its existing primary CIDR block, for example from /24 to /20.

Show answer

Answer: False

False. You cannot increase or decrease the size of an existing CIDR block. Instead you associate a secondary IPv4 CIDR block with the VPC and create new subnets in it.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More SAA-C03 topics in this module