Google Professional Cloud Network Engineer Practice Test 59
Question 580
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A data center needs to query a Cloud DNS private zone but engineers configure only outbound forwarding and no supported inbound query entry point. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Identify producer service eligibility, consumer VPC, internal endpoint or allocated peering range, route and DNS needs, and serverless egress settings.
- Add DNS forwarding to a private IP and assume it can be reached across an absent VPN or Interconnect route.
- Check: Trace queries, forwarding target IP and region, Cloud Router routes, incoming DNS policy and resolver response path.
- Change: Configure supported outbound forwarding zones, inbound DNS server policies and required hybrid return routes with permitted target resolvers.
- Change: Compare Direct Peering and the Verified Peering Provider program for Google public-service network performance while using private connectivity products for private VPC access.
Explanation
Correct Answer
C:Hybrid resolution depends on the direction of queries and network reachability to forwarding targets, not solely on matching zone suffixes. Required intervention: Configure supported outbound forwarding zones, inbound DNS server policies and required hybrid return routes with permitted target resolvers.
D:Hybrid resolution depends on the direction of queries and network reachability to forwarding targets, not solely on matching zone suffixes. Evidence: Trace queries, forwarding target IP and region, Cloud Router routes, incoming DNS policy and resolver response path.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Managed service private connectivity selection) rather than the documented Cloud DNS forwarding to on-premises resolvers decision.
B:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Hybrid resolution depends on the direction of queries and network reachability to forwarding targets, not solely on matching zone suffixes.
E:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Direct Peering versus Verified Peering Provider planning) rather than the documented Cloud DNS forwarding to on-premises resolvers decision.
Question 581
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: An app hostname must resolve to a private IP inside the corporate VPC and a public frontend externally, but the team places both answers in one global public zone. An unsafe shortcut would be: Put private database IP records into the public DNS zone to make external clients see the same answer as internal VMs. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution.
- Put private database IP records into the public DNS zone to make external clients see the same answer as internal VMs.
- Design supported cache keys and response cache policies that include real representation variation while excluding private content from shared caching.
- Configure eligible Cross-Cloud Interconnect connectivity and VLAN attachments with both clouds' route, security and redundancy requirements explicitly integrated.
Explanation
Correct Answer
A:Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Incorrect Answers
B:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy. For this best change assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it.
C:Design supported cache keys and response cache policies that include real representation variation while excluding private content from shared caching. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
D:Configure eligible Cross-Cloud Interconnect connectivity and VLAN attachments with both clouds' route, security and redundancy requirements explicitly integrated. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Question 582
A Google Cloud network infrastructure review finds: An app hostname must resolve to a private IP inside the corporate VPC and a public frontend externally, but the team places both answers in one global public zone. The team proposes: Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- Managed instance groups govern VM fleet scaling while network endpoint groups represent supported specific endpoints; load balancing does not automatically scale arbitrary backends.
- Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
- Pod CIDR growth and cluster DNS are distinct GKE networking functions; correct secondary allocation and DNS topology must be validated separately.
- GKE control-plane reachability is governed by endpoint type, network path and authorization; merely configuring an allowed CIDR does not substitute for identity.
Explanation
Correct Answer
B:Demonstrable success requires: Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints.
Incorrect Answers
A:Managed instance groups govern VM fleet scaling while network endpoint groups represent supported specific endpoints; load balancing does not automatically scale arbitrary backends. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
C:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (GKE additional Pod ranges and DNS integration) rather than the documented Split-horizon DNS public and private answers decision.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Private GKE control plane and DNS endpoint configuration) rather than the documented Split-horizon DNS public and private answers decision.
Question 583
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: An app hostname must resolve to a private IP inside the corporate VPC and a public frontend externally, but the team places both answers in one global public zone. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Compare request host/path/query, Cache-Control, authorization context, cache hit logs and outputs from different test identities.
- Compare edge availability domains, colocation or metro locations, attachments, Cloud Router pairing and controlled failure scenarios against official topology criteria.
- Compare public delegation, private zone authorizations, overlapping record sets, source resolver and observed responses from both network contexts.
- Compare routing-policy record sets, health status, resolver geography, TTL and observed answers during simulated backend failure.
Explanation
Correct Answer
C:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Incorrect Answers
A:Compare request host/path/query, Cache-Control, authorization context, cache hit logs and outputs from different test identities. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Interconnect service availability architecture 99.9 versus 99.99) rather than the documented Split-horizon DNS public and private answers decision.
D:Compare routing-policy record sets, health status, resolver geography, TTL and observed answers during simulated backend failure. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Question 584
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: An app hostname must resolve to a private IP inside the corporate VPC and a public frontend externally, but the team places both answers in one global public zone. The accountable service owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the network response meets the intended outcome? Select ONE best answer.
- Supported traffic reaches the intended healthy backend with the required packet or HTTP semantics and no unavailable L7 feature assumptions.
- Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints.
- Representative malicious application traffic triggers expected inspection while approved traffic remains functional under documented exceptions.
- BGP and route selection operate as intended for authorized prefixes and no unrelated route policy is broadened.
Explanation
Correct Answer
B:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Load balancer architecture choice) rather than the documented Split-horizon DNS public and private answers decision.
C:Representative malicious application traffic triggers expected inspection while approved traffic remains functional under documented exceptions. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
D:BGP and route selection operate as intended for authorized prefixes and no unrelated route policy is broadened. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Question 585
A production Google Cloud networking change review identifies the following problem: An app hostname must resolve to a private IP inside the corporate VPC and a public frontend externally, but the team places both answers in one global public zone. Which paired Google Cloud networking action and verification should close the review? Select ONE best answer.
- Change: Configure the appropriate protocol-specific health check and allow legitimate health-check and proxy sources to reach the correct serving port under supported firewall rules. Verify: Inspect health-check source and destination, configured port/protocol, VM firewall logs, backend status and a controlled successful probe.
- Change: Review Cloud NAT allocation, port-utilization metrics and translation/error logs, then adjust supported address or port capacity for actual demand. Verify: Compare NAT gateway metrics, allocated versus needed ports, error logs, instance activity, source endpoints and test connection rates.
- Change: Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution. Verify: Compare public delegation, private zone authorizations, overlapping record sets, source resolver and observed responses from both network contexts.
- Change: Configure supported cross-project private-zone binding or Cloud DNS peering according to zone ownership and approved consumer networks. Verify: Inspect zone ownership, bound networks, peering zone targets, IAM for binding and queries originating in each VPC.
Explanation
Correct Answer
C:This pair links the appropriate network response with evidence of the underlying cloud networking issue. Applied case: An app hostname must resolve to a private IP inside the corporate VPC and a public frontend externally, but the team places both answers in one global public zone.
Incorrect Answers
A:Change: Configure the appropriate protocol-specific health check and allow legitimate health-check and proxy sources to reach the correct serving port under supported firewall rules.
B:Change: Review Cloud NAT allocation, port-utilization metrics and translation/error logs, then adjust supported address or port capacity for actual demand.
D:Change: Configure supported cross-project private-zone binding or Cloud DNS peering according to zone ownership and approved consumer networks. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Question 586
A Google Cloud Professional Network Engineer is reviewing this Google Cloud networking environment scenario: A developer's laptop on the public internet unexpectedly receives no response for a private Cloud DNS record and asks to publish the internal instance address. An unsafe shortcut would be: Put private database IP records into the public DNS zone to make external clients see the same answer as internal VMs. What should the cloud network administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution.
- Map actual NCC and VPC route propagation and nontransitive boundaries; use supported spokes or Private NAT and appropriate filters to meet required connectivity.
- Put private database IP records into the public DNS zone to make external clients see the same answer as internal VMs.
- Design regional or multiregional backends, health-based traffic direction, state recovery and tested failure behavior appropriate to the required recovery objectives.
Explanation
Correct Answer
A:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Incorrect Answers
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (NCC transitivity and overlapping topology pitfalls) rather than the documented Split-horizon DNS public and private answers decision.
C:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy. Use this instead: Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Regional redundancy and disaster recovery design) rather than the documented Split-horizon DNS public and private answers decision.
Question 587
A Google Cloud network infrastructure review finds: A developer's laptop on the public internet unexpectedly receives no response for a private Cloud DNS record and asks to publish the internal instance address. The team proposes: Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution. Which Google Cloud networking technical principle most strongly supports the proposed response? Select ONE best answer.
- HTTP request routing decisions belong to supported L7 URL map and traffic management configuration, not to arbitrary DNS changes or L4 forwarding rules.
- Hybrid access products have different physical/partner dependencies, performance envelopes and encryption behavior; the correct architecture depends on workload constraints.
- Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
- Redundant connectivity objects only deliver resilience when their route and failure-domain interactions are valid under actual removal of a component.
Explanation
Correct Answer
C:Demonstrable success requires: Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints. This principle explains the proposed network response, which is: Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution.
Incorrect Answers
A:HTTP request routing decisions belong to supported L7 URL map and traffic management configuration, not to arbitrary DNS changes or L4 forwarding rules. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
B:Hybrid access products have different physical/partner dependencies, performance envelopes and encryption behavior; the correct architecture depends on workload constraints. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
D:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (HA VPN/Interconnect route failover and recovery proof) rather than the documented Split-horizon DNS public and private answers decision.
Question 588
The cloud network operations team has not approved a broad network-wide change. Available evidence indicates: A developer's laptop on the public internet unexpectedly receives no response for a private Cloud DNS record and asks to publish the internal instance address. Which evidence best tests the Google Cloud networking diagnosis before approving a disruptive change? Select ONE best answer.
- Compare route tables, prefixes and priorities, BGP learned paths, next-hop health, firewall policy and observed packet forwarding.
- Compare public delegation, private zone authorizations, overlapping record sets, source resolver and observed responses from both network contexts.
- Review zone type, NS delegation, complete record inventory, TTLs, authorized networks and both public and private DNS queries.
- Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests.
Explanation
Correct Answer
B:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy. Confirm afterward that: Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints.
Incorrect Answers
A:Compare route tables, prefixes and priorities, BGP learned paths, next-hop health, firewall policy and observed packet forwarding. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
C:Review zone type, NS delegation, complete record inventory, TTLs, authorized networks and both public and private DNS queries. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
D:Compare announced routes, filter conditions, import/export status, effective spoke route tables and permit/deny reachability tests. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Question 589
A candidate network change has been piloted and stakeholders require a post-change acceptance check. Original problem: A developer's laptop on the public internet unexpectedly receives no response for a private Cloud DNS record and asks to publish the internal instance address. The accountable service owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the network response meets the intended outcome? Select ONE best answer.
- Backends register healthily and scale or fail over according to supported configuration under realistic demand.
- Each workload uses a valid regional subnet and intended regional or global connectivity without relying on nonexistent cross-region subnet attachment.
- Unhealthy peers are detected within the planned interval and alternative paths receive traffic without flapping healthy links.
- Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints.
Explanation
Correct Answer
D:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Incorrect Answers
A:Backends register healthily and scale or fail over according to supported configuration under realistic demand. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
B:This option addresses a different Google Cloud Professional Cloud Network Engineer secure networking topic (Global VPC versus regional resource locality) rather than the documented Split-horizon DNS public and private answers decision.
C:Unhealthy peers are detected within the planned interval and alternative paths receive traffic without flapping healthy links. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
Question 590
For an original Google Cloud Professional Cloud Network Engineer educational scenario, consider: A developer's laptop on the public internet unexpectedly receives no response for a private Cloud DNS record and asks to publish the internal instance address. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare public delegation, private zone authorizations, overlapping record sets, source resolver and observed responses from both network contexts.
- Change: Configure the appropriate protocol-specific health check and allow legitimate health-check and proxy sources to reach the correct serving port under supported firewall rules.
- Put private database IP records into the public DNS zone to make external clients see the same answer as internal VMs.
- Change: Configure public and private zones with the intended shared domain name and approved VPC-specific record visibility for split-horizon resolution.
- Check: Compare required security capabilities, selected NGFW tier, enabled policy services, support or enrollment and attack simulation logs.
Explanation
Correct Answer
A:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy. Acceptance: Internal callers reach private endpoints while external callers resolve only sanctioned public endpoints.
D:Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy. Evidence: Compare public delegation, private zone authorizations, overlapping record sets, source resolver and observed responses from both network contexts.
Incorrect Answers
B:Change: Configure the appropriate protocol-specific health check and allow legitimate health-check and proxy sources to reach the correct serving port under supported firewall rules. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
C:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.
E:Check: Compare required security capabilities, selected NGFW tier, enabled policy services, support or enrollment and attack simulation logs. Split-horizon DNS returns different authorized answers based on resolver network visibility; a private zone need not be exposed to the public DNS hierarchy.