You created a VPC network named Retail in auto mode. You want to create a VPC network named Distribution and peer it with the Retail VPC.
How should you configure the Distribution VPC?

• A.Create the Distribution VPC in auto mode. Peer both the VPCs via network peering.
• B.Create the Distribution VPC in custom mode. Use the CIDR range 10.128.0.0/9. Create the necessary subnets, and then peer them via network peering.
• C.Create the Distribution VPC in custom mode. Use the CIDR range 10.0.0.0/9. Create the necessary subnets, and then peer them via network peering.
• D.Rename the default VPC as "Distribution" and peer it via network peering.

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 iam.serviceAccountUser to your user account.
• C.Grant the read-only privilege to the service account for the Cloud Storage bucket.
• D.Grant the cloud-platform privilege to the service account for the Cloud Storage bucket.

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

You are increasing your usage of Cloud VPN between on-premises and GCP, and you want to support more traffic than a single tunnel can handle. You want to increase the available bandwidth using Cloud VPN.
What should you do?

• A.Double the MTU on your on-premises VPN gateway from 1460 bytes to 2920 bytes.
• B.Create two VPN tunnels on the same Cloud VPN gateway that point to the same destination VPN gateway IP address.
• C.Add a second on-premises VPN gateway with a different public IP address. Create a second tunnel on the existing Cloud VPN gateway that forwards the same IP range, but points at the new on-premises gateway IP.
• D.Add a second Cloud VPN gateway in a different region than the existing VPN gateway. Create a new tunnel on the second Cloud VPN gateway that forwards the same IP range, but points to the existing on-premises VPN gateway IP address.

Comment: *

Name: *

Email: *

Verification: *

A database virtual machine on Google Compute Engine has an ext4-formatted persistent disk for data files. The database is about to run out of storage space How can you remediate the problem with the least amount of downtime?

• A.In the Cloud Platform Console, increase the size of the persistent disk and use the resize2fs command in Linux.
• B.Shut down the virtual machine, use the Cloud Platform Console to increase the persistent disk size, then restart the virtual machine.
• C.In the Cloud Platform Console, increase the size of the persistent disk and verify the new space is ready to use with the fdisk command in Linux.
• D.In the Cloud Platform Console, create a new persistent disk attached to the virtual machine, format and mount it, and configure the database service to move the files to the new disk.
• E.In the Cloud Platform Console, create a snapshot of the persistent disk, restore the snapshot to a new larger disk, unmount the old disk, mount the new disk, and restart the database service.

Comment: *

Name: *

Email: *

Verification: *