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.0.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.128.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 need to create a new VPC network that allows instances to have IP addresses in both the 10.1.1.0/24 network and the 172.16.45.0/24 network.
What should you do?

• A.Configure an alias-IP range of 172.16.45.0/24 on the virtual instances within the VPC subnet of 10.1.1.0/24.
• B.Create unique DNS records for each service that sends traffic to the desired IP address.
• C.Use VPC peering to allow traffic to route between the 10.1.0.0/24 network and the 172.16.45.0/24 network.
• D.Configure global load balancing to point 172.16.45.0/24 to the correct instance.

Comment: *

Name: *

Email: *

Verification: *

You need to give each member of your network operations team least-privilege access to create, modify, and delete Cloud Interconnect VLAN attachments.
What should you do?

• A.Assign each user the editor role.
• B.Assign each user the compute.networkAdmin role.
• C.Give each user the following permissions only: compute.interconnectAttachments.create, compute.interconnectAttachments.get.
• D.Give each user the following permissions only: compute.interconnectAttachments.create, compute.interconnectAttachments.get, compute.routers.create, compute.routers.get, compute.routers.update.

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.The instance has been configured with multiple interfaces.
• B.The instance is accessible by a load balancer external IP address.
• C.You have created static routes that use RFC1918 ranges.
• D.An external IP address has been configured on the instance.

Comment: *

Name: *

Email: *

Verification: *

You need to restrict access to your Google Cloud load-balanced application so that only specific IP addresses can connect.
What should you do?

• A.Create a secure perimeter using the Access Context Manager feature of VPC Service Controls and restrict access to the source IP range of the allowed clients and Google health check IP ranges.
• B.Create a secure perimeter using VPC Service Controls, and mark the load balancer as a service restricted to the source IP range of the allowed clients and Google health check IP ranges.
• C.Tag the backend instances "application," and create a firewall rule with target tag "application" and the source IP range of the allowed clients and Google health check IP ranges.
• D.Label the backend instances "application," and create a firewall rule with the target label "application" and the source IP range of the allowed clients and Google health check IP ranges.

Comment: *

Name: *

Email: *

Verification: *