Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization implements a hub-and-spoke network architecture in Google Cloud. The architecture includes a centralized hub-vpc connected to an on-premises data center using Cloud Interconnect, and a separate spoke-vpc hosting application workloads. The two VPCs are interconnected using VPC Network Peering.
The security and network engineering teams have established the following requirements:
spoke-vpc through hub-vpc.hub-vpc must advertise the spoke-vpc address spaces to the on-premises Border Gateway Protocol (BGP) peers.hub-vpc must restrict incoming traffic based on the identity of workloads running in spoke-vpc without using IP CIDR blocks or non-functional cross-peering constructs.Which combination of routing configurations and firewall controls should the organization implement?
hub-vpc Cloud Router, enable custom route export in hub-vpc and custom route import in spoke-vpc, and enforce ingress filtering using IAM-governed secure Resource Manager Tags as sources in network firewall policies.This solution pairs VPC Network Peering custom route exchange and Cloud Router custom route advertisements with IAM-governed Resource Manager Tags to satisfy cross-VPC hybrid routing constraints and strict boundary micro-segmentation.
hub-vpc Cloud Router allows on-premises BGP routers to learn routes to spoke-vpc subnets.hub-vpc peering configuration and custom route import on the spoke-vpc peering configuration permits on-premises dynamic routes learned by Cloud Router in hub-vpc to be imported into spoke-vpc.roles/resourcemanager.tagUser), preventing unauthorized VM tagging by local project administrators.Native custom route exchange and custom BGP advertisements eliminate latency overhead and maintenance burdens associated with Network Virtual Appliances (NVAs), while secure Resource Manager Tags provide the only native mechanism in Google Cloud network firewall policies to identify source workloads across VPC peering boundaries.
spoke-vpc VM instances, reference those service accounts as source service accounts in hub-vpc firewall rules, and set dynamic routing mode to global in hub-vpc without custom advertisements.This option attempts to use Service Account filtering in VPC firewall rules to establish workload identity and relies on Global Dynamic Routing in hub-vpc to automatically propagate routes between on-premises environments and peered networks.
hub-vpc firewall rules cannot identify or match traffic from service accounts attached to VMs in spoke-vpc.The workloads were located within the same Shared VPC network where service accounts can be evaluated uniformly across host and service projects.
Service account filtering in Google Cloud firewall rules is an effective security measure for micro-segmentation within a single VPC or Shared VPC, but it cannot span VPC Network Peering connections.
constraints/compute.restrictDedicatedInterconnectUsage to authorize spoke-vpc, enable default subnet route exchange, and apply hierarchical firewall rules using destination IP matching.This option uses the Organization Policy constraint constraints/compute.restrictDedicatedInterconnectUsage to regulate Cloud Interconnect attachments, while relying on static destination IP matching in hierarchical firewall policies for security enforcement.
constraints/compute.restrictDedicatedInterconnectUsage restricts which VPC networks can create VLAN attachments for Cloud Interconnect; it does not configure BGP route advertisements or route table propagation between peered VPCs.spoke-vpc subnets across the Cloud Interconnect connection.The primary objective was to enforce an organization-wide governance restriction preventing development teams from provisioning unauthorized VLAN attachments directly inside spoke-vpc.
Organization policy constraints enforce governance boundaries during resource creation, whereas dynamic routing and traffic filtering require data plane configurations on Cloud Routers, VPC peering links, and firewall policies.
spoke-vpc as source tags in hub-vpc VPC firewall rules.This approach attempts to use standard dynamic route propagation with default VPC peering route exchange settings, while using Compute Engine network tags (metadata strings) for source-based traffic filtering in hub-vpc VPC firewall rules.
hub-vpc cannot resolve network tags assigned to VM instances in spoke-vpc.spoke-vpc CIDRs over Cloud Interconnect to on-premises systems, leaving on-premises hosts without reachability to spoke-vpc.All communicating virtual machines resided entirely within the same VPC network and did not require cross-VPC or hybrid route propagation.
Organizations must distinguish between Compute Engine network tags (ephemeral instance metadata) and Resource Manager Tags (strongly typed, IAM-governed resources that work across VPC peering for network firewall policy source evaluation).
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 Validated