Topic 1 Question 321
Your team plans to use AlloyDB as their database backend for an upcoming application release. Your application is currently hosted in a different project and network than the AlloyDB instances. You need to securely connect your application to the AlloyDB instance while keeping the projects isolated. You want to minimize additional operations and follow Google-recommended practices. How should you configure the network for database connectivity?
Provision a Shared VPC project where both the application project and the AlloyDB project are service projects.
Use AlloyDB Auth Proxy and configure the application project’s firewall to allow connections to port 5433.
Provision a service account from the AlloyDB project. Use this service account’s JSON key file as the --credentials-file to connect to the AlloyDB instance.
Ask the database team to provision AlloyDB databases in the same project and network as the application.
ユーザの投票
コメント(2)
- 正解だと思う選択肢: B
he best option for securely connecting your application to the AlloyDB instance while keeping the projects isolated, following Google-recommended practices, and minimizing additional operations is Option B: Use AlloyDB Auth Proxy and configure the application project’s firewall to allow connections to port 5433.
👍 2anshad6662024/10/12 - 正解だと思う選択肢: A
Shared VPC provides the basic network connectivity by allowing resources in different projects to share a common VPC. However, either PSA or PSC is additionally required to enable access to the AlloyDB service, which resides in Google's internal service network
👍 2jlr19732025/01/14
シャッフルモード