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 healthcare organization is migrating patient databases to Cloud SQL and BigQuery and must comply with HIPAA and GDPR. The compliance team requires the following controls:
Which combination of Google Cloud controls should you implement?
This solution combines Cloud Audit Logs, Access Transparency, and Sensitive Data Protection (formerly Cloud Data Loss Prevention or Cloud DLP) to establish end-to-end observability and data privacy across Google Cloud database environments. Together, these services address internal user accountability, cloud provider personnel oversight, and automated protection of regulated data such as personally identifiable information (PII) and protected health information.
ADMIN_WRITE), while Data Access audit logs (ADMIN_READ, DATA_READ, and DATA_WRITE) capture user data reads and writes. Because Data Access logs are disabled by default for services other than BigQuery (such as Cloud SQL), enabling them at the organization level ensures uniform coverage across all existing and new projects and prevents project-level disabling. Exporting logs through a Cloud Logging sink to long-term storage satisfies the 1-to-7-year retention periods mandated by regulations like HIPAA.Unlike partial logging configurations or storage-level encryption alone, this combination directly satisfies all three pillars of regulatory database compliance: internal user and admin auditing, external cloud-provider access verification, and column-level PII redaction prior to analytical consumption.
This option relies on Policy Denied audit logs, default Cloud Logging bucket retention, Security Command Center, and Sensitive Data Protection discovery jobs without any de-identification step. Although these tools improve security posture visibility, they fail to capture required activity, retain logs long enough, or protect PII from analyst exposure.
DATA_READ and DATA_WRITE queries. Furthermore, default Cloud Logging bucket retention periods are often too short to satisfy HIPAA mandates requiring 1 to 7 years of audit log retention.The goal were simply to inventory where sensitive data exists, aggregate security posture findings in Security Command Center, and track blocked access attempts over a short retention window.
An effective privacy workflow pairs Sensitive Data Protection discovery (to locate unexpected or unprotected PII) with de-identification templates to produce safe, tokenized copies for downstream analytics.
This configuration uses BigQuery Data Access audit logs, the Logs Viewer IAM role (roles/logging.viewer), VPC Flow Logs, and Cloud KMS customer-managed encryption keys (CMEK). While these are important security controls, several critical gaps prevent them from meeting HIPAA and GDPR requirements.
roles/logging.viewer) role can read Admin Activity, System Event, and Policy Denied logs, but they cannot view Data Access audit logs stored in the _Default bucket. Auditors require the Private Logs Viewer (roles/logging.privateLogViewer) role to inspect Data Access logs.The organization only needed to encrypt BigQuery storage with customer-managed keys, sample VPC network traffic, and allow staff to view Admin Activity logs without accessing Data Access logs.
To audit Google support actions, Access Transparency is required, and to inspect and redact sensitive column values for analytics, Sensitive Data Protection must be used alongside CMEK.
This option relies on Admin Activity audit logs, Cloud Identity log sharing, and Cloud Logging field-level access controls. Each of these mechanisms serves a legitimate security function in Google Cloud, but they address entirely different layers of auditing and privacy than what the compliance requirements specify.
ADMIN_WRITE), such as creating a database instance or modifying IAM policies. They do not record DATA_READ or DATA_WRITE operations performed against Cloud SQL or BigQuery data, leaving user queries and exports unlogged unless Data Access audit logs are explicitly enabled.LogEntry payloads (such as an email address captured in a log message) from unauthorized log viewers. They do not discover, mask, or tokenize PII stored inside Cloud SQL tables or BigQuery datasets for analytics teams.The goal were solely to track resource configuration changes, centralize corporate user sign-in logs, and hide sensitive attributes appearing inside Cloud Logging log entries from certain IAM principals.
A common misconception is confusing log-entry redaction with database de-identification. Securing log payloads protects operational telemetry, whereas Sensitive Data Protection is required to scan and transform actual stored datasets.
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