nerdexam
CompTIA

SK0-005 · Question #582

A systems administrator notices that 2 machine on a newly provisioned VLAN is having trouble connecting to the internet. The IP address is 192.168.10.10 with a subnet mask of 255.255.254.0. The…

The correct answer is D. Changing the subnet mask to 255.255.255.128. The machine's large subnet mask (255.255.254.0 or /23) incorrectly places the gateway outside its subnet, while the network team defines a smaller /25 subnet, causing connectivity issues.

Troubleshooting

Question

A systems administrator notices that 2 machine on a newly provisioned VLAN is having trouble connecting to the internet. The IP address is 192.168.10.10 with a subnet mask of 255.255.254.0. The networking team confirms routing is working, and the default gateway can be reached on the subnet assigned to the VLAN. The team also confirms that the subnet is 192.168.10.0/25 with a gateway address of 182.168.10. Which of the following will correct the issue?

Options

  • AChanging the machine IP to 192.168.10.131
  • BChanging the default gateway to 192.168.0.254
  • CAdding a static route using the ROUTE command
  • DChanging the subnet mask to 255.255.255.128

How the community answered

(40 responses)
  • A
    5% (2)
  • B
    13% (5)
  • C
    3% (1)
  • D
    80% (32)

Why each option

The machine's large subnet mask (255.255.254.0 or /23) incorrectly places the gateway outside its subnet, while the network team defines a smaller /25 subnet, causing connectivity issues.

AChanging the machine IP to 192.168.10.131

Changing the machine IP to 192.168.10.131 would place it in the second half of the /25 subnet, which still wouldn't resolve the fundamental subnet mask mismatch for the gateway.

BChanging the default gateway to 192.168.0.254

Changing the default gateway to 192.168.0.254 would place the gateway outside the machine's 192.168.10.0 network entirely, preventing connectivity.

CAdding a static route using the ROUTE command

Adding a static route is for routing traffic to remote networks; the issue is local subnet communication, as the gateway is reportedly reachable.

DChanging the subnet mask to 255.255.255.128Correct

The machine is configured with IP 192.168.10.10 and subnet mask 255.255.254.0 (a /23 network), while the network team states the subnet is 192.168.10.0/25 (192.168.10.0-192.168.10.127). Changing the subnet mask to 255.255.255.128 (a /25 mask) will ensure the machine's IP and the gateway (presumably within the 192.168.10.0/25 range) are on the same local subnet, allowing direct communication.

Concept tested: IP subnetting and gateway configuration

Source: https://learn.microsoft.com/en-us/windows-server/networking/technologies/ip-addressing/subnetting-basics

Topics

#Subnetting#IP addressing#Network configuration#Network troubleshooting

Community Discussion

No community discussion yet for this question.

Full SK0-005 Practice