Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A company is designing the database authentication architecture for two production workloads on Google Cloud:
Which authentication strategy should the company implement for these workloads?
Traditional built-in database authentication verifies identities using database-managed usernames and static passwords configured directly within each instance. IAM database authentication replaces local passwords with centralized IAM policies and temporary OAuth 2.0 access tokens, enforcing encrypted SSL/TLS connections for every sign-in.
This option reverses the appropriate authentication models for both workloads:
Workload A were a legacy application strictly dependent on local PostgreSQL passwords (for example, on a resource-constrained instance avoiding IAM token verification overhead), and Workload B were running on Cloud SQL for PostgreSQL or MySQL instead of SQL Server.
Automatic IAM database authentication delegates the retrieval and renewal of OAuth 2.0 access tokens to client-side intermediaries such as the AlloyDB Auth Proxy, Cloud SQL Auth Proxy, or Language Connectors. This enables applications to authenticate using IAM principals rather than static database passwords while automatically encrypting connections.
While this approach works well for Workload A on AlloyDB for PostgreSQL, it fails for Workload B because Cloud SQL for SQL Server does not support IAM database authentication for database-level operations. In Cloud SQL for SQL Server, IAM permissions govern only control-plane actions such as managing instances, creating backups, or viewing configuration metadata. Attempting to configure a Cloud SQL connector to perform IAM database authentication for SQL queries on SQL Server is unsupported and will prevent the legacy application from connecting to its databases.
Workload B were running on Cloud SQL for PostgreSQL or Cloud SQL for MySQL instead of SQL Server, and the legacy application could connect using IAM principals without depending on local SQL logins.
Automatic IAM database authentication integrates database sign-ins with Google Cloud Identity and Access Management (IAM), replacing static database passwords with short-lived OAuth 2.0 access tokens managed transparently by an intermediary connector. Traditional built-in database authentication relies on local database usernames and passwords stored and verified directly by the database engine.
This hybrid strategy applies IAM database authentication where it is supported and most beneficial—long-lived, security-sensitive PostgreSQL microservices—while correctly respecting Cloud SQL for SQL Server's architectural boundary that restricts IAM authentication to control-plane operations rather than database queries.
Manual IAM database authentication requires a client or user to explicitly request an OAuth 2.0 access token from IAM (for example, via gcloud auth print-access-token) and supply that token as the database password during connection setup. IAM group authentication allows administrators to assign IAM roles and database privileges to a Cloud Identity group so members inherit access automatically without adding each account individually to the database.
Workload A consisted of short-lived, interactive developer sessions using CLI tools like psql, and Workload B used Cloud SQL for PostgreSQL or MySQL rather than SQL Server.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated