Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise organization centralizes logs from multiple application projects into a dedicated centralized logging project. Your compliance and operations teams have established the following access control requirements for multi-project observability:
LogEntry payloads.Which solution should you implement to meet these requirements?
Field-level access control in Cloud Logging provides granular security by allowing administrators to restrict access to specific fields inside a LogEntry (such as jsonPayload.email or jsonPayload.ssn) while keeping the rest of the log record visible. Users without specific permissions can view the log entry, but restricted fields are masked or hidden.
roles/logging.viewer) ensures they can query, filter, and view application logs for debugging while automatically hiding sensitive PII fields.roles/logging.fieldAccessor role in addition to roles/logging.viewer gives them full clearance to read both unrestricted and restricted fields across the entire centralized repository.Field-level access control operates natively within the Cloud Logging platform. Compared to managing multiple log sinks or restricting access purely by entire log views, field-level controls enforce least privilege at the field level without complicating data routing topologies.
Log views provide subset filtering on a log bucket using a Cloud Logging query filter. They control access at the level of the entire LogEntry, determining whether a principal can or cannot view a specific log entry in its entirety.
The requirement was to segregate access based on log type, project ID, or resource type (for example, allowing developers to view only resource.type="k8s_container" while denying access to resource.type="audited_resource").
The Private Logs Viewer (roles/logging.privateLogViewer) role grants access to view private logs such as Data Access audit logs, while Logs Admin (roles/logging.admin) provides full administrative control over logging resources, sinks, and buckets.
roles/logging.privateLogViewer role actually grants access to sensitive Data Access audit logs, which contradicts the principle of least privilege for developers.roles/logging.privateLogViewer is intended for accessing sensitive audit records, not for restricting application payload fields.The objective was to delegate administration of the logging infrastructure to security personnel while permitting developers to view Data Access audit logs in sandbox environments.
Log sink exclusion filters prevent matched log entries from being ingested into a log bucket or routed destination, helping organizations manage logging costs by discarding unnecessary entries before storage.
The organization had a strict regulatory requirement that prohibited the collection or cloud storage of user email addresses under any circumstances across all teams.
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