Private IPv4 Addressing and RFC 1918

24 questions

Question 1Question

A network administrator is assigning an IPv4 address to an enterprise border router interface connected directly to an Internet Service Provider (ISP) WAN link. The interface must communicate on the public Internet without employing Network Address Translation (NAT). Which of the following IPv4 addresses is globally routable over the Internet according to RFC 1918 specifications?

Show answer & explanation

Answer: 172.32.50.1

Answer

172.32.50.1 is a globally routable public address because it lies outside the RFC 1918 private address boundaries.
RFC 1918 defines three private IPv4 address ranges that are not routed on the public Internet: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. The Class B range covers 172.16.0.0 through 172.31.255.255. The IP address 172.32.50.1 falls outside this range, making it a valid public IPv4 address suitable for Internet communication without NAT.

Step-by-Step Solution

1
Recall the RFC 1918 private IPv4 address allocations.
Class A: 10.0.0.0/8 (10.0.0.0 to 10.255.255.255); Class B: 172.16.0.0/12 (172.16.0.0 to 172.31.255.255); Class C: 192.168.0.0/16 (192.168.0.0 to 192.168.255.255).
Identify which IP ranges are reserved for internal/private use and unroutable on the public Internet.
2
Evaluate each candidate IPv4 address against the RFC 1918 boundaries.
10.254.10.1 is in 10.0.0.0/8 (private). 192.168.250.1 is in 192.168.0.0/16 (private). 172.31.200.1 is in 172.16.0.0/12 (private). 172.32.50.1 is outside 172.16.0.0/12 (public).
The Class B private block ends at 172.31.255.255. Addresses starting at 172.32.0.0 are public IP addresses.
3
Select the address suitable for WAN interface routing without NAT.
172.32.50.1 is public and globally routable.
ISPs drop RFC 1918 private addresses at edge boundaries, so only public IP addresses can communicate over the global Internet without NAT.

Key Concept

RFC 1918 Private Address Ranges and Public Routability
Question 2Question

A network administrator is auditing enterprise IP addressing schemas across multiple branch office subnets to ensure full compliance with RFC 1918 private addressing standards. During the audit, the administrator observes four host interface configurations:

- Device A: 10.255.250.1/810.255.250.1/8
- Device B: 172.31.255.1/12172.31.255.1/12
- Device C: 172.32.10.1/16172.32.10.1/16
- Device D: 192.168.255.1/16192.168.255.1/16

Which host is configured with a globally routable public IPv4 address rather than a valid RFC 1918 private IPv4 address?

Show answer & explanation

Answer: Device C (172.32.10.1/16172.32.10.1/16)

Answer

Device C (172.32.10.1/16172.32.10.1/16) is configured with a public IPv4 address because RFC 1918 defines the Class B private IPv4 allocation strictly as 172.16.0.0172.16.0.0 to 172.31.255.255172.31.255.255 (172.16.0.0/12172.16.0.0/12).
The RFC 1918 standard reserves three specific IPv4 address blocks for private internal network use: 10.0.0.0/810.0.0.0/8 (10.0.0.010.0.0.010.255.255.25510.255.255.255), 172.16.0.0/12172.16.0.0/12 (172.16.0.0172.16.0.0172.31.255.255172.31.255.255), and 192.168.0.0/16192.168.0.0/16 (192.168.0.0192.168.0.0192.168.255.255192.168.255.255). The address assigned to Device C (172.32.10.1/16172.32.10.1/16) falls outside the 172.16.0.0/12172.16.0.0/12 boundary because its second octet (3232) is greater than 3131. Therefore, it is a globally routable public address.

Step-by-Step Solution

1
Identify the three defined RFC 1918 private IPv4 address blocks and their prefix boundaries.
Class A: 10.0.0.0/810.0.0.0/8 (10.0.0.010.0.0.010.255.255.25510.255.255.255); Class B: 172.16.0.0/12172.16.0.0/12 (172.16.0.0172.16.0.0172.31.255.255172.31.255.255); Class C: 192.168.0.0/16192.168.0.0/16 (192.168.0.0192.168.0.0192.168.255.255192.168.255.255).
RFC 1918 reserves specific IPv4 address ranges exclusively for private enterprise networks.
2
Evaluate each given IP address against the defined RFC 1918 boundaries.
10.255.250.110.255.250.1 is within 10.0.0.0/810.0.0.0/8; 172.31.255.1172.31.255.1 is within 172.16.0.0/12172.16.0.0/12; 192.168.255.1192.168.255.1 is within 192.168.0.0/16192.168.0.0/16; 172.32.10.1172.32.10.1 exceeds the upper limit (172.31.255.255172.31.255.255) of the Class B range.
Addresses beyond 172.31.255.255172.31.255.255, such as 172.32.0.0/11172.32.0.0/11, are allocated as public IP space by IANA.
3
Determine which device uses a public, globally routable IPv4 address.
Device C (172.32.10.1/16172.32.10.1/16) uses a public address.
Because 172.32.10.1172.32.10.1 is outside the RFC 1918 private boundary, it requires direct public Internet routing or dynamic translation.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Question 3Question

A network architect is establishing standard address allocations and boundary checks for an enterprise network redesign. Match each IPv4 address block or prefix range on the left with its corresponding RFC 1918 classification, CIDR specifications, or Internet routing characteristics on the right.

Click a left item, then click its matching right item

Items

10.0.0.0/810.0.0.0/8
172.16.0.0/12172.16.0.0/12
192.168.0.0/16192.168.0.0/16
172.32.0.0/11172.32.0.0/11

Matches

Show answer & explanation

Answer

10.0.0.0/8 matches the single Class A private block (10.0.0.0 to 10.255.255.255); 172.16.0.0/12 matches the 16 contiguous Class B private subnets (172.16.0.0 to 172.31.255.255); 192.168.0.0/16 matches the 256 contiguous Class C private subnets (192.168.0.0 to 192.168.255.255); 172.32.0.0/11 matches the globally routable public address space.
Each item matches its corresponding RFC 1918 definition or boundary specification correctly: 10.0.0.0/8 is the single Class A private block, 172.16.0.0/12 spans 16 contiguous Class B private /16 networks (172.16.0.0 - 172.31.255.255), 192.168.0.0/16 spans 256 Class C /24 networks (192.168.0.0 - 192.168.255.255), and 172.32.0.0/11 consists of public addresses immediately above the 172.31.255.255 RFC 1918 upper bound.

Step-by-Step Solution

1
Identify the Class A RFC 1918 block
10.0.0.0/810.0.0.0/8 encompasses the host range 10.0.0.010.0.0.0 to 10.255.255.25510.255.255.255 (16,777,21616,777,216 addresses).
RFC 1918 reserves one /8/8 prefix in the 10.0.0.0 network space for private internal use.
2
Analyze the Class B RFC 1918 block and boundary limits
172.16.0.0/12172.16.0.0/12 encompasses 16 contiguous /16/16 blocks (172.16.0.0172.16.0.0 through 172.31.255.255172.31.255.255).
The prefix length /12/12 spans from 172.16.0.0172.16.0.0 up to 172.31.255.255172.31.255.255. Addresses starting with 172.32.0.0172.32.0.0 are public.
3
Identify the Class C RFC 1918 block
192.168.0.0/16192.168.0.0/16 encompasses 256 contiguous /24/24 subnets (192.168.0.0192.168.0.0 through 192.168.255.255192.168.255.255).
RFC 1918 defines a single /16/16 prefix block within the 192.168.0.0 space for Class C private addressing.
4
Distinguish public ranges from RFC 1918 private ranges
172.32.0.0/11172.32.0.0/11 starts at 172.32.0.0172.32.0.0, which is beyond the 172.31.255.255172.31.255.255 boundary and is therefore public.
Any IP address in the range 172.32.0.0172.32.0.0 to 172.63.255.255172.63.255.255 is public and routable on the global Internet.

Key Concept

RFC 1918 Private IPv4 Address Space Ranges and Public Boundaries
Estimated Time:2m 0s
Question 4Question

A network engineer is configuring interface IP addresses on a core layer switch for an internal corporate segment. Company policy strictly dictates that all internal devices must use RFC 1918 private IPv4 addresses and that addresses must be usable host assignments. Which of the following IP address and subnet mask combinations represents a valid, usable host address located strictly within the upper boundary limit of the RFC 1918 Class B private address space?

Show answer & explanation

Answer: 172.31.255.254 255.240.0.0

Answer

The address 172.31.255.254 with subnet mask 255.240.0.0 is the correct choice as it represents the highest usable host address within the RFC 1918 Class B private range.
The correct answer specifies 172.31.255.254 with mask 255.240.0.0 (/12). RFC 1918 reserves 172.16.0.0 to 172.31.255.255 for Class B private networking. In the 172.16.0.0/12 block, 172.31.255.255 is the broadcast address, making 172.31.255.254 the highest usable host address within the private Class B scope.

Step-by-Step Solution

1
Identify the exact RFC 1918 Class B private IPv4 address range boundaries.
RFC 1918 defines the Class B private address space as 172.16.0.0/12172.16.0.0/12, which encompasses IP addresses from 172.16.0.0172.16.0.0 through 172.31.255.255172.31.255.255.
Understanding exact RFC 1918 boundaries is required to filter out public IP addresses.
2
Evaluate candidate addresses against the upper boundary (172.31.255.255172.31.255.255).
172.32.0.1172.32.0.1 exceeds the upper limit and is public. 172.15.255.254172.15.255.254 is below the lower limit (172.16.0.0172.16.0.0) and is public. Both 172.31.255.254172.31.255.254 and 172.31.255.255172.31.255.255 fall inside the private range.
Only addresses between 172.16.0.0172.16.0.0 and 172.31.255.255172.31.255.255 comply with the RFC 1918 private addressing requirement.
3
Determine host address usability for the remaining compliant addresses.
For the network block, 172.31.255.255172.31.255.255 acts as a broadcast address and is unusable for host assignment. 172.31.255.254172.31.255.254 is the last valid, assignable host address in the block.
Host IP assignments must exclude the network ID and broadcast address of the given subnet.

Key Concept

RFC 1918 Private IPv4 Address Space Boundaries and Usable Host Restrictions
Question 5Question

An enterprise network engineer is auditing the IPv4 addressing scheme across several newly acquired branch office routers. Corporate security policy strictly mandates that all internal host interfaces must be configured within RFC 1918 private IPv4 address space to prevent internal routing leakage over the public Internet. During the audit, the engineer inspects four interface IP configurations. Which of the following IPv4 address and subnet mask assignments represents a public IPv4 host address that violates RFC 1918 guidelines?

Show answer & explanation

Answer: 172.32.14.50/20

Answer

The address 172.32.14.50/20 is a public IPv4 address because it falls outside the RFC 1918 private Class B prefix range of 172.16.0.0/12.
The RFC 1918 Class B private address space spans from 172.16.0.0 to 172.31.255.255 (CIDR prefix 172.16.0.0/12). The address 172.32.14.50 has a second octet of 32, placing it outside the private address block and into public IPv4 space.

Step-by-Step Solution

1
Recall the defined RFC 1918 private IPv4 address blocks
Class A: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), Class B: 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), Class C: 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).
Identifying private space requires strict matching against the starting and ending boundaries of RFC 1918 blocks.
2
Evaluate the second octet of the Class B candidate addresses
The address 172.31.240.100 has a second octet of 31, which is inside the range 16–31. The address 172.32.14.50 has a second octet of 32, which is outside the range 16–31.
The /12 prefix for Class B private space covers second octet values from 16 to 31 inclusive (172.16.0.0172.31.255.255172.16.0.0 - 172.31.255.255).
3
Determine which address violates RFC 1918 private designation
172.32.14.50 is public and cannot be routed across private networks without public IP ownership.
Addresses starting with 172.32.x.x are allocated globally by IANA as public IP addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Estimated Time:1m 30s
Question 6Question

A network technician is configuring an isolated staging environment and must assign a dedicated IPv4 subnet using unroutable addresses specified in RFC 1918. Which of the following network prefixes represents a valid private IPv4 address block according to RFC 1918?

Show answer & explanation

Answer: 172.25.0.0/16

Answer

172.25.0.0/16 is the valid RFC 1918 private IPv4 network prefix.
The prefix 172.25.0.0/16 lies within the 172.16.0.0/12 block reserved by RFC 1918 for private IPv4 networks (spanning from 172.16.0.0 to 172.31.255.255).

Step-by-Step Solution

1
Recall the defined RFC 1918 private IPv4 address ranges
Class A: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), Class B: 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), Class C: 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).
RFC 1918 explicitly reserves these three specific IP address blocks for private internal networks.
2
Evaluate the candidate prefixes against the RFC 1918 boundaries
The prefix 172.25.0.0/16 is inside the Class B range of 172.16.0.0 to 172.31.255.255. All other options fall outside the private boundaries (172.33.0.0/16, 192.169.1.0/24, and 11.0.0.0/8 are all public IPv4 ranges).
Addresses outside the three defined blocks are globally routable public addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Question 7Question

A network security analyst is auditing border firewall traffic logs to ensure no unroutable internal addresses are leaked to the public Internet. Corporate security policy requires Network Address Translation (NAT) for all internal devices accessing public web services.

Which TWO IPv4 addresses identified in the firewall log belong to the RFC 1918 private address space and require source NAT before being routed across the public Internet? (Select two.)

Select all that apply

Show answer & explanation

Answer: 10.254.1.5; 172.30.100.45

Answer

The addresses 10.254.1.5 and 172.30.100.45 are RFC 1918 private IPv4 addresses that require Network Address Translation to be routed over the public Internet.
RFC 1918 defines three private IPv4 address blocks that are not routable across the public Internet: 10.0.0.0/8, 172.16.0.0/12 (172.16.0.0 through 172.31.255.255), and 192.168.0.0/16. The address 10.254.1.5 falls inside the 10.0.0.0/8 Class A block, and 172.30.100.45 falls inside the 172.16.0.0/12 Class B block. Both require source NAT to communicate over public networks.

Step-by-Step Solution

1
Identify the standard RFC 1918 private IPv4 address blocks.
Class A: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255)
Class B: 172.16.0.0/12 (172.16.0.0 – 172.31.255.255)
Class C: 192.168.0.0/16 (192.168.0.0 – 192.168.255.255)
RFC 1918 designates these exact prefixes for private enterprise networks and dictates that they are non-routable on the public Internet.
2
Evaluate each address option against the private IPv4 boundary definitions.
10.254.1.5 resides within 10.0.0.0/8.
172.30.100.45 resides within 172.16.0.0/12.
172.32.50.10 is outside 172.16.0.0/12.
192.169.10.1 is outside 192.168.0.0/16.
Addresses starting with 172.32 and 192.169 belong to public IPv4 address space assigned to internet registries.

Key Concept

RFC 1918 Private IPv4 Addressing Ranges
Estimated Time:1m 15s
Question 8Question

A network administrator is documenting the RFC 1918 private IPv4 address space allocation for an enterprise network redesign. Match each RFC 1918 address block on the left with its corresponding CIDR prefix length and block composition description on the right.

Click a left item, then click its matching right item

Items

10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255

Matches

Show answer & explanation

Answer

10.0.0.0 – 10.255.255.255 matches '/8 prefix length comprising 1 Class A network block'; 172.16.0.0 – 172.31.255.255 matches '/12 prefix length comprising 16 contiguous Class B network blocks'; 192.168.0.0 – 192.168.255.255 matches '/16 prefix length comprising 256 contiguous Class C network blocks'.
Each RFC 1918 private IPv4 block aligns with a specific CIDR prefix and quantity of traditional classful networks: 10.0.0.0/8 represents one Class A block; 172.16.0.0/12 represents 16 contiguous Class B blocks (172.16.0.0 to 172.31.255.255); and 192.168.0.0/16 represents 256 contiguous Class C blocks (192.168.0.0 to 192.168.255.255).

Step-by-Step Solution

1
Identify the RFC 1918 Class A private address range
10.0.0.0 to 10.255.255.255 corresponds to 10.0.0.0/8 (1 Class A network).
RFC 1918 reserves the entire 10.0.0.0/8 network block for private IP addressing.
2
Identify the RFC 1918 Class B private address range
172.16.0.0 to 172.31.255.255 corresponds to 172.16.0.0/12, which spans 16 contiguous Class B networks (172.16.0.0/16 through 172.31.0.0/16).
A /12 prefix length allows 4 bits of subnetwork variation in the second octet (16 to 31), creating 16 Class B ranges.
3
Identify the RFC 1918 Class C private address range
192.168.0.0 to 192.168.255.255 corresponds to 192.168.0.0/16, which spans 256 contiguous Class C networks (192.168.0.0/24 through 192.168.255.0/24).
A /16 prefix length allows 8 bits of subnetwork variation in the third octet (0 to 255), creating 256 Class C ranges.

Key Concept

RFC 1918 Private IPv4 Address Space Specifications
Question 9Question

A network administrator is configuring an internal host interface and must assign an IP address within the RFC 1918 Class B private address space. Which of the following IP addresses is a valid RFC 1918 private IPv4 address?

Show answer & explanation

Answer: 172.20.50.1

Answer

172.20.50.1
The address 172.20.50.1 is a valid RFC 1918 private IPv4 address because it falls within the 172.16.0.0/12 block, which ranges from 172.16.0.0 to 172.31.255.255.

Step-by-Step Solution

1
Identify the RFC 1918 Class B private address boundaries
RFC 1918 defines Class B private space as 172.16.0.0 through 172.31.255.255 (/12 prefix).
Understanding RFC 1918 ranges is essential for properly distinguishing private non-routable internal addresses from globally routable public addresses.
2
Evaluate the candidate addresses against the RFC 1918 boundaries
The address 172.20.50.1 falls between 172.16.0.0 and 172.31.255.255. The other addresses (172.32.1.10, 192.169.100.1, 11.10.0.1) fall outside RFC 1918 ranges.
Only addresses within the designated RFC 1918 ranges are non-routable on the public Internet and reserved for private network deployment.

Key Concept

Private IPv4 Address Ranges (RFC 1918)
Estimated Time:45s
Question 10Question

A network engineer is configuring internal host interfaces on a private enterprise network. According to RFC 1918, which of the following IP addresses falls within a reserved private IPv4 address block and can be assigned to internal network devices without public Internet routing?

Show answer & explanation

Answer: 172.20.45.10

Answer

172.20.45.10 is a valid private IPv4 address as defined by RFC 1918.
The address 172.20.45.10 is part of the RFC 1918 Class B private address range (172.16.0.0/12), which covers all IP addresses from 172.16.0.0 through 172.31.255.255. Since the second octet is 20, it falls within this reserved range and can be used on internal private networks without public routing.

Step-by-Step Solution

1
Recall the three designated RFC 1918 private IPv4 address ranges
The reserved ranges are: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), and 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).
RFC 1918 specifies exact address ranges reserved strictly for internal private enterprise use.
2
Evaluate the second octet of the Class B candidate address 172.20.45.10
The second octet is 20, which lies inclusively between 16 and 31.
Addresses starting with 172 are only private if the second octet is within the 16 to 31 range inclusive.
3
Verify candidates against public address boundaries
The address 172.20.45.10 is private, while 172.32.10.1, 192.169.1.25, and 11.10.0.1 fall outside the RFC 1918 designated ranges and are public addresses.
Only addresses inside the designated RFC 1918 prefixes are valid private addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Question 11Question

A network engineer is conducting an IP addressing audit for an enterprise network. The organization requires all internal hosts to utilize private IPv4 addresses specified in RFC 1918 to ensure proper isolated routing and avoid packet delivery issues across the public Internet. Which IPv4 address assignment contains a globally routable public IPv4 address rather than a valid RFC 1918 private address?

Show answer & explanation

Answer: 172.32.15.1/24 assigned to an internal host interface

Answer

172.32.15.1/24 assigned to an internal host interface is a globally routable public address because it falls outside the RFC 1918 Class B allocation (172.16.0.0 - 172.31.255.255).
The address starting with 172.32.15.1 is a public IPv4 address because the RFC 1918 Class B private address allocation only spans from 172.16.0.0 to 172.31.255.255 (a /12 prefix). Any address with a first octet of 172 and a second octet greater than 31 or less than 16 is a public, globally routable IP address.

Step-by-Step Solution

1
Recall the three designated RFC 1918 private IPv4 address ranges.
The reserved private ranges are: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), and 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).
Establishing accurate address boundaries is mandatory to distinguish non-routable private IPs from public IPs.
2
Evaluate the second octet of the Class B address candidate 172.32.15.1.
The second octet is 32, which exceeds the upper bound of 31 for the 172.16.0.0/12 private prefix block.
The /12 prefix length covers second octet values from 16 to 31 inclusive (binary 00010000 to 00011111).
3
Verify that all other candidate addresses fall strictly within RFC 1918 boundaries.
172.31.255.254 is within 172.16.0.0/12; 192.168.254.1 is within 192.168.0.0/16; 10.255.1.1 is within 10.0.0.0/8.
Confirming the validity of remaining options isolates the public address misconfiguration.

Key Concept

RFC 1918 Private IPv4 Address Space Boundaries
Question 12Question

Match each RFC 1918 private IPv4 address range to its defined default CIDR block and maximum number of usable host addresses.

Click a left item, then click its matching right item

Items

10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255

Matches

Show answer & explanation

Answer

10.0.0.0 to 10.255.255.255 matches the /8 CIDR block (16,777,21416,777,214 usable hosts); 172.16.0.0 to 172.31.255.255 matches the /12 CIDR block (1,048,5741,048,574 usable hosts); 192.168.0.0 to 192.168.255.255 matches the /16 CIDR block (65,53465,534 usable hosts).
Under RFC 1918, the three private IPv4 address allocations have distinct prefix masks and sizes: 10.0.0.0/8 provides a single large block with 24 host bits (16,777,21416,777,214 usable hosts); 172.16.0.0/12 encompasses 16 Class B ranges spanning 172.16.0.0 through 172.31.255.255 with 20 host bits (1,048,5741,048,574 usable hosts); and 192.168.0.0/16 encompasses 256 Class C ranges spanning 192.168.0.0 through 192.168.255.255 with 16 host bits (65,53465,534 usable hosts).

Step-by-Step Solution

1
Analyze the 10.0.0.0/8 Class A private block
The range 10.0.0.0 to 10.255.255.255 reserves 24 host bits (328=2432 - 8 = 24).
Calculating usable host count yields 2242=16,777,2142^{24} - 2 = 16,777,214 addresses.
2
Analyze the 172.16.0.0/12 Class B private block
The range 172.16.0.0 to 172.31.255.255 spans from second octet 16 to 31, reserving 20 host bits (3212=2032 - 12 = 20).
Calculating usable host count yields 2202=1,048,5742^{20} - 2 = 1,048,574 addresses.
3
Analyze the 192.168.0.0/16 Class C private block
The range 192.168.0.0 to 192.168.255.255 reserves 16 host bits (3216=1632 - 16 = 16).
Calculating usable host count yields 2162=65,5342^{16} - 2 = 65,534 addresses.

Key Concept

RFC 1918 Private IPv4 Address Allocation and CIDR Prefix Boundaries
Question 13Question

Match each RFC 1918 private IPv4 address block to its designated default CIDR prefix length.

Click a left item, then click its matching right item

Items

10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255

Matches

Show answer & explanation

Answer

10.0.0.0 to 10.255.255.255 matches /8, 172.16.0.0 to 172.31.255.255 matches /12, and 192.168.0.0 to 192.168.255.255 matches /16.
RFC 1918 specifies three private address blocks for enterprise networks: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), and 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).

Step-by-Step Solution

1
Identify the prefix length for the 10.0.0.0/8 address block.
The range 10.0.0.0 – 10.255.255.255 uses a /8 prefix length.
RFC 1918 defines the 10.0.0.0 network as a single Class A range with 8 network bits.
2
Identify the prefix length for the 172.16.0.0 address block.
The range 172.16.0.0 – 172.31.255.255 uses a /12 prefix length.
RFC 1918 allocates a set of 16 Class B networks from 172.16.0.0 through 172.31.255.255, aggregating to a /12 prefix length.
3
Identify the prefix length for the 192.168.0.0 address block.
The range 192.168.0.0 – 192.168.255.255 uses a /16 prefix length.
RFC 1918 allocates a set of 256 Class C networks from 192.168.0.0 through 192.168.255.255, aggregating to a /16 prefix length.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Question 14Question

A network security architect is auditing perimeter firewalls and IP addressing schemes across a enterprise topology. Match each IPv4 address specification to its corresponding RFC 1918 compliance status and public Internet routing behavior.

Click a left item, then click its matching right item

Items

172.31.255.254/28172.31.255.254/28
172.32.0.1/16172.32.0.1/16
192.168.255.254/31192.168.255.254/31
192.169.1.1/24192.169.1.1/24

Matches

Show answer & explanation

Answer

The correct pairings match 172.31.255.254/28172.31.255.254/28 to the private 172.16.0.0/12172.16.0.0/12 scope description, 172.32.0.1/16172.32.0.1/16 to the public space directly above 172.31.255.255172.31.255.255, 192.168.255.254/31192.168.255.254/31 to the private 192.168.0.0/16192.168.0.0/16 point-to-point scope description, and 192.169.1.1/24192.169.1.1/24 to the public space directly above 192.168.255.255192.168.255.255.
Each IP address is accurately mapped according to RFC 1918 boundaries: 172.31.255.254172.31.255.254 is private (172.16.0.0/12172.16.0.0/12), 172.32.0.1172.32.0.1 is public space immediately above 172.31.255.255172.31.255.255, 192.168.255.254192.168.255.254 is private (192.168.0.0/16192.168.0.0/16), and 192.169.1.1192.169.1.1 is public space immediately above 192.168.255.255192.168.255.255.

Step-by-Step Solution

1
Evaluate RFC 1918 address ranges and boundary limits.
The three RFC 1918 private address ranges are 10.0.0.0/810.0.0.0/8 (10.0.0.010.255.255.25510.0.0.0 - 10.255.255.255), 172.16.0.0/12172.16.0.0/12 (172.16.0.0172.31.255.255172.16.0.0 - 172.31.255.255), and 192.168.0.0/16192.168.0.0/16 (192.168.0.0192.168.255.255192.168.0.0 - 192.168.255.255).
Establishing accurate lower and upper boundary IP addresses is necessary to distinguish private from public IPv4 space.
2
Analyze 172.31.255.254/28172.31.255.254/28 and 172.32.0.1/16172.32.0.1/16.
172.31.255.254172.31.255.254 is the second-to-last address within 172.16.0.0/12172.16.0.0/12, making it private and non-routable. 172.32.0.1172.32.0.1 exceeds 172.31.255.255172.31.255.255, making it a public IP address.
Common misidentifications mistake 172.32.0.0/16172.32.0.0/16 for private space by assuming all 172.x.x.x172.x.x.x addresses are private, whereas only 172.16.0.0172.16.0.0 through 172.31.255.255172.31.255.255 are reserved by RFC 1918.
3
Analyze 192.168.255.254/31192.168.255.254/31 and 192.169.1.1/24192.169.1.1/24.
192.168.255.254192.168.255.254 falls inside 192.168.0.0/16192.168.0.0/16 and is private regardless of prefix length (/31/31). 192.169.1.1192.169.1.1 exceeds 192.168.255.255192.168.255.255, making it public.
The 192.168.0.0/16192.168.0.0/16 block ends at 192.168.255.255192.168.255.255. Addresses starting with 192.169.x.x192.169.x.x are public addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges and Boundary Verification
Question 15Question

During a security compliance audit of internal corporate subnets, a network engineer is asked to verify that host interfaces use IPv4 addresses from the Class B private space defined in RFC 1918. Which of the following IPv4 addresses falls strictly within the valid RFC 1918 Class B private address range?

Show answer & explanation

Answer: 172.31.200.15

Answer

The address 172.31.200.15 is the only valid RFC 1918 Class B private IPv4 address among the choices.
The IPv4 address 172.31.200.15 resides within the 172.16.0.0/12 block reserved by RFC 1918, which spans from 172.16.0.0 through 172.31.255.255.

Step-by-Step Solution

1
Recall the RFC 1918 private IPv4 address ranges.
Class A: 10.0.0.0 to 10.255.255.255 (10.0.0.0/8); Class B: 172.16.0.0 to 172.31.255.255 (172.16.0.0/12); Class C: 192.168.0.0 to 192.168.255.255 (192.168.0.0/16).
Identifying the official range boundaries is necessary to differentiate private space from public space.
2
Evaluate each provided option against the Class B RFC 1918 boundaries.
172.31.200.15 is between 172.16.0.0 and 172.31.255.255, making it a private RFC 1918 address.
The second octet of 31 is the upper boundary of the /12 block.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Estimated Time:1m 0s
Question 16Question

An administrator is configuring an internal workstation and needs to manually assign an IPv4 address that belongs to an RFC 1918 private network block. Which IPv4 address is valid for this requirement?

Show answer & explanation

Answer: 172.25.100.50

Answer

172.25.100.50 is a valid RFC 1918 private IPv4 address.
The address 172.25.100.50 is correct because RFC 1918 specifies 172.16.0.0/12 (covering 172.16.0.0 through 172.31.255.255) as a private IPv4 block. Because 25 is between 16 and 31 in the second octet, 172.25.100.50 is a valid private IPv4 address.

Step-by-Step Solution

1
Identify the designated RFC 1918 private IPv4 address ranges.
The defined private ranges are 10.0.0.0/8 (10.0.0.0 - 10.255.255.255), 172.16.0.0/12 (172.16.0.0 - 172.31.255.255), and 192.168.0.0/16 (192.168.0.0 - 192.168.255.255).
RFC 1918 reserves specific IP address blocks for private internal networks that are not routable on the public Internet.
2
Evaluate the given address options against the RFC 1918 ranges.
172.25.100.50 falls between 172.16.0.0 and 172.31.255.255, making it a valid private address. The addresses starting with 172.33, 192.169, and 11 are public addresses.
Only IP addresses within the exact start and end boundaries of RFC 1918 blocks are reserved for private use.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Question 17Question

An edge security gateway is configured to drop any outgoing packet to the public Internet if its source IP address belongs to an RFC 1918 private address space. During a security audit of un-translated egress traffic logs, four source IPv4 addresses were recorded. Which source IPv4 address is globally routable on the public Internet and will be permitted through the firewall filter?

Show answer & explanation

Answer: 172.32.10.55

Answer

172.32.10.55 is a public IPv4 address because it falls outside the RFC 1918 Class B private address allocation (172.16.0.0/12).
RFC 1918 allocates three specific ranges for private networks: 10.0.0.0/8 (10.0.0.0 - 10.255.255.255), 172.16.0.0/12 (172.16.0.0 - 172.31.255.255), and 192.168.0.0/16 (192.168.0.0 - 192.168.255.255). The address 172.32.10.55 begins with 172.32, which is higher than the upper boundary of 172.31.255.255, making it a globally routable public address that passes the RFC 1918 egress filter.

Step-by-Step Solution

1
Recall the RFC 1918 private IPv4 address allocations.
Class A: 10.0.0.0 to 10.255.255.255 (10.0.0.0/8), Class B: 172.16.0.0 to 172.31.255.255 (172.16.0.0/12), Class C: 192.168.0.0 to 192.168.255.255 (192.168.0.0/16).
Establishing accurate range boundaries is necessary to differentiate private non-routable addresses from public addresses.
2
Compare each given address against the RFC 1918 boundaries.
10.255.254.1 is inside 10.0.0.0/8; 192.168.100.255 is inside 192.168.0.0/16; 172.30.100.1 is inside 172.16.0.0/12. However, 172.32.10.55 exceeds 172.31.255.255.
Any IP starting with 172.32.x.x is part of public IP address space, not RFC 1918.
3
Determine which address is permitted through the egress filter.
172.32.10.55 is a public IP address and will pass through the RFC 1918 filter.
The filter only drops packets originating from RFC 1918 private ranges.

Key Concept

RFC 1918 Private IPv4 Address Space Boundaries
Estimated Time:1m 0s
Question 18Question

A network engineer is auditing perimeter firewall logs on an enterprise WAN edge router. The firewall security policy is configured to drop any outbound packet whose source IP address falls within the RFC 1918 private IPv4 address space unless it has undergone Network Address Translation (NAT). During a routine inspection, the log records outbound packets from four host IP addresses: 11.10.5.1, 172.28.140.22, 172.33.10.1, and 192.169.50.4. Which source IP address will be dropped by the firewall policy for utilizing an RFC 1918 private IPv4 address?

Show answer & explanation

Answer: 172.28.140.22

Answer

172.28.140.22 is the RFC 1918 private IPv4 address and will be dropped by the firewall.
The IP address 172.28.140.22 falls directly within the RFC 1918 Class B private address space of 172.16.0.0 to 172.31.255.255 (a /12 prefix block). Because it is an un-translated private address destined for an outbound WAN connection, the firewall policy correctly drops the traffic.

Step-by-Step Solution

1
Recall the defined RFC 1918 private IPv4 address ranges.
Class A: 10.0.0.0 to 10.255.255.255 (10.0.0.0/8)
Class B: 172.16.0.0 to 172.31.255.255 (172.16.0.0/12)
Class C: 192.168.0.0 to 192.168.255.255 (192.168.0.0/16)
These three blocks are set aside by IANA and RFC 1918 for internal network use and are non-routable over the public Internet without NAT.
2
Evaluate host 172.28.140.22 against the Class B RFC 1918 range.
The second octet is 28, which falls inclusively between 16 and 31.
Because 16 <= 28 <= 31, 172.28.140.22 is a valid private IPv4 address.
3
Verify the remaining candidate IP addresses to confirm public vs private classification.
11.10.5.1 is outside 10.0.0.0/8; 172.33.10.1 is above 172.31.255.255; 192.169.50.4 is outside 192.168.0.0/16.
All three remaining options are public IPv4 addresses.

Key Concept

RFC 1918 Private IPv4 Address Space Boundaries
Question 19Question

A network manager is reviewing host IP allocation requests for internal database servers. To ensure non-routable communication over the public Internet according to RFC 1918 standards, the network team must identify valid private host IPv4 addresses. Which of the following IPv4 addresses belong to the RFC 1918 private address space and can be assigned to internal hosts? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: 10.200.150.75; 172.29.45.12

Answer

The addresses 10.200.150.75 and 172.29.45.12 belong to the RFC 1918 private IPv4 address space.
The IP addresses 10.200.150.75 and 172.29.45.12 fall directly within the RFC 1918 private IPv4 blocks. 10.200.150.75 is inside the 10.0.0.0/8 block, and 172.29.45.12 is inside the 172.16.0.0/12 block.

Step-by-Step Solution

1
Recall the RFC 1918 reserved private IPv4 address ranges.
Class A: 10.0.0.0 to 10.255.255.255 (10.0.0.0/8); Class B: 172.16.0.0 to 172.31.255.255 (172.16.0.0/12); Class C: 192.168.0.0 to 192.168.255.255 (192.168.0.0/16).
These specific ranges are reserved by IANA for private enterprise networking and are non-routable over the public Internet.
2
Evaluate candidate address 10.200.150.75.
10.200.150.75 falls between 10.0.0.0 and 10.255.255.255.
It matches the 10.0.0.0/8 private address prefix.
3
Evaluate candidate address 172.29.45.12.
172.29.45.12 falls between 172.16.0.0 and 172.31.255.255.
The second octet 29 is within the range 16 through 31 reserved for RFC 1918 Class B space.
4
Evaluate candidate addresses 172.35.10.20 and 192.169.100.1.
172.35.10.20 (second octet 35 > 31) and 192.169.100.1 (second octet 169 != 168) are outside RFC 1918 boundaries.
Both are globally routable public IPv4 addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Estimated Time:1m 30s
Question 20Question

A network administrator is allocating IPv4 addresses for internal workstations on an enterprise LAN. Which of the following IPv4 addresses are reserved for private network use under RFC 1918? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: 10.200.15.1; 172.28.45.10

Answer

The addresses 10.200.15.1 and 172.28.45.10 are reserved private IPv4 addresses under RFC 1918.
The IPv4 address 10.200.15.1 belongs to the 10.0.0.0/8 private address block, and 172.28.45.10 belongs to the 172.16.0.0/12 private address block (which ranges from 172.16.0.0 to 172.31.255.255). Both are valid RFC 1918 private IPv4 addresses.

Step-by-Step Solution

1
Identify the three RFC 1918 private address ranges
Class A: 10.0.0.0/8 (10.0.0.0 - 10.255.255.255), Class B: 172.16.0.0/12 (172.16.0.0 - 172.31.255.255), Class C: 192.168.0.0/16 (192.168.0.0 - 192.168.255.255).
RFC 1918 explicitly defines these three address blocks for private, unroutable network use.
2
Evaluate each candidate address against the RFC 1918 blocks
10.200.15.1 is inside 10.0.0.0/8. 172.28.45.10 is inside 172.16.0.0/12. 172.35.10.50 is outside 172.16.0.0/12 (35 > 31). 192.170.10.1 is outside 192.168.0.0/16 (170 != 168).
Comparing second octets ensures correct boundary verification for Class B and Class C private ranges.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Page 1 / 2Next
Private IPv4 Addressing and RFC 1918 Practice Questions — Cisco CCNA | Examkin