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 Cloud SQL, AlloyDB, Firestore, and BigQuery databases in a production Google Cloud project. Following a security audit, you must implement a centralized auditing strategy using Cloud Audit Logs to meet these requirements:
_Default bucket.Which configuration should you implement?
The Logs Viewer (roles/logging.viewer) IAM role provides read-only access to standard Cloud Logging entries along with Admin Activity, System Event, and Policy Denied audit logs. It is commonly assigned to developers and operators who need to troubleshoot infrastructure or review administrative configuration changes.
roles/logging.viewer cannot view Data Access audit logs stored in the _Default log bucket.roles/logging.viewer from querying them in _Default. The auditor would see BigQuery and administrative events only if allowed by other permissions, or miss _Default Data Access logs entirely._Required bucket logs (Admin Activity and System Event) and Policy Denied logs._Default bucket._Default bucket Data Access logs requires the Private Logs Viewer (roles/logging.privateLogViewer) role, which includes all roles/logging.viewer permissions plus private audit log access.The auditor only needed to investigate administrative configuration changes, Google-managed system events, and policy denials, or if all Data Access audit logs were routed out of _Default into a user-defined log bucket with explicit bucket-level read permissions.
By default, Google Cloud automatically enables Admin Activity, System Event, and Policy Denied audit logs across all projects, folders, and organizations. However, Data Access audit logs are handled differently depending on the specific Google Cloud service.
DATA_READ, DATA_WRITE, and ADMIN_READ operations against Cloud SQL, AlloyDB, and Firestore will never be recorded.roles/logging.privateLogViewer gives the auditor permission to read the _Default bucket, no Data Access entries for those three database services will exist in the bucket to inspect.AuditConfig policy to enable ADMIN_READ, DATA_READ, and DATA_WRITE logging per service or for all services.BigQuery were the only database service in the environment, or if the audit requirements only covered administrative changes and system events without needing to track individual data reads and writes on Cloud SQL, AlloyDB, and Firestore.
Admin Activity audit logs record user-driven API calls that create, modify, or delete resource configurations and metadata. Policy Denied audit logs record events where a Google Cloud service blocks access due to a security policy violation. Engine-level flags such as PostgreSQL log_statement capture SQL statements directly inside PostgreSQL database logs.
DATA_READ and DATA_WRITE) generate Data Access audit logs, not Admin Activity audit logs. Relying on Admin Activity logs leaves data access patterns unrecorded.log_statement flags apply only to PostgreSQL-compatible instances (Cloud SQL for PostgreSQL and AlloyDB) and do not capture Firestore document reads/writes or BigQuery API-level Cloud Audit Logs.You only needed to audit SQL statement execution inside PostgreSQL engines alongside security policy denials and resource configuration changes, rather than unified Cloud Audit Logs for data access across Firestore and all managed databases.
Cloud Audit Logs provides immutable audit trails across Google Cloud services to answer who did what, where, and when. It divides events into four log types: Admin Activity, Data Access, System Event, and Policy Denied audit logs, stored primarily in the _Required and _Default Cloud Logging buckets.
_Required bucket.ADMIN_READ, DATA_READ, and DATA_WRITE) ensures every user and service account read and write operation is captured in the _Default bucket.roles/logging.privateLogViewer) role gives the auditor read-only access to Admin Activity, System Event, and Policy Denied logs while also granting permission to read sensitive Data Access logs in the _Default bucket.This configuration avoids unnecessary duplication while ensuring zero blind spots across database engines, enforcing least-privilege IAM access, and meeting long-term retention mandates.
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