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 operates a hub-and-spoke topology across multiple Google Cloud projects. The hub project hosts private managed DNS zones for centralized internal microservices. The security team has defined the following requirements for all spoke VPC networks:
Which combination of Cloud DNS security and architecture controls should the security engineer deploy?
This option involves duplicating all private DNS zones inside every spoke VPC project, using VPC Firewall Rules to filter domain names, and granting the roles/dns.reader role on the hub project.
roles/dns.reader provides read-only permissions (dns.managedZones.get, dns.managedZones.list, dns.resourceRecordSets.get, etc.), which does not allow spoke service accounts to establish DNS peering linkages to the hub network (dns.networks.bindDNSResponsePolicy or dns.networks.targetWithPeeringZone).Each spoke project operated as an entirely autonomous, disconnected entity with static records and no need for dynamic cross-VPC DNS resolution or centralized security controls.
Cloud DNS Peering Zones, DNS Response Policies (RPZ), and the DNS Peer role (roles/dns.peer) provide a secure, scalable framework for centralized name resolution, granular traffic redirection, and least-privilege administrative access across multi-project Google Cloud environments.
A Cloud DNS peering zone is a private zone configured in a consumer network (the spoke VPC) that forwards DNS queries for a given namespace to a producer network (the hub VPC). This allows instances in spoke VPCs to query private records hosted centrally in the hub network without needing VPC network peering at the data plane or duplicating zone records across spoke projects.
Cloud DNS Response Policies act as a response policy zone (RPZ) mechanism applied directly to VPC networks. They evaluate DNS queries before standard resolution paths:
localData, queries matching malicious or unauthorized domains are intercepted and resolved to an internal sinkhole IP address (or NXDOMAIN).--behavior=bypassResponsePolicy attribute, trusted domain lookups bypass policy matching and resolve normally through authoritative zones or upstream resolvers.The predefined roles/dns.peer (DNS Peer) role allows an identity to establish a DNS peering link pointing to a VPC network in the target project without granting permissions to view, alter, or delete individual resource record sets or private managed zones in that target project.
roles/dns.admin) segregated from network peering binding (roles/dns.peer).This option suggests using Cloud DNS Forwarding Zones aimed at the local instance metadata server (169.254.169.254), applying Google Cloud Armor security policies to inspect and block DNS lookups, and granting the roles/compute.networkAdmin IAM role.
roles/compute.networkAdmin grants broad control over Compute Engine networking resources (subnets, firewalls, routers) rather than the specific roles/dns.peer role needed for DNS peering zone creation.The requirements focused on filtering HTTP/HTTPS web application attacks (such as SQL injection or XSS) on public endpoints using Cloud Armor and managing VPC subnets.
This option relies on VPC Network Peering to exchange custom network routes, Outbound DNS Server Policies pointing to alternative nameservers for domain inspection, and granting the roles/dns.admin role to project service accounts.
35.199.192.0/19). They do not provide native Cloud DNS in-VPC response policy interception, local record overrides, or selective bypassResponsePolicy rules.roles/dns.admin gives complete administrative control over all DNS zones, record sets, and policies in the hub project, violating the principle of least privilege.roles/dns.admin permits deleting zones and modifying sensitive authoritative records.The organization required full bidirectional RFC 1918 IP routing between VPCs and offloaded all corporate DNS resolution to external physical firewalls located on-premises.
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