Your company has a single Virtual Private Cloud (VPC) network deployed in Google Cloud with access from on-premises locations using Cloud Interconnect connections. Your company must be able to send traffic to Cloud Storage only through the Interconnect links while accessing other Google APIs and services over the public internet. What should you do?

• A.Use Private Google Access, with restricted.googleapis.com virtual IP addresses for Cloud Storage and private.googleapis.com for all other Google APIs and services.
• B.Use Private Service Connect to access Cloud Storage, and use the default public domains for all other Google APIs and services.
• C.Use Private Google Access, with private.googleapis.com virtual IP addresses for Cloud Storage and restricted.googleapis.com virtual IP addresses for all other Google APIs and services.
• D.Use the default public domains for all Google APIs and services.

Comment: *

Name: *

Email: *

Verification: *

You created a new VPC for your development team. You want to allow access to the resources in this VPC via SSH only.
How should you configure your firewall rules?

• A.Create two firewall rules: one to block all traffic with priority 0, and another to allow port 22 with priority
  1000.
• B.Create two firewall rules: one to block all traffic with priority 65536, and another to allow port 3389 with priority 1000.
• C.Create a single firewall rule to allow port 22 with priority 1000.
• D.Create a single firewall rule to allow port 3389 with priority 1000.

Comment: *

Name: *

Email: *

Verification: *

You are designing a hybrid cloud environment for your organization. Your Google Cloud environment is interconnected with your on-premises network using Cloud HA VPN and Cloud Router. The Cloud Router is configured with the default settings. Your on-premises DNS server is located at 192.168.20.88 and is protected by a firewall, and your Compute Engine resources are located at 10.204.0.0/24. Your Compute Engine resources need to resolve on-premises private hostnames using the domain corp.altostrat.com while still 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.
  Configure your on-premises firewall to accept traffic from 10.204.0.0/24.
  Set a custom route advertisement on the Cloud Router for 10.204.0.0/24
• B.Create a private forwarding zone in Cloud DNS for 'corp .altostrat.com' called corp-altostrat-com that points to 192.168.20.88.
  Configure your on-premises firewall to accept traffic from 10.204.0.0/24.
  Modify the /etc/resolv conf file on your Compute Engine instances to point to 192.168.20 88
• C.Create a private zone in Cloud DNS for 'corp altostrat.com' called corp-altostrat-com.
  Configure DNS Server Policies and create a policy with Alternate DNS servers to 192.168.20.88.
  Configure your on-premises firewall to accept traffic from 35.199.192.0/19.
  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.
  Configure your on-premises firewall to accept traffic from 35.199.192.0/19 Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.

Comment: *

Name: *

Email: *

Verification: *

You want to use Partner Interconnect to connect your on-premises network with your VPC. You already have an Interconnect partner.
What should you first?

• A.Log in to your partner's portal and request the VLAN attachment there.
• B.Ask your Interconnect partner to provision a physical connection to Google.
• C.Create a Partner Interconnect type VLAN attachment in the GCP Console and retrieve the pairing key.
• D.Run gcloud compute interconnect attachments partner update <attachment> / -- region <region> --admin-enabled.

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.
  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.
• 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 PCs, with the hub VPC as the target.
  Set a custom route advertisement on the Cloud Router for 35.199.192.0/19.
• 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 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.
• 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.
  Create a hub-and-spoke VPN deployment in each spoke VPC to connect back to the on-premises network directly.

Comment: *

Name: *

Email: *

Verification: *