ASSOCIATE-CLOUD-ENGINEER Question #316: Real Exam Question with Answer & Explanation

Question

Your Dataproc cluster runs in a single Virtual Private Cloud (VPC) network in a single subnetwork with range 172.16.20.128/25. There are no private IP addresses available in the subnetwork. You want to add new VMs to communicate with your cluster using the minimum number of steps. What should you do?

Options

• AModify the existing subnet range to 172.16.20.0/24.
• BCreate a new Secondary IP Range in the VPC and configure the VMs to use that range.
• CCreate a new VPC network for the VMs. Enable VPC Peering between the VMs'VPC network and
• DCreate a new VPC network for the VMs with a subnet of 172.32.0.0/16. Enable VPC network

Explanation

To add new VMs to a Dataproc cluster in a subnetwork with no available IP addresses using the minimum number of steps, expand the existing subnetwork's IP range.

Common mistakes.

• B. Secondary IP ranges are primarily for alias IPs on instances, not for expanding the primary IP range for new instances in the subnet. While possible, it's more complex than simply expanding the primary range and might not be suitable for primary IP assignment for new VMs.
• C. Creating a new VPC network and then using VPC Peering involves multiple steps (network creation, subnet creation, peering configuration, routing setup) and adds complexity, which goes against the goal of minimizing steps.
• D. Similar to option C, creating an entirely new VPC network and enabling VPC network peering is a more complex solution than simply expanding the existing subnetwork, introducing additional overhead and configuration steps.

Concept tested. Expanding VPC subnetwork IP ranges

Reference. https://cloud.google.com/vpc/docs/configure-private-ip-addresses#expanding-subnet-range

No community discussion yet for this question.