You want to deploy a VPN Gateway to connect your on-premises network to GCP. You are using a non BGP- capable on-premises VPN device. You want to minimize downtime and operational overhead when your network grows. The device supports only IKEv2, and you want to follow Google-recommended practices.
What should you do?

• A.* Create a Cloud VPN instance.
  * Create a policy-based VPN tunnel per subnet.
  * Configure the appropriate local and remote traffic selectors to match your local and remote networks.
  * Create the appropriate static routes.
• B.* Create a Cloud VPN instance.
  * Create a policy-based VPN tunnel.
  * Configure the appropriate local and remote traffic selectors to match your local and remote networks.
  * Configure the appropriate static routes.
• C.* Create a Cloud VPN instance.
  * Create a route-based VPN tunnel.
  * Configure the appropriate local and remote traffic selectors to match your local and remote networks.
  * Configure the appropriate static routes.
• D.* Create a Cloud VPN instance.
  * Create a route-based VPN tunnel.
  * Configure the appropriate local and remote traffic selectors to 0.0.0.0/0.
  * Configure the appropriate static routes.

Comment: *

Name: *

Email: *

Verification: *

You are configuring a new instance of Cloud Router in your Organization's Google Cloud environment to allow connection across a new Dedicated Interconnect to your data center Sales, Marketing, and IT each have a service project attached to the Organization's host project.
Where should you create the Cloud Router instance?

• A.VPC network in all projects
• B.VPC network in the Host Project
• C.VPC network in the Sales, Marketing, and IT Projects
• D.VPC network in the IT Project

Comment: *

Name: *

Email: *

Verification: *

Your organization recently created a sandbox environment for a new cloud deployment. To have parity with the production environment, a pair of Compute Engine instances with multiple network interfaces (NICs) were deployed. These Compute Engine instances have a NIC in the Untrusted VPC (10.0.0.0/23) and a NIC in the Trusted VPC (10.128.0.0/9). A HA VPN tunnel has been established to the on-premises environment from the Untrusted VPC. Through this pair of VPN tunnels, the on-premises environment receives the route advertisements for the Untrusted and Trusted VPCs. In return, the on-premises environment advertises a number of CIDR ranges to the Untrusted VPC. However, when you tried to access one of the test services from the on-premises environment to the Trusted VPC, you received no response. You need to configure a highly available solution to enable the on-premises users to connect to the services in the Trusted VPC. What should you do?

• A.Add both multi-NIC VMs to a new unmanaged instance group, named nva-uig.
  Create an internal passthrough Network Load Balancer in the Untrusted VPC, named ilb-untrusted, with the nva-uig unmanaged instance group designated as the backend.
  Create a custom static route in the Untrusted VPC for destination 10.123.0.0/9 and the next hop ilb- untrusted.
  Create an internal passthrough Network Load Balancer in the Trusted VPC, named ilb-trusted, with the nva-uig unmanaged instance group designated as the backend.
  Create a custom static route in the Trusted VPC for destination 0.0.0.0/0 and the next hop ilb-trusted.
• B.Add both multi-NIC VMs to a new unmanaged instance group, named nva-uig.
  Create an internal passthrough Network Load Balancer in the Untrusted VPC, named ilb-untrusted, with the nva-uig unmanaged instance group designated as the backend.
  Create a custom static route in the Untrusted VPC for destination 10.128.0.0/9 and the next hop ilb- untrusted.
  Create an internal passthrough Network Load Balancer in the Trusted VPC, named ilb-trusted, with the nva-uig unmanaged instance group designated as the backend.
  Create a custom static route in the Trusted VPC for destination 10.0.0.0/23 and the next hop ilb-trusted.
• C.Add both multi-NIC VMs to a new unmanaged instance group, named nva-uigO.
  Create an internal passthrough Network Load Balancer in the Untrusted VPC, named ilb-untrusted, with the nva-uigO as backend.
  Create a custom static route in the Untrusted VPC for destination 10.128.0.0/9 and the next hop ilb- untrusted.
  Add both multi-NIC VMs to a new unmanaged instance group, named nva-uigl.
  Create an internal passthrough Network Load Balancer in the Trusted VPC, named ilb-trusted, with the nva-uigl as backend.
  Create a custom static route in the Trusted VPC for destination 0.0.0.0/0 and the next hop ilb-trusted.
• D.Add both multi-NIC VMs to a new unmanaged instance group, named nva-uig.
  Create two custom static routes in the Untrusted VPC for destination 10.128.0.0/9 and set each of the VMs' NIC as the next hop.
  Create two custom static routes in the Trusted VPC for destination 10.0.0.0/23 and set each of the VMs' NIC as the next hop.

Comment: *

Name: *

Email: *

Verification: *

You need to configure a Google Kubernetes Engine (GKE) cluster. The initial deployment should have 5 nodes with the potential to scale to 10 nodes. The maximum number of Pods per node is 8. The number of services could grow from 100 to up to 1024. How should you design the IP schema to optimally meet this requirement?

• A.Configure a /28 primary IP address range for the node IP addresses. Configure a /28 secondary IP range for the Pods. Configure a /21 secondary IP range for the Services.
• B.Configure a /28 primary IP address range for the node IP addresses. Configure a /24 secondary IP range for the Pads. Configure a /22 secondary IP range for the Services.
• C.Configure a /28 primary IP address range for the node IP addresses. Configure a (25 secondary IP range for the Pods. Configure a /22 secondary IP range for the Services.
• D.Configure a /28 primary IP address range for the node IP addresses. Configure a /25 secondary IP range for the Pods. Configure a /21 secondary IP range for the Services.

Comment: *

Name: *

Email: *

Verification: *

You have deployed a proof-of-concept application by manually placing instances in a single Compute Engine zone. You are now moving the application to production, so you need to increase your application availability and ensure it can autoscale.
How should you provision your instances?

• A.Create an unmanaged instance group for each zone, and manually distribute the instances across the desired zones.
• B.Create a managed instance group for each region, select Single zone for the location, and manually distribute instances across the zones in that region.
• C.Create a single managed instance group, specify the desired region, and select Multiple zones for the location.
• D.Create an unmanaged instance group in a single zone, and then create an HTTP load balancer for the instance group.

Comment: *

Name: *

Email: *

Verification: *