Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 34 of 108
Free Preview · 108 of 359 · questions 1–108 of 359 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
C. 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 allows clients within the same Virtual Private Cloud (VPC) to resolve the Compute Engine instance's internal IP address using internal DNS, which is a feature provided by Compute Engine. The internal DNS name is constructed using the instance name, zone, and project ID, and this DNS entry is automatically created and managed by Google Cloud. This method ensures that traffic between clients and the API does not leave the Google Cloud network, providing lower latency and enhanced security.
This is a simple and effective way to enable communication between services within the same VPC without the need for external IP addresses or load balancing services.
D, connecting to the instance name with the url https://[API_NAME]/[API_VERSION]/, may not work as it is not specified how clients would know the correct API name and version. C is the correct answer: By connecting to the instance name with the url https://[INSTANCE_NAME].[ZONE].c. [PROJECT_ID].internal/, clients can use Compute Engine's internal DNS to access the API hosted on the virtual machine instance within the same VPC. This will allow clients to access the API with low latency and without the need for a static external IP address.