Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is configuring a custom mode VPC network to support a new backend workload. The engineering team plans to deploy virtual machines (VMs) located exclusively in the us-central1 region without assigning them external IP addresses.
The VMs must be able to securely access Google APIs (such as Cloud Storage) without routing over the public internet, and security compliance requires capturing network telemetry for all VM traffic within the subnet.
Which subnet configuration meets these requirements?
us-central1 region, enable Private Google Access, and enable VPC Flow Logs.In Google Cloud Platform (GCP), Virtual Private Cloud (VPC) networks are global resources, but individual subnets are strictly regional resources. When creating a subnet to support specific workloads, you must bind it to a designated region and configure optional regional subnet-level features such as Private Google Access and VPC Flow Logs.
us-central1 ensures that compute resources launched in that region can attach their network interfaces directly to this subnet's IP range.This approach directly satisfies all architectural and compliance requirements during the standard subnet creation process. Subnets must be regional, Private Google Access specifically enables private Google API reachability, and explicitly enabling VPC Flow Logs activates telemetry collection on the subnet.
us-central1 region, disable Private Google Access, and configure the subnet purpose as INTERNAL_HTTPS_LOAD_BALANCER.A subnet configured with the purpose INTERNAL_HTTPS_LOAD_BALANCER is designated as a proxy-only subnet. Proxy-only subnets provide IP address space reserved specifically for Envoy proxies used by internal Application Load Balancers.
Invalid field set in subnetwork with purpose INTERNAL_HTTPS_LOAD_BALANCER).The requirement was to reserve an IP address pool for backend proxy endpoints used by internal Application Load Balancers rather than provisioning a subnet for backend VM workloads.
This option incorrectly assumes that a single subnet can be created as a global resource spanning multiple Google Cloud regions simultaneously.
us-central1).Google Cloud VPC architecture supported multi-region or global subnet addressing schemes, which it does not. In legacy networking (deprecated), global networks existed without regional subnets, but all modern custom and auto mode VPCs enforce regional subnets.
us-central1 region, enable Private Google Access, and leave VPC Flow Logs disabled because new subnets automatically enable flow logging by default.When a new subnet is created in a Google Cloud VPC network, VPC Flow Logs is set to disabled by default unless explicitly enabled in the subnet creation command or API request payload.
subnet_flow_logs or logConfig.enable must be set to true.0.0 to 1.0) and aggregation intervals (INTERVAL_5_SEC to INTERVAL_15_MIN).Google Cloud automatically enabled VPC Flow Logs by default upon creation of any new subnet, which is contrary to standard VPC behavior.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated