Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A multinational financial enterprise requires a centralized, tamper-proof security logging architecture across its entire Google Cloud organization to satisfy strict regulatory compliance requirements.
The security engineering team defines the following mandatory requirements:
Which combination of actions should the security engineer implement?
This approach attempts to use project-level sinks to export logs into the system-created _Default bucket of a centralized project, applying project-level IAM viewer roles for compliance staff.
_Default and _Required) do not support direct bucket-level locking or user-managed custom CMEK assignments in the same manner as user-defined buckets._Default bucket cannot be locked against configuration updates or log exclusions, leaving retention and data access open to administrative alterations.roles/logging.viewer at the project level grants read access to all non-data-access logs across the entire project rather than enforcing scoped access on a dedicated audit bucket view.The organization had a flat single-project architecture without organizational hierarchy, required only standard 30-day retention, and did not require bucket-level immutability locks or CMEK encryption.
This configuration routes organizational logs into the system-defined _Required bucket of the destination security project and grants auditors broad private log viewing privileges.
_Required bucket: When routing logs from an aggregated sink to a destination project, logs do not automatically pass through or store into the destination project's _Required bucket. The _Required bucket strictly stores log entries that originate directly inside that local project._Required bucket is hardcoded to 400 days and cannot be modified or extended to custom multi-year retention periods (such as 7 years).roles/logging.privateLogViewer grants permissions to read all log data, including sensitive Data Access audit logs, directly violating the requirement to restrict compliance auditors from viewing data access payloads._Required buckets._Required log bucket only holds events originating within that specific resource entity.roles/logging.privateLogViewer allows full visibility into data access logs across the resource.The team only needed to inspect locally generated Admin Activity and System Event logs within a single project for the standard 400-day window and required full access to all private log types.
This architecture establishes an organization-wide centralized logging pipeline that aggregates audit events, enforces data immutability, utilizes customer-controlled cryptography, and restricts access through granular log views.
--include-children setting automatically routes audit logs from all existing and future child folders and projects into the centralized logging project.logName : "cloudaudit.googleapis.com%2Factivity" and granting the roles/logging.viewAccessor IAM role allows compliance auditors to inspect administrative actions without accessing Data Access audit records.Native Cloud Logging features—specifically aggregated sinks, user-defined locked log buckets, and bucket log views—provide native end-to-end immutability, granular access scoping, and centralized query capabilities through Logs Explorer and Log Analytics without introducing third-party operational dependencies.
This option exports audit logs across the organization to a Google Cloud Storage bucket protected by Object Retention / Bucket Lock and CMEK, granting auditors read access through Cloud Storage IAM roles.
roles/storage.objectViewer) operate at the bucket or object prefix level. They cannot provide dynamic log entry parsing or granular log-view separation to allow viewing Admin Activity entries while preventing access to Data Access log files stored within the same archive hierarchy.AuditLog protoPayload structures to mask or exclude data access operations.The primary goal was cold data archiving for disaster recovery or third-party forensic tool ingestion where interactive querying, log views, and native log-based filtering were not required.
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