Free Google Professional-Cloud-Network-Engineer Exam Dumps Questions & Answers

Your company is planning a migration to Google Kubernetes Engine. Your application team informed you that they require a minimum of 60 Pods per node and a maximum of 100 Pods per node Which Pod per node CIDR range should you use?

• A./25
• B./24
• C./26
• D./28

You are designing a hybrid cloud environment for your organization. Your Google Cloud environment is interconnected with your on-premises network using Cloud HA VPN and Cloud Router. The Cloud Router is configured with the default settings. Your on-premises DNS server is located at 192.168.20.88 and is protected by a firewall, and your Compute Engine resources are located at 10.204.0.0/24. Your Compute Engine resources need to resolve on-premises private hostnames using the domain corp.altostrat.com while still resolving Google Cloud hostnames. You want to follow Google-recommended practices. What should you do?

• A.Create a private forwarding zone in Cloud DNS for 'corp .altostrat.com' called corp-altostrat-com that points to 192.168.20.88.
  Configure your on-premises firewall to accept traffic from 10.204.0.0/24.
  Modify the /etc/resolv conf file on your Compute Engine instances to point to 192.168.20 88
• B.Create a private zone in Cloud DNS for 'corp altostrat.com' called corp-altostrat-com.
  Configure DNS Server Policies and create a policy with Alternate DNS servers to 192.168.20.88.
  Configure your on-premises firewall to accept traffic from 35.199.192.0/19.
  Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.
• C.Create a private forwarding zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com that points to 192.168.20.88.
  Configure your on-premises firewall to accept traffic from 10.204.0.0/24.
  Set a custom route advertisement on the Cloud Router for 10.204.0.0/24
• D.Create a private forwarding zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com that points to 192.168 20.88.
  Configure your on-premises firewall to accept traffic from 35.199.192.0/19 Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.

Question:
Your organization has a hub and spoke architecture with VPC Network Peering, and hybrid connectivity is centralized at the hub. The Cloud Router in the hub VPC is advertising subnet routes, but the on-premises router does not appear to be receiving any subnet routes from the VPC spokes. You need to resolve this issue.
What should you do?

• A.Create custom routes at the Cloud Router in the spokes to advertise the subnets of the VPC spokes.
• B.Create a BGP route policy at the Cloud Router, and ensure the subnets of the VPC spokes are being announced towards the on-premises environment.
• C.Create custom routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes.
• D.Create custom learned routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes.

You are deploying an HA VPN within Google Cloud. You need to exchange routes dynamically between your on-premises gateway and Google Cloud. You have already created an HA VPN gateway and a peer VPN gateway resource. What should you do?

• A.Create a Cloud Router, add VPN tunnels, and then configure static routes to your subnet ranges.
• B.Create a Cloud Router, add VPN tunnels, and enable global dynamic routing.
• C.Create a second HA VPN gateway, add VPN tunnels, and enable global dynamic routing.
• D.Create a Cloud Router, add VPN tunnels, and then configure BGP sessions.

You are developing an HTTP API hosted on a Compute Engine virtual machine instance that must be invoked only by multiple clients within the same Virtual Private Cloud (VPC). You want clients to be able to get the IP address of the service. What should you do?

• A.Ensure that clients use Compute Engine internal DNS by connecting to the instance name with the url
  https://[INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal/.
• B.Ensure that clients use Compute Engine internal DNS by connecting to the instance name with the url
  https://[API_NAME]/[API_VERSION]/.
• C.Reserve a static external IP address and assign it to an HTTP(S) load balancing service's forwarding rule. Clients should use this IP address to connect to the service.
• D.Reserve a static external IP address and assign it to an HTTP(S) load balancing service's forwarding rule. Then, define an A record in Cloud DNS. Clients should use the name of the A record to connect to the service.