Google Prof Cloud Network - pt 1

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

• 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.

• 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.

• 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.

• 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

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?

• Create 2 VPCs, each with their own regions and individual subnets. Create 2 VPN gateways to establish connectivity between these regions.

• Create 2 VPCs, each with their own region and individual subnets. Use external IP addresses on the instances to establish connectivity between these regions.

• Create 1 VPC with 2 regional subnets. Create a global load balancer to establish connectivity between the regions.

• Create 1 VPC with 2 regional subnets. Deploy workloads in these subnets and have them communicate using private RFC1918 IP addresses.

Your organization is deploying a single project for 3 separate departments. Two of these departments require network connectivity between each other, but the third department should remain in isolation. Your design should create separate network administrative domains between these departments. You want to minimize operational overhead. How should you design the topology?

• Create a Shared VPC Host Project and the respective Service Projects for each of the 3 separate departments.

• Create a Shared VPC Host Project and the respective Service Projects for each of the 3 separate departments.

• Create 3 separate VPCs, and use VPC peering to establish connectivity between the two appropriate VPCs.

• Create a single project, and deploy specific firewall rules. Use network tags to isolate access between the departments.

You are migrating to Cloud DNS and want to import your BIND zone file. Which command should you use?

• gcloud dns record-sets import ZONE_FILE --zone MANAGED_ZONE

• gcloud dns record-sets import ZONE_FILE --replace-origin-ns --zone MANAGED_ZONE

• gcloud dns record-sets import ZONE_FILE --zone-file-format --zone MANAGED_ZONE

• gcloud dns record-sets import ZONE_FILE --delete-all-existing --zone MANAGED ZONE

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?

• Create the Distribution VPC in auto mode. Peer both the VPCs via network peering.

• 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.

• 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.

• Rename the default VPC as "Distribution" and peer it via network peering.

You are using a third-party next-generation firewall to inspect traffic. You created a custom route of 0.0.0.0/0 to route egress traffic to the firewall. You want to allow your VPC instances without public IP addresses to access the BigQuery and Cloud Pub/Sub APIs, without sending the traffic through the firewall. Which two actions should you take? (Choose two.

• Turn on Private Google Access at the subnet level.

• Turn on Private Google Access at the VPC level.

• Turn on Private Services Access at the VPC level.

• Create a set of custom static routes to send traffic to the external IP addresses of Google APIs and services via the default internet gateway.

• Create a set of custom static routes to send traffic to the internal IP addresses of Google APIs and services via the default internet gateway.

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?

• Open the Cloud Shell SSH into the instance using gcloud compute ssh.

• Set the custom metadata enable-oslogin to TRUE, and SSH into the instance using a third-party tool like putty or ssh.

• 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.

• 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.

what should you do?

• Use Shared VPC, and deploy the VLAN attachments and Interconnect in the host project.

• Use Shared VPC, and deploy the VLAN attachments in the service projects. Connect the VLAN attachment to the Shared VPC's host project.

• Use standalone projects, and deploy the VLAN attachments in the individual projects. Connect the VLAN attachment to the standalone projects' Interconnects.

• Use standalone projects and deploy the VLAN attachments and Interconnects in each of the individual projects.

You have deployed a new internal application that provides HTTP and TFTP services to on-premises hosts. You want to be able to distribute traffic across multiple Compute Engine instances, but need to ensure that clients are sticky to a particular instance across both services. Which session affinity should you choose?

• None

• Client IP

• Client IP and protocol

• Client IP, port and protocol

You created a new VPC network named Dev with a single subnet. You added a firewall rule for the network Dev to allow HTTP traffic only and enabled logging. When you try to log in to an instance in the subnet via Remote Desktop Protocol, the login fails. You look for the Firewall rules logs in Stackdriver Logging, but you do not see any entries for blocked traffic. You want to see the logs for blocked traffic. What should you do?

• Check the VPC flow logs for the instance.

• Try connecting to the instance via SSH, and check the logs.

• Create a new firewall rule to allow traffic from port 22, and enable logs.

• Create a new firewall rule with priority 65500 to deny all traffic, and enable logs