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.
Your team is automating data transfers between a Cloud SQL for PostgreSQL instance and a dedicated Cloud Storage bucket. The pipeline must support exporting database dumps to the bucket and importing data back into Cloud SQL while meeting these requirements:
Which configuration should you implement?
roles/cloudsql.editor) to the initiating principal, grant the Storage Admin role (roles/storage.admin) at the project level to the Cloud SQL instance's service account, and use object ACLs with OWNER permission for bucket access.This approach correctly gives the initiating principal roles/cloudsql.editor to trigger exports and imports, but it grants the Storage Admin role (roles/storage.admin) across the entire project to the Cloud SQL instance's service account and relies on legacy Access Control Lists (ACLs) with OWNER permissions.
roles/storage.admin at the project level gives the Cloud SQL service account full administrative control over every Cloud Storage bucket in the project, directly violating the requirement to block access to unrelated buckets.roles/storage.admin role includes storage.buckets.setIamPolicy and storage.buckets.delete permissions, allowing the principal to alter access controls and take full control of bucket policies.OWNER permissions bypasses centralized IAM governance and grants excessive control over objects, failing the requirement to enforce IAM-only access.*.setIamPolicy permissions or OWNER ACLs allow principals to grant themselves or others additional access.You were delegating full administrative ownership of all Cloud Storage infrastructure in a project to a dedicated storage administrator, rather than scoping a database service account to a single transfer bucket.
roles/cloudsql.client) to the initiating principal, grant the Storage Object Viewer role (roles/storage.objectViewer) on the target bucket to the Compute Engine default service account, and enable Uniform Bucket-Level Access.This configuration enables Uniform Bucket-Level Access, assigns the Cloud SQL Client role (roles/cloudsql.client) to the initiating principal, and grants Storage Object Viewer (roles/storage.objectViewer) on the bucket to the Compute Engine default service account.
roles/cloudsql.client role is designed for establishing database network connections (such as through the Cloud SQL Auth Proxy), not for running administrative cloudsql.instances.export or import jobs.roles/storage.objectViewer role only permits reading and listing objects. While it allows reading files for imports, it cannot create or write new database dump objects during a Cloud SQL export.roles/cloudsql.client authorizes cloudsql.instances.connect and get, whereas exports require roles/cloudsql.editor or a custom role with cloudsql.instances.export.storage.objects.create permissions, which roles/storage.objectViewer omits.An application running on a Compute Engine VM needed to connect to Cloud SQL via the Auth Proxy (roles/cloudsql.client) and only read static files from a Cloud Storage bucket (roles/storage.objectViewer).
roles/cloudsql.editor) to the initiating principal, grant the Storage Object Admin role (roles/storage.objectAdmin) to the Cloud SQL instance's service account on the target bucket, and enable Uniform Bucket-Level Access.This configuration separates the responsibilities of initiating a database transfer from reading and writing files in Cloud Storage, assigning the exact minimum permissions required to each identity involved in the Cloud SQL import and export pipeline.
roles/cloudsql.editor) grants the initiating user or automation account the cloudsql.instances.export and import management permissions needed to trigger operations, without granting full project-wide administrative control. Meanwhile, the Storage Object Admin role (roles/storage.objectAdmin) gives the Cloud SQL instance's service account full read, write, and delete access to objects so it can both write export dumps and read import files.roles/storage.objectAdmin directly on the target bucket (rather than at the project level) restricts access strictly to that single bucket and excludes the storage.buckets.setIamPolicy permission, preventing the service account from altering bucket permissions or touching other project buckets.roles/storage.objectAdmin covers both exporting data out of Cloud SQL and importing data back in.Unlike granting roles/storage.admin at the project level or relying on legacy ACLs, scoping roles/storage.objectAdmin to the specific bucket with UBLA enabled satisfies Google Cloud's security best practices while ensuring seamless, automated Cloud SQL exports and imports.
roles/cloudsql.viewer) and the Storage Object Admin role (roles/storage.objectAdmin) on the target bucket to the initiating principal, while keeping default permissions on the Cloud SQL instance's service account.This option grants read-only Cloud SQL visibility (roles/cloudsql.viewer) and bucket-level object management (roles/storage.objectAdmin) to the initiating principal, while leaving the Cloud SQL instance's service account without explicit Cloud Storage permissions.
cloudsql.instances.export and import permissions required to start data transfer jobs.roles/storage.objectAdmin assigned to that instance service account, both export and import operations fail with permission denied errors.roles/cloudsql.viewer is restricted to get and list operations on Cloud SQL resources.roles/storage.objectAdmin unnecessarily lets that user delete or overwrite backup objects manually.You only wanted an auditor or developer to inspect Cloud SQL instance configurations while independently uploading or managing files in a Cloud Storage bucket outside of Cloud SQL's native import/export workflow.
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