You configured a single IPSec Cloud VPN tunnel for your organization to a third-party customer. You confirmed that the VPN tunnel is established; however, the BGP session status states that BGP is not configured. The customer has provided you with their BGP settings:
* Local BGP address: 169.254.11.1/30
* Local ASN: 64515
* Peer BGP address: 169.254.11.2
* Peer ASN: 64517
* Base MED: 1000
* MD5 Authentication: Disabled
You need to configure the local BGP session for this tunnel based on the settings provided by the customer.
You already associated the Cloud Router with the Cloud VPN Tunnel. What settings should you use for the BGP session?

• A.Peer ASN: 64517
  Advertised Route Priority (MED): 100
  Local BGP IP: 169.254.11.2
  Peer BGP IP: 169.254.11.1
  MD5 Authentication: Disabled
• B.Peer ASN: 64515
  Advertised Route Priority (MED): 100
  Local BGP IP: 169.254.11.2
  Peer BGP IP: 169.254.11.1
  MD5 Authentication: Disabled
• C.Peer ASN: 64515
  Advertised Route Priority (MED): 1000
  Local BGP IP: 169.254.11.2
  Peer BGP IP: 169.254.11.1
  MD5 Authentication: Enabled
• D.Peer ASN: 64515
  Advertised Route Priority (MED): 100
  Local BGP IP: 169.254.11.1
  Peer BGP IP: 169.254.11.2
  MD5 Authentication: Disabled

Comment: *

Name: *

Email: *

Verification: *

You decide to set up Cloud NAT. After completing the configuration, you find that one of your instances is not using the Cloud NAT for outbound NAT.
What is the most likely cause of this problem?

• A.You have created static routes that use RFC1918 ranges.
• B.An external IP address has been configured on the instance.
• C.The instance is accessible by a load balancer external IP address.
• D.The instance has been configured with multiple interfaces.

Comment: *

Name: *

Email: *

Verification: *

You are using the gcloud command line tool to create a new custom role in a project by coping a predefined role. You receive this error message:
INVALID_ARGUMENT: Permission resourcemanager.projects.list is not valid What should you do?

• A.Remove the resourcemanager.projects.list permission, and try again.
• B.Try again with a different role with a new name but the same permissions.
• C.Add the resourcemanager.projects.get permission, and try again.
• D.Add the resourcemanager.projects.setIamPolicy permission, and try again.

Comment: *

Name: *

Email: *

Verification: *

You are the Organization Admin for your company. One of your engineers is responsible for setting up multiple host projects across multiple folders and sharing subnets with service projects. You need to enable the engineer's Identity and Access Management (IAM) configuration to complete their task in the fewest number of steps. What should you do?

• A.Set up the engineer with Compute Shared VPC Admin IAM role at the organization level.
• B.Set up the engineer with Compute Shared VPC Admin IAM role at the folder level.
• C.Set up the engineer with Compute Shared VPC Admin IAM role and Project IAM Admin role at the organization level.
• D.Set up the engineer with Compute Shared VPC Admin IAM role and Project IAM Admin role at the folder level.

Comment: *

Name: *

Email: *

Verification: *

You are designing a hybrid cloud environment. Your Google Cloud environment is interconnected with your on-premises network using HA VPN and Cloud Router in a central transit hub VPC. The Cloud Router is configured with the default settings. Your on-premises DNS server is located at 192.168.20.88. You need to ensure that your Compute Engine resources in multiple spoke VPCs can resolve on-premises private hostnames using the domain corp.altostrat.com while also 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. Associate the zone with the hub VPC.
  Create a private peering zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com associated with the spoke VPCs, with the hub VPC as the target.
  Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.
  Create a hub-and-spoke VPN deployment in each spoke VPC to connect back to the on-premises network directly.
• B.Create a private forwarding zone in Cloud DNS for 'corp altostrat.com' called corp-altostrat-com that points to 192. 168.20.88. Associate the zone with the hub VPC.
  Create a private peering zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com associated with the spoke VPCs, with the hub VPC as the target.
  Sat a custom route advertisement on the Cloud Router for 35.199.192.0/19.
  Create a hub and spoke VPN deployment in each spoke VPC to connect back to the hub VPC.
• C.Create a private forwarding zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com that points to 192.168.20.88.
  Associate the zone with the hub VPC. Create a private peering zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com associated with the spoke PCs, with the hub VPC as the target.
  Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.
• D.Create a private forwarding zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com that points to 192.168.20.88. Associate the zone with the hub VPC.
  Create a private peering zone in Cloud DNS for 'corp.altostrat.com' called corp-altostrat-com associated with the spoke VPCs, with the hub VPC as the target.
  Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.
  Configure VPC peering in the spoke VPCs to peer with the hub VPC.

Comment: *

Name: *

Email: *

Verification: *