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 enterprise requires a centralized, tamper-proof audit logging architecture across all Google Cloud projects within its organization. The compliance and security teams mandate the following technical requirements:
sec-logging-prod project.Which architecture and set of configuration steps should the security engineer implement?
sec-logging-prod. Grant the sink's writerIdentity the Pub/Sub Publisher role (roles/pubsub.publisher), enable customer-managed encryption keys on the topic, and configure a Cloud Storage subscription that uses soft delete to prevent log deletion.This approach uses an organization sink targeting a Pub/Sub topic encrypted with CMEK, then delivers the messages into Cloud Storage using a Pub/Sub Cloud Storage subscription backed by soft delete protection.
The objective was to stream audit telemetry in real-time to a SIEM forwarder while providing a temporary safety net against accidental bucket deletion.
_Required and _Default sinks in every project to route to a BigQuery dataset in sec-logging-prod. Grant the BigQuery Data Editor role (roles/bigquery.dataEditor) to the Organization Administrator, encrypt the BigQuery tables with CMEK, and configure table expiration set to seven years.This configuration attempts to alter the built-in _Required and _Default log sinks across all projects to forward data to BigQuery tables configured with CMEK and a 7-year table expiration.
_Required sink cannot be modified, deleted, or redirected to an external destination; it is permanently configured to write mandatory Google Cloud platform logs to the local _Required log bucket.writerIdentity service agent, not the identity of the Organization Administrator._Required sinks cannot be disabled, reconfigured, or deleted.The requirement was to stream non-audit operational logs into an analytical data warehouse for interactive SQL querying with automatic table retirement after seven years.
sec-logging-prod. Grant the Storage Admin role (roles/storage.admin) to the default Compute Engine service account, configure default Google-managed encryption on the destination bucket, and configure an Object Lifecycle Management rule to delete objects after seven years.This option deploys standalone log sinks individually in each child project, utilizes the default Compute Engine service account for storage operations with administrative privileges, relies on Google default encryption, and uses standard lifecycle deletion rules.
roles/storage.admin violates least privilege; sinks only require roles/storage.objectCreator on the destination bucket.The scenario required decentralized log management with automated data purging after seven years without requiring CMEK, tamper resistance, or write-once-read-many (WORM) immutability.
--include-children pointing to the storage bucket in sec-logging-prod. Grant the sink's writerIdentity the Storage Object Creator role (roles/storage.objectCreator) on the destination bucket, assign the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) to the Cloud Storage service agent on the CMEK key, and enforce a 7-year locked retention policy using Bucket Lock.This architecture establishes an aggregated log sink at the Google Cloud organization root that centrally captures and routes audit telemetry across all descendant folders and projects into a hardened, CMEK-encrypted, and WORM-compliant Cloud Storage bucket.
--include-children automatically aggregates logs across every current and future child folder and project, routing them directly to the designated Cloud Storage bucket in sec-logging-prod.roles/storage.objectCreator to the sink's unique writerIdentity service account allows Cloud Logging to write new log objects to the destination bucket without granting unnecessary read or delete capabilities.roles/cloudkms.cryptoKeyEncrypterDecrypter to the Cloud Storage service agent ensures all incoming log objects written to the bucket are encrypted using customer-controlled keys in Cloud KMS.Aggregated sinks configured at the organization root combined with locked bucket retention policies and CMEK provide an end-to-end zero-trust logging architecture that completely isolates security records from individual workload owners.
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