Google Professional Cloud Network Engineer Exam

Page:    1 / 35   
Total 172 questions

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.


Answer : C

Reference:
https://link.springer.com/chapter/10.1007/978-1-4842-1004-8_4

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?

  • A. Create 2 VPCs, each with their own regions and individual subnets. Create 2 VPN gateways to establish connectivity between these regions.
  • B. Create 2 VPCs, each with their own region and individual subnets. Use external IP addresses on the instances to establish connectivity between these regions.
  • C. Create 1 VPC with 2 regional subnets. Create a global load balancer to establish connectivity between the regions.
  • D. Create 1 VPC with 2 regional subnets. Deploy workloads in these subnets and have them communicate using private RFC1918 IP addresses.


Answer : D

VPC Network Peering enables you to peer VPC networks so that workloads in different VPC networks can communicate in private RFC 1918 space. Traffic stays within Google's network and doesn't traverse the public internet.
Reference:
https://cloud.google.com/vpc/docs/vpc-peering

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?

  • A. Create a Shared VPC Host Project and the respective Service Projects for each of the 3 separate departments.
  • B. Create 3 separate VPCs, and use Cloud VPN to establish connectivity between the two appropriate VPCs.
  • C. Create 3 separate VPCs, and use VPC peering to establish connectivity between the two appropriate VPCs.
  • D. Create a single project, and deploy specific firewall rules. Use network tags to isolate access between the departments.


Answer : A

Use Shared VPC to connect to a common VPC network. Resources in those projects can communicate with each other securely and efficiently across project boundaries using internal IPs. You can manage shared network resources, such as subnets, routes, and firewalls, from a central host project, enabling you to apply and enforce consistent network policies across the projects.
With Shared VPC and IAM controls, you can separate network administration from project administration. This separation helps you implement the principle of least privilege. For example, a centralized network team can administer the network without having any permissions into the participating projects. Similarly, the project admins can manage their project resources without any permissions to manipulate the shared network.
Reference:
https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations

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

  • A. gcloud dns record-sets import ZONE_FILE --zone MANAGED_ZONE
  • B. gcloud dns record-sets import ZONE_FILE --replace-origin-ns --zone MANAGED_ZONE
  • C. gcloud dns record-sets import ZONE_FILE --zone-file-format --zone MANAGED_ZONE
  • D. gcloud dns record-sets import ZONE_FILE --delete-all-existing --zone MANAGED ZONE


Answer : C

Once you have the exported file from your other provider, you can use the gcloud dns record-sets import command to import it into your managed zone.
To import record-sets, you use the dns record-sets import command. The --zone-file-format flag tells importto expect a BIND zone formatted file. If you omit this flag, import expects a YAML-formatted records file.
Reference:
https://medium.com/@prashantapaudel/gcp-certification-series-2-4-planning-and-configuring-network-resources-8045ac2cc2ac

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.


Answer : B

Reference:
https://cloud.google.com/vpc/docs/using-vpc

Page:    1 / 35   
Total 172 questions