QUESTION: 77

After a network change window one of your company's applications stops working. The application uses an on-premises database server that no longer receives any traffic from the application. The database server IP address is 10.2.1.25. You examine the change request, and the only change is that 3 additional VPC subnets were created. The new VPC subnets created are 10.1.0.0/16, 10.2.0.0/16, and 10.3.1.0/24/ The on-premises router is advertising 10.0.0.0/8.

What is the most likely cause of this problem?

The less specific VPC subnet route is taking priority.
The more specific VPC subnet route is taking priority.
The on-premises router is not advertising a route for the database server.
A cloud firewall rule that blocks traffic to the on-premises database server was created during the change.

Answer(s): B

Reveal Solution Next Question

QUESTION: 78

You need to create a new VPC network that allows instances to have IP addresses in both the 10.1.1.0/24 network and the 172.16.45.0/24 network.

What should you do?

Configure global load balancing to point 172.16.45.0/24 to the correct instance.
Create unique DNS records for each service that sends traffic to the desired IP address.
Configure an alias-IP range of 172.16.45.0/24 on the virtual instances within the VPC subnet of 10.1.1.0/24.
Use VPC peering to allow traffic to route between the 10.1.0.0/24 network and the 172.16.45.0/24 network.

Answer(s): C

Reveal Solution Next Question

QUESTION: 79

You are deploying a global external TCP load balancing solution and want to preserve the source IP address of the original layer 3 payload.

Which type of load balancer should you use?

HTTP(S) load balancer
Network load balancer
Internal load balancer
TCP/SSL proxy load balancer

Answer(s): D

Explanation:

By default TCP/SSL proxy load balancer original client IP address and port information is not preserved, but it can be preserved using the PROXY protocol: https://cloud.google.com/load- balancing/docs/tcp#target-proxies https://medium.com/google-cloud/preserving-client-ips-through-google-clouds-global-tcp-and-ssl-

proxy-load-balancers-3697d76feeb1

Reference:

https://cloud.google.com/load-balancing/docs/network

Reveal Solution Next Question

QUESTION: 80

Your company has a single Virtual Private Cloud (VPC) network deployed in Google Cloud with access from your on-premises network using Cloud Interconnect. You must configure access only to Google APIs and services that are supported by VPC Service Controls through hybrid connectivity with a service level agreement (SLA) in place.
What should you do?

Configure the existing Cloud Routers to advertise the Google API's public virtual IP addresses.
Use Private Google Access for on-premises hosts with restricted.googleapis.com virtual IP addresses.
Configure the existing Cloud Routers to advertise a default route, and use Cloud NAT to translate traffic from your on-premises network.
Add Direct Peering links, and use them for connectivity to Google APIs that use public virtual IP addresses.

Answer(s): B

Reveal Solution Next Question

Free Professional Cloud Network Engineer Exam Braindumps (page: 21)

QUESTION: 77

QUESTION: 78

QUESTION: 79

Explanation:

Reference:

QUESTION: 80

Professional Cloud Network Engineer Discussions & Posts