Exam Associate Cloud Engineer All Questions

View all questions & answers for the Associate Cloud Engineer exam

Exam Associate Cloud Engineer topic 1 question 129 discussion

Actual exam question from Google's Associate Cloud Engineer

Question #: 129
Topic #: 1

[All Associate Cloud Engineer Questions]

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?

A. Modify the existing subnet range to 172.16.20.0/24.
B. Create a new Secondary IP Range in the VPC and configure the VMs to use that range.
C. Create a new VPC network for the VMs. Enable VPC Peering between the VMs' VPC network and the Dataproc cluster VPC network.
D. 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.

Show Suggested Answer

Suggested Answer: A 🗳️

by francisco_guerra at Aug. 10, 2020, 4:43 a.m.

Comments

Submit Cancel

ESP_SAP

Highly Voted 4 years, 11 months ago

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

upvoted 50 times

ccieman2016

2 years, 10 months ago

I think, you can't expand ip range subnet, if there isn't space in VPC. I read this question a lot, VPC CIDR like with 172.16.20.128/25 and there's only one subnet 172.16.20.128/25 inside this VPC, so you can't expand nothing. for me, there's Letter C and D works, but letter D is necessary extra work. LETTER C is right.

upvoted 4 times

FeaRoX

2 years, 5 months ago

There's no information about VPC CIDR, only subnet. You can't tell that there's no space

upvoted 2 times

...

BigMac666

2 years ago

VPC's DO NOT have IP range limitations. You can only object if 172.16.20.0/25 is in use in the same VPC or in a VPC that this VPC is already peered with. .128/25 expands to .0/24 (i.e. "backwards") So as long as it's free, you're good. In a question like this, it's obvious that the simple answer is the right one, i.e. A - Expansion.

upvoted 3 times

gastonreppeto77

1 year, 9 months ago

- The statement is clear with point 1A and 2A: 1A.- "single Virtual Private Cloud (VPC) network in a single subnet" 2A.- "There are no private IP addresses available in the VPC network." - Question: How can you expand if there is a single VPC with a single subnet and there are no private IP addresses available in the only VPC network ??? - Result: Yes it has limitation, this question is clear, this is and exam, not the real life, we cannot verify anything else and we have the limitation os the statement.

upvoted 1 times

...

francisco_guerra

Highly Voted 4 years, 11 months ago

I think is A,

upvoted 37 times

passmepls

4 years, 11 months ago

thank you

upvoted 4 times

...

Priyanka109

2 years, 9 months ago

No it can't be as you can't modify ip address but can expand. There is no ip in the existing vpc so you have to create a new vpc and connect it using peering.

upvoted 3 times

...

alex70

Most Recent 3 months, 3 weeks ago

Selected Answer: B

B is the Best Answer: Minimal steps: Just add a secondary range and assign it to new VMs. No downtime: Existing Dataproc cluster remains unaffected. Same VPC communication: No need for peering or route changes.

upvoted 1 times

...

halifax

7 months, 1 week ago

Selected Answer: A

The answer is A, but the question is worded badly: "There are no private IP addresses available in the VPC network. " I think they meant to say there are no remaining private IP addresses left to assign to new virtual machine (VM) instances within the specified subnet of the VPC network. it is impossible to suggest that they run out of the class B private IP range because, in the Class B private IP address range, there are approximately 65,534 IP addresses.

upvoted 1 times

...

vansbg

7 months, 2 weeks ago

Selected Answer: C

I would go with C because "There are no private IP addresses available in the VPC network."

upvoted 1 times

...

deskj

9 months ago

Selected Answer: A

The question asks for the "minimum number of steps", not what is wrong or right. A is the "minimum number of steps".

upvoted 1 times

...

denno22

9 months, 3 weeks ago

Selected Answer: A

gcloud compute networks subnets expand-ip-range - expand the IP range of a Compute Engine subnetwork https://cloud.google.com/sdk/gcloud/reference/compute/networks/subnets/expand-ip-range

upvoted 2 times

...

Enamfrancis

9 months, 3 weeks ago

Selected Answer: A

A is correct answer

upvoted 1 times

...

RKS_2021

10 months ago

Selected Answer: A

Expand the subnet

upvoted 1 times

...

klayhung

10 months, 2 weeks ago

Selected Answer: A

The correct answer is A because increasing the disk size is the simplest way to address the issue. Option C is overly complex and unnecessary.

upvoted 1 times

...

klayhung

10 months, 2 weeks ago

The correct answer is A, because increasing the disk size is the simplest way to address the issue. Option C is overly complex and unnecessary.

upvoted 1 times

...

bad5fad

10 months, 3 weeks ago

Selected Answer: A

"minimum number of steps". I think A is correct

upvoted 1 times

...

Timfdklfajlksdjlakf

10 months, 4 weeks ago

Selected Answer: A

You can always expand subnets. You can shrink them. So A is the correct answer.

upvoted 1 times

...

yehia2221

11 months, 4 weeks ago

The correct answer is A, in GCP, it is different from AWS or Azure, there is no CIDR assigned for the VPC itself, but each subnet inside the VPC has its own unique CIDR range, that you can expand (with some considtions), I saw some answers based on the logic of AWS and Azure

upvoted 1 times

...