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

Questions 16–20

1. 16foundation · easy

   What is a mesh topology in Network Connectivity Center?

   • AA topology where only on-premises networks are connected.
   • BA topology that uses a single point of failure.
   • CA topology where all spokes connect to a central hub.
   • DA topology where spokes connect directly to each other without a central hub.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Compared to a hub and spokes topology, a mesh topology generally has:

   • ALower complexity and lower scalability.
   • BLower complexity and higher scalability.
   • CHigher complexity and higher scalability.
   • DHigher complexity and lower scalability.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   Your company has an on-premises data center connected to Google Cloud via a Cloud VPN tunnel. You want to use Network Connectivity Center to allow multiple VPCs to reach the on-premises network. You have created a hub and attached a hybrid spoke for the VPN connection. You have also attached two VPCs as VPC spokes. You notice that the VPCs can communicate with each other, but they cannot reach the on-premises network. What is the most likely cause?

   • AThe VPN tunnel is not in the same project as the hub.
   • BThe VPC spokes need a Cloud Router to route traffic to the hybrid spoke.
   • CThe VPC spokes are not in the same region as the hybrid spoke.
   • DThe hybrid spoke is not advertising the on-premises CIDR ranges.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   What is the purpose of Private NAT in Network Connectivity Center?

   • ATo encrypt traffic between spokes.
   • BTo enable private IP address translation for traffic between spokes and on-premises networks.
   • CTo translate public IP addresses to private IP addresses.
   • DTo provide a public IP address for internet access.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   You have a Network Connectivity Center hub with a VPC spoke 'spoke-a' and a hybrid spoke connected to on-premises. You have applied an IP/CIDR range filter on 'spoke-a' that only advertises 10.1.0.0/24. You are troubleshooting a connectivity issue where 'spoke-a' cannot reach an on-premises server at 10.2.0.10. The on-premises network advertises 10.2.0.0/24. You have verified that the VPN tunnel is up and the Cloud Router is advertising the on-premises routes. What is the most likely cause of the issue?

   • AThe IP/CIDR range filter on 'spoke-a' is blocking the route to 10.2.0.0/24 from being received.
   • BThe on-premises network is not advertising the 10.2.0.0/24 route to the Cloud Router.
   • CThe VPC firewall rules in 'spoke-a' are blocking traffic to 10.2.0.10.
   • DThe Cloud Router on the hybrid spoke is not advertising the 10.2.0.0/24 route to the hub.
   Reveal Solution Discussion Select an answer first