Exam Professional Cloud Network Engineer topic 1 question 76 discussion

it's C! You cannot change the internal IP address of an existing VM. You can do that for an external IP tho! The only way to preserve a VM's existing internal IP is by upgrading it to a static IP! Peace :)

It’s C

First of all, you have to rerve a new static internal , see the documentation : https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address#reservenewip gcloud compute addresses create ADDRESS_NAMES \ --region REGION --subnet SUBNETWORK \ --addresses IP_ADDRESS after that, create a vm instance with a reserved internal https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address#create_a_vm_instance_with_a_specific_internal_ip_address gcloud compute instances create VM_NAME --private-network-ip IP_ADDRESS it's B reserve new ip and assign

Option C is correct because changing the instance's current internal IP address to static ensures that the IP address will not be automatically assigned to a different instance if the original instance is deleted. This guarantees that the instance will keep the same IP address, providing better consistency and avoiding potential issues with applications or services that rely on that IP address. Option A is incorrect because assigning a public IP address to the instance does not prevent the private IP address from being automatically reassigned to a different instance. Option B is incorrect because assigning a new reserved internal IP address to the instance does not guarantee that the previous IP address will not be automatically reassigned to a different instance. Option D is incorrect because adding custom metadata to the instance does not prevent the IP address from being automatically reassigned to a different instance.

• C. Change the instance's current internal IP address to *** static. If you have ephemeral IP addresses that are currently in use, you can promote these addresses to static internal IP addresses so the addresses remain with your project until you actively remove them.

C. Change the instance's current internal IP address to static. https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address

yep C its for me

You cannot change the internal IP address of an existing resource. For example, you cannot assign a new static internal IP address to a running VM instance. You can, however, promote the ephemeral internal IP address of a resource to a static internal IP so that the address remains reserved even after the resource is deleted. https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address#restrictions So the Option "C" is right.

Answer is : C

C https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address#promote-in-use-internal-address If you have ephemeral IP addresses that are currently in use, you can promote these addresses to static internal IP addresses so the addresses remain with your project until you actively remove them.

C is correct

"C" is correct. Because in this scenario, we have a RUNNING instance and ensure that the current private IP address is a static address. We cannot change the internal IP address of an existing instance. "B" is wrong. On the other hand, we can promote the ephemeral internal IP address of a resource to a static internal IP address. "C" is correct.

definitely C, this is tested working

If we go with theory only... I would chose answer C --> https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address#reservenewip Since here https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip-address#reservenewip it is written that "automatically allocated or an unused address from an existing subnet".

Ans - C

Answer is C, because you need the current internal IP and not another IP.

Definately B