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

You have the following routing design. You discover that Compute Engine instances in Subnet-2 in the asia- southeast1 region cannot communicate with compute resources on-premises. What should you do?

• A.Add a second Border Gateway Protocol (BGP) session to the Cloud Router.
• B.Configure a custom route advertisement on the Cloud Router.
• C.Enable IP forwarding in the asia-southeast1 region.
• D.Change the VPC dynamic routing mode to Global.

Your organization has Compute Engine instances in us-east1, us-west2, and us-central1. Your organization also has an existing Cloud Interconnect physical connection in the East Coast of the United States with a single VLAN attachment and Cloud Router in us-east1. You need to provide a design with high availability and ensure that if a region goes down, you still have access to all your other Virtual Private Cloud (VPC) subnets. You need to accomplish this in the most cost-effective manner possible. What should you do?

• A.Configure your VPC routing in regional mode.
  Add an additional Cloud Interconnect VLAN attachment in the us-east1 region, and configure a Cloud Router in us-east1.
• B.Configure your VPC routing in regional mode.
  Add additional Cloud Interconnect VLAN attachments in the us-west2 and us-central1 regions, and configure Cloud Routers in us-west2 and us-central1.
• C.Configure your VPC routing in global mode.
  Add an additional Cloud Interconnect VLAN attachment in the us-west2 region, and configure a Cloud Router in us-west2.
• D.Configure your VPC routing in global mode.
  Add an additional Cloud Interconnect VLAN attachment in the us-east1 region, and configure a Cloud Router in us-east1.

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?

• A.Client IP and protocol
• B.None
• C.Client IP, port and protocol
• D.Client IP

You want to deploy a VPN Gateway to connect your on-premises network to GCP. You are using a non BGP- capable on-premises VPN device. You want to minimize downtime and operational overhead when your network grows. The device supports only IKEv2, and you want to follow Google-recommended practices.
What should you do?

• A.* Create a Cloud VPN instance.* Create a route-based VPN tunnel.* Configure the appropriate local and remote traffic selectors to match your local and remote networks.* Configure the appropriate static routes.
• B.* Create a Cloud VPN instance.* Create a policy-based VPN tunnel.* Configure the appropriate local and remote traffic selectors to match your local and remote networks.* Configure the appropriate static routes.
• C.* Create a Cloud VPN instance.* Create a route-based VPN tunnel.* Configure the appropriate local and remote traffic selectors to 0.0.0.0/0.* Configure the appropriate static routes.
• D.* Create a Cloud VPN instance.* Create a policy-based VPN tunnel per subnet.* Configure the appropriate local and remote traffic selectors to match your local and remote networks.* Create the appropriate static routes.

Your organization wants to set up hybrid connectivity with VLAN attachments that terminate in a single Cloud Router with 99.9% uptime. You need to create a network design for your on-premises router that meets those requirements and has an active/passive configuration that uses only one VLAN attachment at a time.
What should you do?

• A.Create a design that uses a BGP multi-exit discriminator (MED) attribute to influence the egress path from Google Cloud to the on-premises environment.
• B.Create a design that uses an equal-cost multipath (ECMP) with flow-based hashing on your on-premises devices.
• C.Create a design that uses the as_path BGP attribute to influence the egress path from Google Cloud to the on-premises environment.
• D.Create a design that uses the local_pref BGP attribute to influence the egress path from Google Cloud to the on-premises environment.