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.
An organization processes financial transactions in Google Cloud and stores application logs in a custom Cloud Logging bucket. The JSON payloads contain general debugging data alongside sensitive customer identifiers (jsonPayload.user.ssn and jsonPayload.user.credit_card).
Security requirements dictate that:
Which solution should the security team implement to satisfy these requirements?
jsonPayload.user.ssn and jsonPayload.user.credit_card, grant developers standard log viewing roles, and grant the compliance team the roles/logging.fieldAccessor role.Field-level access control in Cloud Logging is a granular security mechanism that allows administrators to hide specific fields inside a LogEntry (such as nested paths in jsonPayload, protoPayload, or labels) while keeping the rest of the log entry visible to authorized users.
--restricted-fields="jsonPayload.user.ssn,jsonPayload.user.credit_card" on the target log bucket, Cloud Logging automatically redacts and denies direct queries to those exact leaf paths for unauthorized users while still returning the parent log entries.roles/logging.viewer or roles/logging.viewAccessor) can query and inspect the unmasked payload fields in Logs Explorer. Only members of the compliance team granted the Log Field Accessor (roles/logging.fieldAccessor) role can view the restricted fields.roles/logging.fieldAccessor query logs, global searches bypass restricted field content, and returned LogEntry records omit the restricted values.Unlike log views or sink exclusion filters—which operate at the granularity of entire log entries—field-level access control allows development teams to maintain full context and operational visibility for debugging without exposing PII.
Log views provide read access control over subsets of logs stored within a Cloud Logging bucket by filtering entries based on resource types, log names, or payload contents.
LogEntry). They cannot hide or redact specific leaf keys inside a single record while showing the rest of the entry.roles/logging.viewAccessor role bound to specific log view resources.The requirement was to segment different categories of logs entirely (for example, allowing developers to see only k8s_container logs while compliance viewed audit logs).
Log Analytics allows querying log buckets using standard BigQuery SQL syntax and linking them to BigQuery datasets for advanced reporting and analytics.
The organization performed centralized security analytics exclusively in BigQuery and used BigQuery dynamic data masking with policy tags on structured warehouse tables.
jsonPayload.user.ssn and jsonPayload.user.credit_card to drop the fields during routing.Log Router exclusion filters evaluate incoming log entries against defined filter criteria and prevent entire matching LogEntry records from being routed and written to the designated destination sink.
The organization wanted to discard entire noisy debug log entries matching specific payload conditions to reduce Cloud Logging ingestion and storage costs.
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