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 financial services organization must implement a centralized log export architecture across all Google Cloud resources to comply with strict regulatory frameworks. The compliance and security requirements are:
europe-west3).Which log export and IAM configuration should the security team implement?
--include-children enabled, targeting a Cloud Storage bucket located in europe-west3 within a dedicated security project. Grant the sink's generated writer identity only the roles/storage.objectCreator role on the destination bucket.This solution uses a Google Cloud aggregated log sink at the organization level combined with least-privilege IAM permissions and regional Cloud Storage configuration to deliver a centralized, secure, and compliant log repository.
--include-children flag guarantees that all current and future child folders and projects automatically export their audit logs without requiring manual sink deployment per project.europe-west3 in a dedicated logging project guarantees that log archives remain stored within the mandated regulatory boundaries.roles/storage.objectCreator ensures write-only access—the writer identity can upload (storage.objects.create) new log objects but cannot read, overwrite, or delete existing log entries. Furthermore, centralizing storage in a restricted security project isolates logs from child project administrators.roles/storage.objectCreator role prevents log exfiltration (no read permissions) and log tampering (no overwrite or delete permissions).This architecture satisfies all compliance and isolation requirements by leveraging native GCP aggregated log sinks and atomic IAM role assignments, eliminating administrative overhead while enforcing strict data residency and write-only integrity.
europe-west3. Grant each project's default Compute Engine service account the roles/storage.objectCreator role on the bucket.This approach relies on distributed project-level log sinks configured in each individual project and delegates bucket write permissions to default Compute Engine service accounts.
serviceAccount:service-org-xxx@gcp-sa-logging.iam.gserviceaccount.com or project equivalent), not the Compute Engine default service account. Granting roles to the Compute Engine service account does not grant Cloud Logging permission to write objects and needlessly expands the attack surface.Each project required custom, localized export rules with no central organization-level governance or overarching compliance mandates.
--include-children disabled, targeting a BigQuery dataset in europe-west3. Grant the sink's generated writer identity the roles/bigquery.admin role on the destination dataset.This option sets up an organization-level sink without child inheritance and exports log entries into a BigQuery dataset while granting broad BigQuery administrative privileges.
--include-children restricts log capture solely to events generated directly at the organization resource level, omitting all logs generated in underlying folders and projects.roles/bigquery.admin grants full read, write, update, and delete access over all BigQuery tables and data, allowing data exfiltration and table deletion rather than enforcing secure write-only log streaming via roles/bigquery.dataEditor.The goal was only to capture administrative actions executed strictly on the Organization resource itself and analytics administrators required complete administrative control over dataset schemas and permissions.
--include-children enabled, targeting a multi-region Cloud Storage bucket in a dedicated security project. Grant the sink's generated writer identity the roles/storage.objectAdmin role on the bucket.This configuration establishes an aggregated sink across all child resources but directs exports to a multi-region Cloud Storage bucket and assigns broad administrative permissions (roles/storage.objectAdmin) to the sink's writer identity.
europe-west3.roles/storage.objectAdmin role grants storage.objects.delete, storage.objects.get, and storage.objects.update permissions alongside create permissions. This violates least privilege and creates risk of log tampering, unintended overwrites, and exfiltration if the service account identity is compromised.storage.objects.delete) where only append/write capability is necessary.The scenario required global data redundancy across multiple European territories and required the sink writer identity to manage object lifecycle states and perform bucket-level object deletions.
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