Google Associate Cloud Engineer Practice Test 37
Question 360
A private internal application must be load-balanced across approved clients in the same VPC, with no internet endpoint. What endpoint class fits?
- An external Application Load Balancer configured with a URL map and backend services for the required paths.
- Increase the VM CPU count as the only remedy for the network path failure.
- Allow all ingress from 0.0.0.0/0 without narrowing the relevant source or destination.
- Use a suitable internal load balancer and restrict client access within the approved private network.
Explanation
Correct Answer
D:Internal load balancers serve VPC-connected clients without exposing an ordinary internet-facing frontend.
Incorrect Answers
A:This does not establish the network route or policy needed by the traffic. The necessary distinction is the actual network path or policy. The appropriate action here is: Use a suitable internal load balancer and restrict client access within the approved private network.
B:Additional CPU changes compute capacity rather than the named cloud control. The case instead depends on the actual network path or policy. The appropriate action here is: Use a suitable internal load balancer and restrict client access within the approved private network.
C:An unrestricted network opening is broader than the described connection requires. It leaves the actual network path or policy unaddressed. The appropriate action here is: Use a suitable internal load balancer and restrict client access within the approved private network.
Question 361
A website must use one global public IP and serve HTTP traffic from backend deployments in several supported Google Cloud regions, with cross-region balancing. No load balancer exists yet. Which design should be built?
- Create a separate regional external Network Load Balancer in each region and claim that they all share one global IP automatically.
- Deploy only a regional external Application Load Balancer in one region and assume it directly spans arbitrary other regions.
- Create a global external Application Load Balancer with an appropriate global frontend and eligible backends in multiple regions.
- Use Cloud NAT to translate inbound worldwide HTTP traffic to internal private VMs based on the URL path.
Explanation
Correct Answer
C:Create a global external Application Load Balancer with an appropriate global frontend and eligible backends in multiple regions. The global external Application Load Balancer supports a global frontend and eligible multi-region backend configuration for HTTP(S) traffic.
Incorrect Answers
A:Create a separate regional external Network Load Balancer in each region and claim that they all share one global IP automatically. Independent regional load balancers have separate endpoint resources. They do not automatically become a single global Anycast frontend.
B:Deploy only a regional external Application Load Balancer in one region and assume it directly spans arbitrary other regions. A regional load-balancing frontend serves a regional design. It is not the global entry point requested for multi-region backend availability.
D:Use Cloud NAT to translate inbound worldwide HTTP traffic to internal private VMs based on the URL path. Cloud NAT is for outbound translation, not inbound public HTTP load balancing and cross-region application routing.
Question 362
A regulated service must terminate incoming traffic and run all application backends in a single approved Google Cloud region. The team does NOT require global anycast load balancing. Which architecture best respects the requested regional scope?
- Deploy a global external Application Load Balancer by default; it guarantees all global proxy processing occurs only in the chosen backend region.
- Choose the protocol-appropriate supported regional external or internal load balancer and locate its eligible backends in the approved region.
- Use a global Cloud DNS record alone, because DNS automatically performs health-aware HTTPS termination within a region.
- Publish individual Compute Engine public IPs without a load balancer; each public address includes managed regional TLS proxying.
Explanation
Correct Answer
B:Choose the protocol-appropriate supported regional external or internal load balancer and locate its eligible backends in the approved region. Regional load balancer variants are designed for appropriate traffic types and single-region backend scope. The exact product must match client reachability and protocol.
Incorrect Answers
A:Deploy a global external Application Load Balancer by default; it guarantees all global proxy processing occurs only in the chosen backend region. Global external Application Load Balancers use Google's global edge/proxy design and are not equivalent to a regionally scoped frontend.
C:Use a global Cloud DNS record alone, because DNS automatically performs health-aware HTTPS termination within a region. DNS resolves names, not HTTPS requests or backend health, and does not provide the managed regional load-balancing behavior.
D:Publish individual Compute Engine public IPs without a load balancer; each public address includes managed regional TLS proxying. A VM external IP exposes a network endpoint but does not itself supply a managed regional TLS load-balancer proxy.
Question 363
A service handles encrypted HTTP traffic and requires TLS termination at a managed load balancer so the backend receives inspected HTTP headers. Why is a passthrough Network Load Balancer unsuitable?
- Use a Premium-tier global external Application Load Balancer with appropriate HTTPS certificate, backend services, health checks and supported edge security policy.
- Change a billing account to modify listener protocol and routing behavior.
- Change only the backend instance labels and assume health checks will repair automatically.
- Use an appropriate Application Load Balancer that terminates TLS and provides HTTP routing under the approved design.
Explanation
Correct Answer
D:Passthrough load balancing forwards transport packets; it does not perform managed Layer-7 TLS termination or inspect HTTP request paths.
Incorrect Answers
A:The suggested action changes another component without meeting the main requirement. The specific requirement concerns the load balancer's effective traffic handling.
B:Billing changes payment responsibility, not the technical behavior of this workload. The necessary distinction is the load balancer's effective traffic handling.
C:The suggested action changes another component without meeting the main requirement. The case instead depends on the load balancer's effective traffic handling.
Question 364
A newly configured external HTTP load balancer marks a functioning backend unhealthy. The health check probes /health on port 8080, but the application serves /ready on port 9090 and firewall rules deny probes. What must be corrected?
- Disable all health checks and assume successful manual browser requests guarantee backend health.
- Set the health check to the correct serving protocol/path/port and authorize the documented probe sources to reach the backend.
- Increase the Cloud Billing budget so the load balancer ignores missing or blocked health-probe responses.
- Change backend VM instance names to match the forwarding rule; probe endpoints are selected by instance display name.
Explanation
Correct Answer
B:Set the health check to the correct serving protocol/path/port and authorize the documented probe sources to reach the backend. The probe must reach the application's actual health endpoint and pass the relevant firewall. Both path/port and probe ingress determine health status.
Incorrect Answers
A:Disable all health checks and assume successful manual browser requests guarantee backend health. Health checks are how the load balancer decides which backends can receive traffic. Disabling checks does not establish the required healthy backend state.
C:Increase the Cloud Billing budget so the load balancer ignores missing or blocked health-probe responses. Cost settings cannot cause a blocked TCP probe or wrong HTTP response path to become healthy.
D:Change backend VM instance names to match the forwarding rule; probe endpoints are selected by instance display name. VM display names do not replace the protocol/path/port and firewall criteria used by the load balancer's health checks.
Question 365
The load balancer routes traffic to a backend group without an appropriate attached serving capacity policy, causing high latency under growth. What should be paired with the balancer?
- Create a global external Application Load Balancer with an appropriate global frontend and eligible backends in multiple regions.
- Disable the load balancer health checks and send production traffic to every backend unconditionally.
- Change a billing account to modify listener protocol and routing behavior.
- Configure suitable backend autoscaling and instance-group capacity limits to handle peak demand.
Explanation
Correct Answer
D:Load balancing distributes traffic but does not itself guarantee enough healthy backend capacity.
Incorrect Answers
A:Placement changes do not automatically implement the required resource-level feature. The case instead depends on the requested latency measurement.
B:The suggested action changes another component without meeting the main requirement. It leaves the requested latency measurement unaddressed.
C:Billing changes payment responsibility, not the technical behavior of this workload. The specific requirement concerns the requested latency measurement.
Question 366
A worldwide HTTPS service needs a single public anycast entry point, Google-managed TLS termination, routing to healthy backends in multiple regions, and edge security policies. Which load balancer family fits?
- Use a Premium-tier global external Application Load Balancer with appropriate HTTPS certificate, backend services, health checks and supported edge security policy.
- Use only a regional internal passthrough load balancer; it provides an internet-wide HTTPS anycast frontend by default.
- Use a single Compute Engine VM external IP; that address automatically distributes traffic to backends in any region.
- Create a Cloud Storage lifecycle policy; object retention policies terminate TLS and evaluate web application firewall requests.
Explanation
Correct Answer
A:Use a Premium-tier global external Application Load Balancer with appropriate HTTPS certificate, backend services, health checks and supported edge security policy. A global external Application Load Balancer provides HTTPS proxying with globally distributed client ingress and supports cross-region backends and relevant policies.
Incorrect Answers
B:Use only a regional internal passthrough load balancer; it provides an internet-wide HTTPS anycast frontend by default. Internal passthrough load balancers are for internal client traffic and do not provide the specified global external HTTP proxy frontend.
C:Use a single Compute Engine VM external IP; that address automatically distributes traffic to backends in any region. A VM IP is a direct endpoint and has no automatic health-aware global distribution across separate regional backends.
D:Create a Cloud Storage lifecycle policy; object retention policies terminate TLS and evaluate web application firewall requests. Cloud Storage retention controls object deletion, not global HTTPS termination, WAF evaluation, or backend routing.
Question 367
An internet-facing global service wants clients on different continents to enter the Google network near their users rather than traverse ordinary transit providers for most of the trip. Which Network Service Tier supports that objective?
- Standard Tier, because it guarantees that traffic stays on Google's backbone all the way to the final mile.
- No network tier is relevant; both tiers have identical wide-area path selection for public user traffic.
- Cloud NAT, because source NAT of private VMs is the network performance tier for global public ingress.
- Premium Tier, for an eligible global external frontend and Google backbone-oriented routing.
Explanation
Correct Answer
D:Premium Tier, for an eligible global external frontend and Google backbone-oriented routing. Premium Tier routes eligible internet traffic within Google's worldwide network for more of the path, supporting the global low-latency design.
Incorrect Answers
A:Standard Tier, because it guarantees that traffic stays on Google's backbone all the way to the final mile. Standard Tier optimizes cost and can use peering or transit providers closer to a Google Cloud region; it is not the premium backbone design described.
B:No network tier is relevant; both tiers have identical wide-area path selection for public user traffic. Google documents meaningful differences between Premium and Standard routing paths, supported features, and external frontend configurations.
C:Cloud NAT, because source NAT of private VMs is the network performance tier for global public ingress. Cloud NAT provides outbound translation for eligible private workloads; it is not the ingress network tier for a global public web endpoint.
Question 368
A low-cost regional API has no strict global latency requirement and uses an eligible regional external IP. Which tier may reduce egress cost?
- Use Standard Network Service Tier where supported after validating performance and feature requirements.
- Set the eligible VM/external-IP resource's network tier explicitly to Standard and verify that its frontend mode supports it.
- Change the VPC display name and assume routes and firewall rules are automatically corrected.
- Create an unrelated subnet without changing the active routes or selected targets.
Explanation
Correct Answer
A:Standard Tier can trade the global backbone path for lower cost through ordinary ISP/transit networks.
Incorrect Answers
B:Network settings and service or application controls must be distinguished. The necessary distinction is the chosen Network Service Tier.
C:Display names and labels identify resources; they do not enforce their runtime behavior. The case instead depends on the chosen Network Service Tier.
D:This does not establish the network route or policy needed by the traffic. It leaves the chosen Network Service Tier unaddressed.
Question 369
A deployment configures a GLOBAL external Application Load Balancer but specifies Standard Network Service Tier. The API rejects this combination. What adjustment preserves the global design?
- Keep Standard Tier and switch only the certificate from managed to self-managed; certificate selection enables unsupported global tier combinations.
- Use an internal regional forwarding rule but continue advertising the same public anycast address without changing frontend mode.
- Turn off backend health checks; global tier compatibility depends on the health-check request frequency.
- Use Premium Tier for the global external Application Load Balancer, or redesign to an eligible regional Standard-tier architecture.
Explanation
Correct Answer
D:Use Premium Tier for the global external Application Load Balancer, or redesign to an eligible regional Standard-tier architecture. Google's load-balancer matrix lists global external Application Load Balancers under Premium Tier; Standard-tier operation requires a supported regional option.
Incorrect Answers
A:Keep Standard Tier and switch only the certificate from managed to self-managed; certificate selection enables unsupported global tier combinations. TLS certificate management does not determine which Network Service Tier supports a global external Application Load Balancer.
B:Use an internal regional forwarding rule but continue advertising the same public anycast address without changing frontend mode. An internal regional frontend differs from the requested global external entry point and cannot preserve its routing merely by reusing a public address.
C:Turn off backend health checks; global tier compatibility depends on the health-check request frequency. Health checks are a backend availability mechanism, not the reason Standard Tier is unsupported for the global load-balancer mode.
Question 370
A Compute Engine VM with an eligible regional external IPv4 address needs Standard Network Service Tier despite the project default being Premium. Which configuration takes precedence when supported?
- Rename the VPC network Standard; a network display name changes all external routes to the Standard service tier.
- Set the eligible VM/external-IP resource's network tier explicitly to Standard and verify that its frontend mode supports it.
- Turn off Cloud Logging on the project; logging state selects the default network tier for instance internet paths.
- Move the VM into a multi-region Cloud Storage bucket; object bucket location determines the VM's external network tier.
Explanation
Correct Answer
B:Set the eligible VM/external-IP resource's network tier explicitly to Standard and verify that its frontend mode supports it. For supported Compute Engine external endpoints, a resource-level tier choice can override the project's default tier when creating or configuring the eligible address.
Incorrect Answers
A:Rename the VPC network Standard; a network display name changes all external routes to the Standard service tier. VPC names are resource labels and do not determine Premium-versus-Standard eligible external IP configuration.
C:Turn off Cloud Logging on the project; logging state selects the default network tier for instance internet paths. Cloud Logging collection is independent of Network Service Tier. Disabling logs does not request Standard IP routing.
D:Move the VM into a multi-region Cloud Storage bucket; object bucket location determines the VM's external network tier. Compute Engine VMs are not members of Cloud Storage buckets, and storage location does not configure their regional external IP tier.