Topic 1 Question 129
Your Dataproc cluster runs in a single Virtual Private Cloud (VPC) network in a single subnet with range 172.16.20.128/25. There are no private IP addresses available in the VPC network. You want to add new VMs to communicate with your cluster using the minimum number of steps. What should you do?
Modify the existing subnet range to 172.16.20.0/24.
Create a new Secondary IP Range in the VPC and configure the VMs to use that range.
Create a new VPC network for the VMs. Enable VPC Peering between the VMs' VPC network and the Dataproc cluster VPC network.
Create a new VPC network for the VMs with a subnet of 172.32.0.0/16. Enable VPC network Peering between the Dataproc VPC network and the VMs VPC network. Configure a custom Route exchange.
ユーザの投票
コメント(17)
Correction. Correct Answers is (A):
gcloud compute networks subnets expand-ip-range NAME gcloud compute networks subnets expand-ip-range - expand the IP range of a Compute Engine subnetwork
👍 41ESP_SAP2020/08/21I think is A,
👍 34francisco_guerra2020/08/09I just tried, no private IP available in VPC means that no IP's are available in subnets as it is consumed.. moreover there is no IP range associated with VPC in Google Cloud.
gcloud compute networks subnets expand-ip-range testvpcsubnet --prefix-length=24 --region=asia-east1
The IP range of subnetwork [testvpcsubnet] will be expanded from 172.16.20.128/25 to 172.16.20.0/24. This operation may take several minutes to complete and cannot be undone.
Do you want to continue (Y/n)? y
Updated [https://www.googleapis.com/compute/v1/projects/xxxxxx/regions/asia-east1/subnetworks/testvpcsubnet].
172.16.20.128/25 - has 126 hosts (starts from 129 to 254) 172.16.20.0/24 - has 254 (starts from 1 to 254)
there is no overlapping here earlier it was from 129 to 254 after expansion is now 1 to 254.. IP's we get from expansion is 2 to 128
👍 10kar_techie2022/12/12
シャッフルモード