A DevOps engineer wants to audit all actions performed by Google personnel on their customer data stored in Cloud Storage. They need to review logs that show access by Google employees and the reason for access. Which logging feature should they enable?
Access Transparency is the correct feature because it provides real-time logs of every action taken by Google personnel (and certain subprocessors) when accessing customer content, including reads, writes, and administrative operations. It complements Cloud Audit Logs by covering the 'Google-side' of the shared responsibility model, which no other logging option addresses. It must be explicitly enabled on the organization, folder, or project, and it works only for a defined set of Google Cloud services.
Why this answer
Access Transparency provides logs specifically showing when Google personnel access customer data, including the reason and justification for access. It is designed for auditing Google employee actions on customer data, which is exactly the requirement.
Exam trap
The trap is confusing Cloud Audit Logs with Access Transparency: candidates pick Audit Logs because they think it covers all access, but only Access Transparency logs Google personnel access with justification.
How to eliminate wrong answers
Option A is wrong because Cloud Audit Logs record actions by users and services in your project, not access by Google personnel to your data. Option B is wrong because Cloud Logging is a general log management service; it does not specifically capture Google employee access with justification. Option D is wrong because VPC Flow Logs capture network traffic metadata for VPC subnets, not personnel access to data.