You have a VM instance running in a VPC with single-stack subnets. You need to ensure that the VM instance has a fixed IP address so that other services hosted in the same VPC can communicate with…

Question

Options

• APromote the existing IP address of the VM to become a static external IP address.
• BPromote the existing IP address of the VM to become a static internal IP address.
• CReserve a new static external IPv6 address and assign the new IP address to the VM.
• DReserve a new static external IP address and assign the new IP address to the VM.

• A
  3% (1)
• B
  91% (30)
• C
  6% (2)

Explanation

1. Fixed IP Address for VPC Communication: Services within the same VPC typically communicate using internal IP addresses. Promoting the existing internal IP address to a static internal IP address ensures that the VM retains the same IP address even after reboots, meeting the requirement for fixed IP 2. Minimizing Cost: Using internal IP addresses is cost-effective compared to external IPs because there are no additional charges for internal communication within a VPC. 3. Single-Stack Subnets: Since the subnets are single-stack (likely IPv4-only), assigning or reserving an external or IPv6 address (as in options C and D) is unnecessary and adds cost. 4. Google-Recommended Practices: Google Cloud recommends using internal IP addresses for communication within a VPC to improve security and reduce costs.

No community discussion yet for this question.