Your on-premises data center has 2 routers connected to your Google Cloud environment through a VPN on each router. All applications are working correctly; however, all of the traffic is passing across a single VPN instead of being load-balanced across the 2 connections as desired.
During troubleshooting you find:
* Each on-premises router is configured with a unique ASN.
* Each on-premises router is configured with the same routes and priorities.
* Both on-premises routers are configured with a VPN connected to a single Cloud Router.
* BGP sessions are established between both on-premises routers and the Cloud Router.
* Only 1 of the on-premises router's routes are being added to the routing table.
What is the most likely cause of this problem?
You need to create the technical architecture for hybrid connectivity from your data center to Google Cloud This will be managed by a partner. You want to follow Google-recommended practices for production-level applications. What should you do?
Your organization has resources in two different VPCs, each in different Google Cloud projects, and requires connectivity between the resources in the two VPCs. You have already determined that there is no IP address overlap; however, one VPC uses privately used public IP (PUPI) ranges. You would like to enable connectivity between these resources by using a lower cost and higher performance method. What should you do?
VPC Network Peering is the most cost-effective and high-performance method for connecting two VPCs. Since one VPC uses privately used public IP (PUPI) ranges, you need to configure peering to allow the export and import of subnet routes with public IP addresses. Firewall rules can be used to control traffic between the resources.
Your company's security team wants to limit the type of inbound traffic that can reach your web servers to protect against security threats. You need to configure the firewall rules on the web servers within your Virtual Private Cloud (VPC) to handle HTTP and HTTPS web traffic for TCP only. What should you do?
Your team deployed two applications in GKE that are exposed through an external Application Load Balancer. When queries are sent to www.mountkirkgames.com/sales and www.mountkirkgames.com/get-an-analysis, the correct pages are displayed. However, you have received complaints that www.mountkirkgames.com yields a 404 error. You need to resolve this error. What should you do?
The 404 error is occurring because there is no default backend defined for requests to the root URL. Defining the default backend in the Ingress YAML file ensures that requests to www.mountkirkgames.com are routed to the correct service.
Tesha
5 days agoLorean
13 days agoWava
20 days agoTimothy
27 days agoCecilia
1 months agoCaren
1 months agoTheron
2 months agoCorrie
2 months agoBenedict
2 months agoDannie
4 months agoWerner
5 months agoAnastacia
7 months agoGregoria
8 months agoNieves
9 months agoLisbeth
10 months agoMarta
10 months agoStacey
10 months agoValentine
11 months agoJunita
11 months agoKati
11 months agoAvery
11 months agoGail
12 months agoAleta
12 months agoJenelle
1 years agoJenise
1 years agoMaddie
1 years agoBernardo
1 years agoEmily
1 years agoMona
1 years agoMayra
1 years agoCorazon
1 years agoAdrianna
1 years agoRemona
1 years agoShalon
1 years agoAleisha
1 years agoLera
1 years agoAngelica
1 years agoVeronica
1 years agoJestine
1 years agoLorean
1 years agoQuentin
1 years agoLisha
1 years ago