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.
Your team is deploying an internal backend microservice in Google Cloud. You must ensure that the service endpoint only accepts incoming traffic originating from internal Virtual Private Cloud (VPC) networks within the same project and authorized internal Google Cloud services, while strictly blocking all direct inbound traffic from the public internet.
Which ingress configuration should you implement to meet these traffic restriction requirements?
The default ingress setting in Google Cloud services is All, which keeps the endpoint open to any caller across the internet. A domain mapping associates a custom domain name (e.g., api.example.com) with the underlying service endpoint.
You were publishing a publicly accessible web application that needed branded URL routing via DNS without restricting network origins.
Relying on custom domains or "security through obscurity" by assuming callers will only use specific hostnames fails foundational cloud security principles. Network ingress settings must be explicitly locked down.
The Internal ingress setting is Google Cloud's most restrictive endpoint network control for hosted services. It ensures that service endpoints are only reachable via private paths within Google's internal network infrastructure, effectively shielding the resource from public internet routing.
run.app URL.Configuring the ingress setting directly to Internal is the simplest, most secure, and Google-recommended method to isolate backend workloads from public networks while preserving connectivity for authorized internal callers.
The Internal and Cloud Load Balancing setting is an intermediate ingress control that permits requests originating from internal resources as well as requests routed through an External Application Load Balancer.
The workload were a public web application that needed to accept global internet client requests strictly via an External Application Load Balancer with Google Cloud Armor protection, while blocking direct access to the raw service endpoint URL.
Choosing Internal and Cloud Load Balancing instead of Internal is a common misconfiguration when administrators intend to keep services entirely private but mistakenly select the load balancing option without distinguishing between internal and external load balancer tiers.
Resource Manager Tags are key-value pairs attached directly to Google Cloud resources (such as folders, projects, or clusters) that allow administrators to conditionally apply Identity and Access Management (IAM) policies and govern resource organization across the resource hierarchy.
environment:dev) governs IAM policy conditions and metadata classification; it does not alter the underlying network ingress settings of the service endpoint.env:dev).The objective was to conditionally grant administrative IAM permissions (such as deployment or viewing rights) to developers specifically on resources labeled as development environments.
Candidates often confuse Resource Manager Tags (used for hierarchical IAM governance and organization) with Network Tags or Secure Tags used in VPC firewall policies. Neither replaces service-level ingress controls for managed serverless endpoints.
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