Professional Cloud Security Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Create an organization-level aggregated sink pointing to a user-defined Cloud Logging bucket upgraded for Log Analytics with a linked BigQuery dataset, using the inclusion filter: log_id("cloudaudit.googleapis.com/data_access") AND NOT protoPayload.methodName =~ "^storage\.(buckets|objects)\.(get|list)$"
Create project-level sinks in every project routing to a central Pub/Sub topic connected to a BigQuery subscription, using the exclusion filter: protoPayload.methodName =~ "storage\.(buckets|objects)\.(get|list)"
Create an organization-level aggregated sink pointing to a Cloud Storage bucket destination with Autoclass enabled, using the inclusion filter: log_id("cloudaudit.googleapis.com/data_access") AND NOT protoPayload.methodName = "storage.*"
Create an organization-level aggregated sink with a BigQuery dataset as the direct sink destination, using the inclusion filter: log_id("cloudaudit.googleapis.com/data_access") AND protoPayload.serviceName != "storage.googleapis.com"
Create an organization-level aggregated sink pointing to a user-defined Cloud Logging bucket upgraded for Log Analytics with a linked BigQuery dataset, using the inclusion filter: 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.
Create project-level sinks in every project routing to a central Pub/Sub topic connected to a BigQuery subscription, using the exclusion filter: protoPayload.methodName =~ "storage\.(buckets|objects)\.(get|list)"
Create an organization-level aggregated sink pointing to a Cloud Storage bucket destination with Autoclass enabled, using the inclusion filter: log_id("cloudaudit.googleapis.com/data_access") AND NOT protoPayload.methodName = "storage.*"
Create an organization-level aggregated sink with a BigQuery dataset as the direct sink destination, using the inclusion filter: log_id("cloudaudit.googleapis.com/data_access") AND protoPayload.serviceName != "storage.googleapis.com"