A network engineer notices that traffic between two on-premises sites is taking an unintended path through Google Cloud. What is the most likely cause of this transitivity issue in Network Connectivity Center?

The on-premises routers are not advertising the correct routes to Google Cloud.

The VPN tunnels are not encrypted.

The VPC firewall rules are blocking the intended direct path.

The hub-and-spoke topology is providing transit between the two on-premises sites.

In Network Connectivity Center, what is the role of a hybrid spoke?

It provides DNS resolution for hybrid cloud environments.

It connects a VPC network to another VPC network within the same project.

It represents an on-premises network connected to Google Cloud via VPN or Interconnect.

It is a virtual appliance that inspects traffic between VPCs.

What is the primary purpose of establishing site-to-site data transfer through Network Connectivity Center?

To replace the need for a firewall in the on-premises network.

To accelerate content delivery to end users.

To enable communication between on-premises networks and Google Cloud VPC networks.

To provide a backup internet connection for the on-premises network.

You have configured Network Connectivity Center with a hybrid spoke for a VPN tunnel to your on-premises network. You need to ensure that traffic from the on-premises network can reach a Google Cloud VM in a VPC that is not directly attached to the hub. What must you do?

Create a router appliance spoke in the VPC and attach it to the hub.

Add a static route in the VPC for the on-premises subnet.

Configure the VPN tunnel to advertise the VPC subnets.

Attach the VPC to the hub as a spoke.

Your company is migrating from a legacy VPN setup to Network Connectivity Center. You have multiple VPN tunnels to the same on-premises site for redundancy. You want to use NCC to manage these tunnels. What is the correct approach?

Create a router appliance spoke for each VPN tunnel.

Use Cloud VPN with dynamic routing and skip NCC.

Create a separate hybrid spoke for each VPN tunnel and attach them all to the same hub.

Create a single hybrid spoke and add all VPN tunnels to it.

Google CloudProfessional Cloud Network Engineer

Domain 4Objective 4

4.4 Configuring Network Connectivity Center. Considerations Include: PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice Questions (Page 2)

Part of the Section 4: Configuring and implementing hybrid and multicloud network interconnectivity (~16% of the exam) domain, which accounts for ~16% of the PROFESSIONAL-CLOUD-NETWORK-ENGINEER exam.

17questions here

4free pages

4concepts

~16%of the exam

Questions 6–10

6foundation · easy
A network engineer notices that traffic between two on-premises sites is taking an unintended path through Google Cloud. What is the most likely cause of this transitivity issue in Network Connectivity Center?
Select an answer first
7foundation · easy
In Network Connectivity Center, what is the role of a hybrid spoke?
Select an answer first
8foundation · easy
What is the primary purpose of establishing site-to-site data transfer through Network Connectivity Center?
Select an answer first
9application · medium
You have configured Network Connectivity Center with a hybrid spoke for a VPN tunnel to your on-premises network. You need to ensure that traffic from the on-premises network can reach a Google Cloud VM in a VPC that is not directly attached to the hub. What must you do?
Select an answer first
10application · medium
Your company is migrating from a legacy VPN setup to Network Connectivity Center. You have multiple VPN tunnels to the same on-premises site for redundancy. You want to use NCC to manage these tunnels. What is the correct approach?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PROFESSIONAL-CLOUD-NETWORK-ENGINEER

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Google Cloud. “PROFESSIONAL-CLOUD-NETWORK-ENGINEER” is a trademark of its owner, used for identification only.