Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization runs multiple GKE Standard clusters in a Shared VPC service project and wants to automate DNS record management for GKE Ingress and LoadBalancer resources under app.example.com using external-dns. Your architecture must meet these requirements:
Ingress endpoints, while VPC and on-premises clients resolve internal services and selected public hostnames under app.example.com.external-dns permissions to its dedicated zones while preserving isolated *.cluster.local discovery inside each cluster.Which configuration should you implement?
app.example.com (TTLs <= 259200 seconds, DS record at the registrar) and a cross-project-bound private zone in the service project duplicating needed public records. Enable logging via a DNS server policy in the host project, keep clusters in cluster scope, and grant external-dns zone-level IAM permissions.This design combines Cloud DNS public and private zones in a split-horizon DNS topology with cross-project binding, DNS server policies, and GKE cluster scope so that external and internal service discovery remain secure, auditable, and strictly isolated.
NXDOMAIN errors: Because Cloud DNS uses longest suffix matching and evaluates authorized private zones before public zones, any public app.example.com hostname needed by internal clients must also exist in the private app.example.com zone. Duplicating those records prevents internal clients from receiving NXDOMAIN.259200 seconds (3 days) establishes a complete cryptographic chain of trust while avoiding synchronized signature-expiration spikes.app.example.com zone while binding it to the host project's Shared VPC. Granting zone-level IAM permissions restricts external-dns strictly to those two target zones, while GKE cluster scope keeps each cluster's *.cluster.local records isolated.clouddns-controller from overwriting external-dns records.*.cluster.local without naming conflicts.It satisfies every security, compliance, and multi-cluster isolation constraint using native Cloud DNS governance boundaries without disrupting internal Kubernetes DNS.
app.example.com with DNSSEC enabled on both zones. Enable query logging directly on the private zone resource, keep GKE clusters in cluster scope, and configure external-dns to write internal Service and Ingress records into the GKE-managed gke-CLUSTER_NAME-CLUSTER_HASH-dns private zones.This approach tries to unify security, auditing, and automated record management by enabling DNSSEC on both public and private zones, turning on logging at the zone level for private DNS, and reusing the private zones automatically provisioned by Cloud DNS for GKE.
NS delegation records; DNSSEC is strictly a public zone feature for authenticating internet-facing lookups.gke-CLUSTER_NAME-CLUSTER_HASH-dns zones created for GKE cluster scope are exclusively managed by the GKE clouddns-controller. Any records written there externally or manually are unsupported and are overwritten when the controller restarts.NXDOMAIN responses when internal clients query public hostnames under the same overlapping app.example.com suffix.DNSSEC were enabled only on the public zone (with a registrar DS record), logging were enabled via a Cloud DNS server policy on the Shared VPC network, and external-dns wrote to a dedicated private managed zone rather than the GKE-managed cluster zones.
app.example.com as the shared domain, and attach a logging-enabled DNS server policy in the service project. Create a DNSSEC-enabled public zone and an overlapping private zone containing only internal records so VPC clients fall back to the public zone for external endpoints.This option attempts to extend GKE DNS across the VPC using Cloud DNS additive VPC scope, configure logging from the service project, and minimize duplication in the private zone by expecting Cloud DNS to fall back to the public zone for missing records.
app.example.com domain across multiple clusters.NXDOMAIN failures: When an authorized private zone and a public zone share the same app.example.com origin, Cloud DNS evaluates the private zone first via longest suffix matching and never falls back to the public zone. If an external hostname is omitted from the private zone, VPC clients receive an NXDOMAIN error.cluster.local inside the cluster.The clusters ran in a standalone project (not a Shared VPC service project) with unique custom domains per cluster, the logging policy were attached to the owning VPC project, and required public records were replicated in the private zone.
cluster.local as each cluster's domain, and grant external-dns the roles/dns.admin role at the host project level. Enable DNSSEC on the app.example.com public zone with a 604800-second TTL to reduce query overhead without altering the domain registrar configuration.This option attempts to expose cluster DNS across the network using Cloud DNS VPC scope, centralize automation permissions with a project-wide DNS Administrator role, and enable DNSSEC on the public zone with a 7-day (604800-second) TTL.
*.cluster.local discovery across multiple clusters in the same VPC. Moreover, VPC scope binds a response policy to the VPC network, and only one response policy can be attached to a VPC at a time.roles/dns.admin at the Shared VPC host project level violates the principle of least privilege, allowing external-dns to modify or delete unrelated host-project zones, forwarding rules, and policies.604800-second (7-day) TTL exceeds the recommended maximum of 259200 seconds (3 days) for DNSSEC-signed zones, which can cause mass synchronized cache misses when fixed-time signatures expire.NXDOMAIN behavior is unaddressed.dns.networks.bindPrivateDNSZone allow granular separation between zone record management and network binding.Clusters remained in cluster scope, external-dns received zone-level IAM permissions, a DS record were added at the registrar with TTLs at or below 259200 seconds, and a logging DNS server policy were enabled in the host project.
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