What static IPv4 address and subnet were assigned to the DMZ interface?

What static IPv4 address and subnet were assigned to the DMZ interface?

• A. 172.16.1.1/16
• B. 192.168.0.1/24
• C. 10.0.0.1/8
• D. 172.30.0.1/16

Answer: (A)

Isolating the DMZ relies on placing its devices on a dedicated private subnet and giving the interface a static address within that subnet. In this setup, the DMZ uses the 172.16.0.0/16 private range, so the DMZ interface should have an address that falls inside 172.16.0.0 to 172.16.255.255 with a 255.255.0.0 mask. The address 172.16.1.1 with a /16 (255.255.0.0) mask fits exactly into that DMZ subnet, making it a proper static address for the DMZ interface. The other options place the interface on different private subnets (for example, 192.168.0.0/24, 10.0.0.0/8, or 172.30.0.0/16), which do not correspond to the designated DMZ network in this configuration.

Isolating the DMZ relies on placing its devices on a dedicated private subnet and giving the interface a static address within that subnet. In this setup, the DMZ uses the 172.16.0.0/16 private range, so the DMZ interface should have an address that falls inside 172.16.0.0 to 172.16.255.255 with a 255.255.0.0 mask. The address 172.16.1.1 with a /16 (255.255.0.0) mask fits exactly into that DMZ subnet, making it a proper static address for the DMZ interface. The other options place the interface on different private subnets (for example, 192.168.0.0/24, 10.0.0.0/8, or 172.30.0.0/16), which do not correspond to the designated DMZ network in this configuration.