Exam Professional Cloud Network Engineer topic 1 question 85 discussion

Letter B. Explain: in the question said "must be invoked only by multiple clients within the same VPC", A and C exclude because mention external IP. Letter D exclude because url https://[API_NAME]/[API_VERSION]/ to internal DNS no make sense. Letter B is correct (https://cloud.google.com/compute/docs/internal-dns)

Lots of anti-patterns and excessive creativity in this question: a) reserving external address is meaningless, there's no advantage in going through public ip address for the internal VPC clients. The service will be accessed from the same VPC, private address should be fine, this makes A) and C) senseless b) use of perrenial virtual machine is a pattern better suited for on-prem than for cloud. B can work, but I'd rather avoid this setup c) no A record is involved in D).

This option ensures that clients within the same VPC network use the internal DNS name to connect to the HTTP API hosted on the Compute Engine virtual machine instance. By using the internal DNS name, traffic will not leave the VPC, and the service will not be reachable from outside the VPC. Additionally, clients can get the IP address of the service by resolving the internal DNS name. Option A is incorrect because using a static external IP address means that the service can be accessed from outside the VPC. Option C is also incorrect because it also involves using a static external IP address, which can make the service accessible from outside the VPC. Option D is incorrect because it does not provide a way for clients to get the IP address of the service, and the service can be accessed from outside the VPC.

B. Ensure that clients use Compute Engine internal DNS by connecting to the instance name with the URL https://[INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal/. This option suggests using the internal DNS provided by Compute Engine, which is the recommended approach when clients are within the same VPC. By connecting to the instance name using this URL format, clients can resolve the IP address of the service without the need for a static external IP or additional DNS configuration.

• B. Ensure that clients use Compute Engine internal DNS by connecting to the instance name with the url https://*****[INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal/. $ ping ***** VM_NAME.ZONE.c.PROJECT_ID.internal -c 1 PING VM_NAME.ZONE.c.PROJECT_ID.internal (10.240.0.17) 56(84) bytes of data. 64 bytes from VM_NAME.ZONE.c.PROJECT_ID.internal (10.240.0.17): icmp_seq=1 ttl=64 time=0.136 ms Replace the following:

answer is b "Virtual Private Cloud networks on Google Cloud have an internal DNS service that lets instances in the same network access each other by using internal DNS names" This name can be used for access: [INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal https://cloud.google.com/compute/docs/internal-dns#access_by_internal_DNS

B it is