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 organization manages multiple production Cloud SQL and BigQuery instances across several Google Cloud projects within a sensitive production folder. To meet regulatory compliance, your audit strategy must satisfy the following requirements:
Which auditing and log governance architecture should you implement?
Exporting audit logs to BigQuery enables SQL-based security analytics across historical log entries, while roles/logging.viewer is a predefined Cloud Logging IAM role that allows principals to view Admin Activity and System Event logs within Cloud Logging. However, storing exported audit logs inside each individual workload project fails to isolate telemetry from the teams that operate those databases.
You only needed ad-hoc SQL analytics in a non-sensitive environment without strict separation of duties, and if you used a centralized security project inside the perimeter while granting auditors roles/bigquery.dataViewer on the destination dataset.
A folder-level aggregated log sink collects Admin Activity and Data Access audit logs from all child projects in a folder and routes them to a central destination. Storing these exported logs in a Cloud Storage bucket inside a dedicated security project with a locked retention policy (Bucket Lock) establishes an immutable, long-term archive isolated from database administrators. Wrapping both the source database projects and the destination security project inside the same VPC Service Controls perimeter enforces a strict security boundary around the telemetry.
Unlike project-local storage or streaming brokers, this architecture provides immutable multi-year compliance storage, strict separation of duties between database operators and security teams, destination-scoped least privilege, and network-layer exfiltration protection via VPC Service Controls.
Pub/Sub is an asynchronous, real-time messaging service commonly used as a transport layer when routing Cloud Audit Logs to third-party Security Information and Event Management (SIEM) platforms such as Splunk or custom streaming pipelines. Meanwhile, roles/logging.privateLogViewer is a Cloud Logging IAM role that permits users to read sensitive Data Access audit logs directly within Cloud Logging.
The primary requirement was to stream database audit events in near real time into an external third-party SIEM platform rather than maintaining a self-contained, 7-year immutable compliance archive in Google Cloud.
The _Default log bucket automatically stores enabled Data Access audit logs and Policy Denied logs within each project. Field-level access controls restrict visibility of specific LogEntry fields (such as PII in payloads) for unauthorized users, while Observability Analytics allows administrators to run BigQuery-standard SQL queries against upgraded Cloud Logging buckets.
_Default bucket leaves the log configuration and retention settings within the same project boundary as the database workloads rather than isolating them in a restricted security project._Default bucket retains logs for 30 days unless custom retention (up to 3,650 days) is explicitly configured on each bucket, and project-level isolation makes organization-wide auditing difficult.You wanted to restrict specific payload fields within Cloud Logging's Logs Explorer for internal project troubleshooting without needing Observability Analytics, cross-project isolation, or VPC Service Controls perimeters.
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