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 enterprise wants to implement a centralized log routing and analytical strategy across its Google Cloud organization. The security operations team defines the following requirements:
Which architecture and filter configuration should the security engineer deploy?
protoPayload.methodName =~ "storage\.(buckets|objects)\.(get|list)"This architecture establishes decentralized project-level log sinks that push log entries through a Pub/Sub topic into BigQuery using a BigQuery Pub/Sub subscription.
The requirement mandated real-time streaming ingestion into a third-party analytics pipeline or custom event-driven processor outside of Google Cloud Observability.
log_id("cloudaudit.googleapis.com/data_access") AND NOT protoPayload.methodName = "storage.*"This option exports audit logs directly to a Cloud Storage bucket destination using object lifecycle management (Autoclass) and an exact string match wildcard filter.
year/month/day/hour). It does not provide an interactive SQL query interface or direct connection to Looker Studio without loading the files into an analytics engine.=) in the Logging query language performs exact string or prefix matching depending on syntax, but does not parse regex wildcards like storage.* across method names accurately without the regex operator (=~). Furthermore, filtering storage.* removes all Cloud Storage logs rather than just routine get and list operations.The primary requirement was cold archival and disaster recovery backup of raw log files to object storage at minimal storage cost.
log_id("cloudaudit.googleapis.com/data_access") AND NOT protoPayload.methodName =~ "^storage\.(buckets|objects)\.(get|list)$"This solution pairs an organization-level aggregated log sink with a specialized Cloud Logging bucket upgraded for Log Analytics, integrated with BigQuery via a linked dataset and tuned with a regular expression filter in the Logging query language.
log_id("cloudaudit.googleapis.com/data_access")) while using regex matching (=~) and negation (NOT) to discard high-volume, low-fidelity Cloud Storage object and bucket get and list methods.^storage\.(buckets|objects)\.(get|list)$ accurately matches storage.buckets.get, storage.buckets.list, storage.objects.get, and storage.objects.list in a single concise evaluation.Using a Log Analytics linked dataset fulfills SQL analytics and reporting needs while retaining native Cloud Logging retention and security boundaries, avoiding the maintenance overhead and storage multiplication of traditional multi-destination exports.
log_id("cloudaudit.googleapis.com/data_access") AND protoPayload.serviceName != "storage.googleapis.com"This configuration routes log records directly to a native BigQuery dataset table while attempting to suppress all storage-related audit activity using a service name filter.
protoPayload.serviceName = "storage.googleapis.com" completely eliminates all Cloud Storage audit logs, including high-value security events like bucket permission updates (SetIamPolicy), bucket deletions, and object creations, rather than filtering only routine read/list operations.serviceName fails to differentiate administrative modifications from read/list telemetry.The goal was to export all non-storage audit logs directly to standard BigQuery tables for long-term external data warehousing without needing fine-grained method filtering.
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