Your on-premises data center has 2 routers connected to your Google Cloud environment through a VPN on each router. All applications are working correctly; however, all of the traffic is passing across a single VPN instead of being load-balanced across the 2 connections as desired.
During troubleshooting you find:
* Each on-premises router is configured with a unique ASN.
* Each on-premises router is configured with the same routes and priorities.
* Both on-premises routers are configured with a VPN connected to a single Cloud Router.
* BGP sessions are established between both on-premises routers and the Cloud Router.
* Only 1 of the on-premises router's routes are being added to the routing table.
What is the most likely cause of this problem?

• A.The ASNs being used on the on-premises routers are different.
• B.You do not have a load balancer to load-balance the network traffic.
• C.A firewall is blocking the traffic across the second VPN connection.
• D.The on-premises routers are configured with the same routes.

Comment: *

Name: *

Email: *

Verification: *

Your end users are located in close proximity to us-east1 and europe-west1. Their workloads need to communicate with each other. You want to minimize cost and increase network efficiency.
How should you design this topology?

• A.Create 2 VPCs, each with their own regions and individual subnets. Create 2 VPN gateways to establish connectivity between these regions.
• B.Create 2 VPCs, each with their own region and individual subnets. Use external IP addresses on the instances to establish connectivity between these regions.
• C.Create 1 VPC with 2 regional subnets. Create a global load balancer to establish connectivity between the regions.
• D.Create 1 VPC with 2 regional subnets. Deploy workloads in these subnets and have them communicate using private RFC1918 IP addresses.

Comment: *

Name: *

Email: *

Verification: *

All the instances in your project are configured with the custom metadata enable-oslogin value set to FALSE and to block project-wide SSH keys. None of the instances are set with any SSH key, and no project-wide SSH keys have been configured. Firewall rules are set up to allow SSH sessions from any IP address range. You want to SSH into one instance.
What should you do?

• A.Open the Cloud Shell SSH into the instance using gcloud compute ssh.
• B.Set the custom metadata enable-oslogin to TRUE, and SSH into the instance using a third-party tool like putty or ssh.
• C.Generate a new SSH key pair. Verify the format of the private key and add it to the instance.
  SSH into the instance using a third-party tool like putty or ssh.
• D.Generate a new SSH key pair. Verify the format of the public key and add it to the project.
  SSH into the instance using a third-party tool like putty or ssh.

Comment: *

Name: *

Email: *

Verification: *

You are adding steps to a working automation that uses a service account to authenticate. You need to drive the automation the ability to retrieve files from a Cloud Storage bucket. Your organization requires using the least privilege possible.
What should you do?

• A.Grant the compute.instanceAdmin to your user account.
• B.Grant the read-only privilege to the service account for the Cloud Storage bucket.
• C.Grant the cloud-platform privilege to the service account for the Cloud Storage bucket.
• D.Grant the iam.serviceAccountUser to your user account.

Comment: *

Name: *

Email: *

Verification: *

Your company has just launched a new critical revenue-generating web application. You deployed the application for scalability using managed instance groups, autoscaling, and a network load balancer as frontend. One day, you notice severe bursty traffic that the caused autoscaling to reach the maximum number of instances, and users of your application cannot complete transactions. After an investigation, you think it as a DDOS attack. You want to quickly restore user access to your application and allow successful transactions while minimizing cost.
Which two steps should you take? (Choose two.)

• A.Shut down the entire application in GCP for a few hours. The attack will stop when the application is offline.
• B.Create a global HTTP(s) load balancer and move your application backend to this load balancer.
• C.SSH into the backend compute engine instances, and view the auth logs and syslogs to further understand the nature of the attack.
• D.Use Cloud Armor to blacklist the attacker's IP addresses.
• E.Increase the maximum autoscaling backend to accommodate the severe bursty traffic.

Comment: *

Name: *

Email: *

Verification: *