You manage a Google Cloud VPC network that has multiple Cloud VPN tunnels connecting to a single branch office for redundancy. One tunnel is a new. high-performance link, while the other is an older, less reliable link. You need to configure dynamic routing to influence how your on- premises network routes traffic, ensuring it prefers sending traffic to Google Cloud over the new, high performance tunnel. The older tunnel must remain available as a backup. What should you do?

• A. Adjust the Border Gateway Protocol (BGP) Multi-Exit Discriminator (MED) attribute advertised by the Cloud Router for the preferred VPN tunnel to a lower value.
• B. For the BGP session associated with the new tunnel, configure a higher advertised route priority (a lower numerical value) on the Cloud Router.
• C. On the Cloud Router, configure custom route advertisements to send a shorter prefix route over the new, high-performance tunnel.
• D. Configure static routes with different priorities on your on-premises router to point to the two different Cloud VPN tunnel interfaces in Google Cloud.

You are the network administrator responsible for hybrid connectivity at your organization. Your developer team wants to use Cloud SQL in the us-west1 region in your Shared VPC. You configured a Dedicated Interconnect connection and a Cloud Router in us-west1, and the connectivity between your Shared VPC and on-premises data center is working as expected. You just created the private services access connection required for Cloud SQL using the reserved IP address range and default settings. However, your developers cannot access the Cloud SQL instance from on-premises. You want to resolve the issue. What should you do?

• A. Change the VPC routing mode to global.
  Modify the VPC Network Peering connection used for Cloud SQL, and enable the import and export of routes.
• B. Change the VPC routing mode to global.
  Create a custom route advertisement in your Cloud Router to advertise the Cloud SQL IP address range.
• C. Create an additional Cloud Router in us-west2.
  Create a new Border Gateway Protocol (BGP) peering connection to your on-premises data center.
  Modify the VPC Network Peering connection used for Cloud SQL, and enable the import and export of routes.
• D. Modify the VPC Network Peering connection used for Cloud SQL, and enable the import and export of routes.
  Create a custom route advertisement in your Cloud Router to advertise the Cloud SQL IP address range.

You have provisioned a Partner Interconnect connection to extend connectivity from your on- premises data center to Google Cloud. You need to configure a Cloud Router and create a VLAN attachment to connect to resources inside your VPC. You need to configure an Autonomous System number (ASN) to use with the associated Cloud Router and create the VLAN attachment.
What should you do?

• A. Use a public Google ASN 15169.
• B. Use a 4-byte private ASN 4200000000-4294967294.
• C. Use a 2-byte private ASN 64512-65535.
• D. Use a public Google ASN 16550.

You have a storage bucket that contains two objects. Cloud CDN is enabled on the bucket, and both objects have been successfully cached.
Now you want to make sure that one of the two objects will not be cached anymore, and will always be served to the internet directly from the origin.
What should you do?

• A. Add an appropriate lifecycle rule on the storage bucket containing the two objects.
• B. Ensure that the object you don't want to be cached anymore is not shared publicly.
• C. Create a new storage bucket, and move the object you don't want to be checked anymore inside it.
  Then edit the bucket setting and enable the private attribute.
• D. Add a Cache-Control entry with value private to the metadata of the object you don't want to be cached anymore.
  Invalidate all the previously cached copies.

You are managing a containerized application environment on Google Kubernetes Engine (GKE).
You deployed a microservice with a Kubernetes service manifest that defines a named port, http- api, for its main endpoint. You are now configuring an external http(s) load balancer to expose this microservice. You need to ensure the configuration is independent of the actual port number and follows best practices. What should you do?

• A. Create a backend service that uses the GKE node instance group as its backend, and configure the named port http-apiin the backend service.
• B. Add an annotation in your Kubernetes ingress manifest to specify the http-api port number directly, and configure the backend service to use this hardcoded port number.
• C. Add an annotation to your Kubernetes service manifest to create a GCE_VM_IP network endpoint group (NEG), and configure the backend service to use this NEG.
• D. Reference the GCE_VM_IP_PORT network endpoint group (NEG) in the backend configuration that was automatically created for your Kubernetes service, and specify http-api named port for traffic.