Associate Cloud EngineerDemo

By Google · Question Mode

QuestionQ6

Configuring access and security

You have an application configured to locate its licensing server at the IP address 10.0.3.21. You need to deploy the licensing server on Compute Engine, and you must do so without changing the application's configuration, while ensuring the application can still reach the licensing server. What should you do?

  • A Reserve the IP 10.0.3.21 as a static internal IP address using gcloud and assign it to the licensing server.
  • B Reserve the IP 10.0.3.21 as a static public IP address using gcloud and assign it to the licensing server.
  • C Use the IP 10.0.3.21 as a custom ephemeral IP address and assign it to the licensing server.
  • D Start the licensing server with an automatic ephemeral IP address, and then promote it to a static internal IP address.
Explanation

10.0.3.21 is a private RFC1918 address, so it must be configured as an internal IP on the Compute Engine instance's network interface. Google Cloud allows you to reserve a specific, currently unused internal IP address within a subnet's range as a static internal IP using the gcloud compute addresses create command (specifying --addresses=10.0.3.21 and the appropriate subnet), and then assign that reserved address to the VM when creating it. This guarantees the licensing server always has the exact IP the application expects, without needing to alter the application's configuration. Reserving it as a public/external IP would not match the required internal address, and relying on an ephemeral internal IP does not guarantee persistence of that specific address across VM restarts.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!