Professional-Cloud-Network-Engineer 무료 덤프문제 온라인 액세스

You have the networking configuration shown in the diagram. A pair of redundant Dedicated Interconnect connections (int-Igal and int-Iga2) terminate on the same Cloud Router. The Interconnect connections terminate on two separate on-premises routers. You are advertising the same prefixes from the Border Gateway Protocol (BGP) sessions associated with the Dedicated Interconnect connections. You need to configure one connection as Active for both ingress and egress traffic. If the active Interconnect connection fails, you want the passive Interconnect connection to automatically begin routing all traffic Which two actions should you take to meet this requirement? (Choose Two)

• A.Configure the advertised route priority as 200 for the BGP session associated with the active Interconnect connection.
• B.Configure the advertised route priority as 200 for the BGP session associated with the passive Interconnect connection.
• C.Configure the advertised route priority > 10,200 on the active Interconnect connection.
• D.Advertise a lower MED on the active Interconnect connection from the on-premises router
• E.Advertise a lower MED on the passive Interconnect connection from the on-premises router

Your organization uses a hub-and-spoke architecture with critical Compute Engine instances in your Virtual Private Clouds (VPCs). You are responsible for the design of Cloud DNS in Google Cloud. You need to be able to resolve Cloud DNS private zones from your on-premises data center and enable on-premises name resolution from your hub-and-spoke VPC design. What should you do?

• A.Configure a DNS policy in the hub VPC to allow inbound query forwarding from the spoke VPCs.
  Configure the spoke VPCs with a private zone, and set up DNS peering to the hub VPC.
• B.Configure a DNS policy in the hub VPC, and configure the on-premises DNS as an alternate DNS server.
  Configure the spoke VPCs with a private zone, and set up DNS peering to the hub VPC.
• C.Configure a private DNS zone in the hub VPC, and configure DNS forwarding to the on-premises server.
  Configure DNS peering from the spoke VPCs to the hub VPC.
• D.Configure a DNS policy in the spoke VPCs, and configure your on-premises DNS as an alternate DNS server.
  Configure the hub VPC with a private zone, and set up DNS peering to each of the spoke VPCs.

Question:
Your company's current network architecture has three VPC Service Controls perimeters:
* One perimeter (PERIMETER_PROD) to protect production storage buckets
* One perimeter (PERIMETER_NONPROD) to protect non-production storage buckets
* One perimeter (PERIMETER_VPC) that contains a single VPC (VPC_ONE)
In this single VPC (VPC_ONE), the IP_RANGE_PROD is dedicated to the subnets of the production workloads, and the IP_RANGE_NONPROD is dedicated to subnets of non-production workloads. Workloads cannot be created outside those two ranges. You need to ensure that production workloads can access only production storage buckets and non-production workloads can access only non-production storage buckets with minimal setup effort. What should you do?

• A.Develop a design that uses the IP_RANGE_PROD and IP_RANGE_NONPROD perimeters to create two access levels, with each access level referencing a single range. Create two ingress access policies with each access policy referencing one of the two access levels. Update the PERIMETER_PROD and PERIMETER_NONPROD perimeters.
• B.Develop a design that creates a new VPC (VPC_NONPROD) in the same project as VPC_ONE.
  Migrate all the non-production workloads from VPC_ONE to the PERIMETER_NONPROD perimeter.
  Remove the PERIMETER_VPC perimeter. Update the PERIMETER_PROD perimeter to include VPC_ONE and the PERIMETER_NONPROD perimeter to include VPC_NONPROD.
• C.Develop a design that removes the PERIMETER_VPC perimeter. Update the PERIMETER_PROD perimeter to include the project containing VPC_ONE. Remove the PERIMETER_NONPROD perimeter.
• D.Develop a design that removes the PERIMETER_VPC perimeter. Update the PERIMETER_NONPROD perimeter to include the project containing VPC_ONE. Remove the PERIMETER_PROD perimeter.

Question:
You are configuring the final elements of a migration effort where resources have been moved from on- premises to Google Cloud. While reviewing the deployed architecture, you noticed that DNS resolution is failing when queries are being sent to the on-premises environment. You log in to a Compute Engine instance, try to resolve an on-premises hostname, and the query fails. DNS queries are not arriving at the on-premises DNS server. You need to use managed services to reconfigure Cloud DNS to resolve the DNS error. What should you do?

• A.Validate that the Compute Engine instances are using the Metadata Service IP address as their resolver.
  Configure an outbound forwarding zone for the on-premises domain pointing to the on-premises DNS server. Configure Cloud Router to advertise the Cloud DNS proxy range to the on-premises network.
• B.Review the existing Cloud DNS zones, and validate that there is a route in the VPC directing traffic destined to the IP address of the DNS servers. Recreate the existing DNS forwarding zones to forward all queries to the on-premises DNS servers.
• C.Validate that there is network connectivity to the on-premises environment and that the Compute Engine instances can reach other on-premises resources. If errors persist, remove the VPC Network Peerings and recreate the peerings after validating the routes.
• D.Ensure that the operating systems of the Compute Engine instances are configured to send DNS queries to the on-premises DNS servers directly.

You need to establish network connectivity between three Virtual Private Cloud networks, Sales, Marketing, and Finance, so that users can access resources in all three VPCs. You configure VPC peering between the Sales VPC and the Finance VPC. You also configure VPC peering between the Marketing VPC and the Finance VPC. After you complete the configuration, some users cannot connect to resources in the Sales VPC and the Marketing VPC. You want to resolve the problem.
What should you do?

• A.Delete the legacy network and recreate it to allow transitive peering.
• B.Configure VPC peering in a full mesh.
• C.Create network tags to allow connectivity between all three VPCs.
• D.Alter the routing table to resolve the asymmetric route.