Question 650
A security team must solve this operational problem: The compliance team wants one inherited log export policy instead of configuring each team's project separately. Which implementation is the most direct fit?
Explanation
Correct Answer
Aggregated organization log sink addresses this case by the following supported operation: Configure a properly scoped organization or folder aggregated sink with supported inclusion and destination privileges. For this scenario (the compliance team wants one inherited log export policy instead of configuring each team's project separately), verify that a matching security event from another descendant project appears without a manually configured project sink.
Incorrect Answers
Cloud Logging retention configuration has a distinct purpose: Set log bucket retention and appropriate controls for the required log classes and jurisdiction. It instead applies when a regulated service needs audit records available for a specified retention period, not the current requirement (the compliance team wants one inherited log export policy instead of configuring each team's project separately). Here, verify that a matching security event from another descendant project appears without a manually configured project sink.
Security logging incident runbook has a distinct purpose: Follow an incident runbook that collects relevant audit and workload logs, isolates the affected identity and records containment actions. It instead applies when a suspicious service account is detected and responders need evidence preservation before revoking access, not the current requirement (the compliance team wants one inherited log export policy instead of configuring each team's project separately). Here, verify that a matching security event from another descendant project appears without a manually configured project sink.
Cloud Logging exclusion risk review has a distinct purpose: Scope log-exclusion filters carefully and confirm mandatory logs still reach protected buckets or sinks. It instead applies when teams want to reduce high-volume logs without accidentally removing mandatory security audit evidence, not the current requirement (the compliance team wants one inherited log export policy instead of configuring each team's project separately). Here, verify that a matching security event from another descendant project appears without a manually configured project sink.






Professional Cloud Security Engineer Practice Tests