Exam Professional Cloud Developer topic 1 question 125 discussion

B is the correct answer in this case, A is wrong because according to the best practice and security purpose gcp doesn't allow public ip for redis server.

The most likely reason for the 502 Bad Gateway error and the inability to connect to Memorystore is B. You configured your Serverless VPC Access connector in a different region than your App Engine instance. Here's why: Serverless VPC Access and Regions: App Engine standard environment applications can only communicate with services outside of their environment (like Memorystore) through Serverless VPC Access connectors. These connectors act as a bridge between your App Engine application and your VPC network, where Memorystore resides. Crucially, the connector and the App Engine instance must be in the same region .

B: If you configured your Serverless VPC Access connector in a different region than your App Engine instance, this could cause connectivity issues. Serverless VPC Access connectors and the resources they connect to must be in the same region.

C. The firewall rule allowing a connection between App Engine and Memorystore was removed during an infrastructure update by the DevOps team. Here's why this scenario aligns with the error: 502 Bad Gateway: This error typically indicates that a server (in this case, App Engine) is unable to communicate with an upstream server (Memorystore for Redis) due to a configuration issue. Firewall Rule Removal: If a firewall rule previously allowed App Engine to connect to Memorystore, removing it would block communication and cause the connection failure.

https://cloud.google.com/vpc/docs/configure-serverless-vpc-access In the Region field, select a region for your connector. This must match the region of your serverless service. If your service or job is in the region us-central or europe-west, use us-central1 or europe-west1.

1 1 The most likely reason for the 502 Bad Gateway error is that the firewall rule allowing a connection between App Engine and Memorystore was removed during an infrastructure update by the DevOps team. This is because App Engine needs to be able to connect to Memorystore in order to retrieve the cached user information. If the firewall rule is removed, App Engine will not be able to connect to Memorystore and the application will fail.

502 Bad gateway issue is common more in App Engine Flexible environments than Std due to memory issues. Here I go with option D since pointing connector to a different subnet than App engine instance could cause Bad Gateway issue. A is not correct, because even with the different region with the same subnet, App engine instance do not get issues while connecting to Memeorystore.

C. A: No. The public IP is not mandatory. B: No. App Engine instance region can be different with Serverless VPC Access connector. Link here: https://support.google.com/a/answer/10620692?hl=en . "We support VPC access connectors in 6 regions (us-central, us-west1, us-east1, asia-southeast1, asia-east1, and europe-west1). .... Note: Support for additional regions is coming soon." Although the document didn't mention directly, what if an app in App Engine in southamerica-east1-a would like to connect to Cloud SQL in us region? Note that the diagram here is REALLY mis-leading: https://cloud.google.com/vpc/docs/serverless-vpc-access#example_2 C: Yes. This is the only possible answer. D: No. Serverless VPC Access connector shall be configured with a different subnet. See: https://cloud.google.com/vpc/docs/configure-serverless-vpc-access#console "Every connector requires its own /28 subnet to place connector instances on. A subnet cannot be used by other resources such as VMs, Private Service Connect, or load balancers."

A is not correct because Cloud Run connects to Memorystore via the Serverless VPC Connector. Connections are over private networks. Public addresses are not required. B is correct. All of the components must be in the same region. C is not correct because for connectivity between Cloud Run and Memorystore all that is required is a Serverless VPN Connector. D is not correct. The Serverless VPC Connector is configured with a non-overlapping subnet that is not associated with the VPC.

While both B and D refer to the configuration of the Serverless VPC Access connector and could potentially cause issues with the application's ability to connect to Memorystore, they are slightly different. For B: Having the connector in a different region than the App Engine instance could result in increased latency and potential connectivity issues, but it would not necessarily prevent the App Engine instance from connecting to Memorystore. For D: This option is more specific and is indicating that if the connector is on different subnet or availability zone from App Engine instance it could cause issues with the application's ability to connect to Memorystore, it is less likely for this situation to cause latency or performance issues, but it will affect the connectivity of the App Engine to Memorystore. Both B and D refer to misconfiguration of the Serverless VPC Access connector, but option D is more specific and directly relates to connectivity issue and is more likely to be the root cause of the 502 Bad Gateway error encountered.

B is the answer. https://cloud.google.com/vpc/docs/serverless-vpc-access#how_it_works Serverless VPC Access is based on a resource called a connector. A connector handles traffic between your serverless environment and your VPC network. When you create a connector in your Google Cloud project, you attach it to a specific VPC network and region. You can then configure your serverless services to use the connector for outbound network traffic.

B is correct

Yes! This should be B

I vote B https://cloud.google.com/vpc/docs/configure-serverless-vpc-access