Exam N10-008 topic 1 question 848 discussion

A. Both internal and external would not work. B. Internal would not work, but external yes. C. Both internal and external would not work. D. Internal would work, but external would not. Therefore the only option is B.

NAT makes no sense in this context. It's meant to translate a local IP into a public one to get multiple local devices to access internet. This is literally the opposite of the question that states they can ONLY connect to the INTERNET. I think a rogue DHCP would most likely cut all connection, if you get in a completely wrong subnet, you obviously won't access internal, and NAT won't work, since the router won't expect it. C is probably the sensible answer. External names could be resolved and not internal ones.

C seems like the safest bet here to me.

D NAT is my answer in here

Rogue DHCP server *might* not disrupt your external internet access. Rogue DHCP server would almost certainly mess up your LAN settings and make it so that you're out of your typical network segment, making internal communication impossible.

NAT is to allow private networks to communicate with the internet using a limited number of public IP addresses. while setting up Printers in my office, it does take DNS address. so i guess answer should be C. unreachable DNS

A) Wrong - with APIPA address you can't connect to the Internet B) Correct - there is a possibility that workstation received IP address and default gateway from the rogue DHCP. In that case Internet access works, however access to internal resources is prohibited. C) Wrong - if the DNS would be unreachable, connectivity to the Internet resources would not be possible D) Wrong - NAT settings has nothing to do with accessing internal resources. With incorrect nat settings connectivity to the Internet resources would not work, but it's no the case in the example

Going to have to go with C. I would say the safest bet is to say internal DNS servers could be at play.

d for sure

I think is D.

A NAT error is more likely to cause this issue. If the NAT configuration doesn't properly map the workstation's internal IP address to the public IP address used for internet access, the workstation might be able to access the internet but not communicate with internal resources on the private network.