Exam 312-50v11 topic 1 question 36 discussion

Name resolution not working, port 53 UDP blocked. Answer A is correct.

A (UDP/53 - DNS) is the correct, SP90732's DHCP probably a typo, the port of DHCP (UDP 67-68) are not on the list at all.

Clearly DNS is blocked which uses port 53

Port 53 UDP. The answer is clearly 'A'

IP OK, but DNS Name failed. That's the DNS relative problem.

If websites are accessible by IP address but not by URL, it suggests that traffic on TCP port 80 is blocked. TCP port 80 is used for standard HTTP traffic, which is used to access websites through their URLs. When TCP port 80 is blocked, web browsers are unable to establish the necessary HTTP connections to load web pages using URLs. If the issue were a blocked DNS UDP port 53 issue, you would likely encounter problems when initially trying to resolve domain names to IP addresses using DNS. This would prevent you from even reaching the stage where you could attempt to access websites by either IP address or URL. In that case, you would experience issues with the DNS resolution process itself, before even trying to establish an HTTP connection on port 80. In contrast, when you can access websites by IP address but not by URL, it's more likely that the issue lies with establishing the HTTP connection on port 80, which is used to load web pages. This points to a potential issue with blocked traffic on TCP port 80.

is DNS a TCP or UDP protocol? i think its a TCP protocol, why choose A

DNS services must not be functioning correctly. The purpose of DNS(Domain Name Service) is basically to match a URL to an IP. DNS is port 53.

A - DNS not resolved.

DHCP traffic is being blocked thats why you can still get it using the ip