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 manages a production Firestore database and needs to automate nightly exports to a Google Cloud Storage bucket for archival compliance and downstream analytics in BigQuery. Your automation pipeline must meet the following requirements:
Which approach should you implement?
Datastream is a serverless Change Data Capture (CDC) and replication service on Google Cloud that captures real-time data changes (inserts, updates, and deletes) from operational databases and streams them reliably into BigQuery or Cloud Storage.
Your operational workload ran on a supported relational database such as PostgreSQL, MySQL, SQL Server, or Oracle, and your goal was continuous real-time CDC streaming to Cloud Storage or BigQuery rather than nightly Firestore CLI exports.
Although both Datastream and Firestore managed exports can land data in Cloud Storage for downstream BigQuery analytics, they apply to different database families and operational models. Note that a Firestore export is not a transactional point-in-time snapshot and may include writes occurring while the export runs, whereas Datastream preserves ordered relational CDC event streams.
This approach attempts to authorize the caller's automation service account with write-only permissions (roles/storage.objectCreator) and runs an unfiltered, synchronous export of the entire Firestore database.
roles/storage.admin) role on the bucket.--async flag forces the gcloud CLI to wait until the export finishes, which violates the requirement for non-blocking execution and risks pipeline timeouts.roles/storage.admin on the target bucket.The goal was strictly a full-database backup where synchronous CLI execution was acceptable, and the Firestore service agent already held roles/storage.admin on the bucket—even then, granting roles/storage.objectCreator to the CLI runner would not authorize the managed export writer.
A frequent misconception is applying least-privilege Cloud Storage roles to the CI/CD or scheduler service account that invokes gcloud. Because Google's managed export infrastructure performs the actual bucket writes, the Firestore service agent must hold Storage Admin on the bucket.
Firestore managed export is a serverless operation that copies documents from a Firestore database into a set of files stored in a Cloud Storage bucket. Rather than downloading documents through a local client, the Google-managed backend executes the export job and writes both document data and export metadata directly to the destination bucket.
--async flag to the gcloud firestore export command submits the job and returns control immediately without waiting for the export to complete. Closing the terminal or pipeline runner does not cancel the background operation.service-PROJECT_NUMBER@gcp-sa-firestore.iam.gserviceaccount.com), granting the Storage Admin (roles/storage.admin) role on the destination bucket provides the exact permissions needed to create and manage export objects.Using gcloud firestore export with --async, targeted collection groups, and roles/storage.admin on the Firestore service agent leverages native platform capabilities directly. It avoids custom extraction scripts, ensures BigQuery load compatibility, and prevents pipeline timeouts on large datasets.
Storage Transfer Service is a fully managed Google Cloud tool for automating high-throughput online data transfers into Cloud Storage from object stores (such as Amazon S3 and Azure Blob Storage), HTTP/HTTPS sources, POSIX file systems, or other Cloud Storage buckets.
The data had already been extracted to an external cloud bucket (such as Amazon S3) or an on-premises POSIX file system, and you needed an automated, checksum-verified pipeline to copy those files into Cloud Storage.
Database engineers sometimes confuse Storage Transfer Service with database export services when designing archival workflows. In practice, native database export tools like gcloud firestore export must first write the database files to Cloud Storage, after which Storage Transfer Service can optionally replicate those objects across clouds or buckets.
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