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.
A security engineer needs to establish centralized detection and alerting across an enterprise Google Cloud organization for unauthorized API invocation attempts and policy violations blocked at the perimeter.
The solution must fulfill the following operational requirements:
Which configuration strategy should the engineer implement?
workload.googleapis.com metrics, and set up ActiveMQ integration alerting policies in Cloud Monitoring.This approach installs the Google Cloud Ops Agent on virtual machines to ingest guest-level syslog data and application runtime metrics into Cloud Monitoring.
workload.googleapis.com metrics reflect application-specific workloads rather than cloud audit telemetry.The requirement was to monitor application message broker queues and server latency inside Compute Engine instances.
_Default sink for storage in each individual project, and create project-level PromQL queries in Metrics Explorer to track cloudaudit.googleapis.com%2Fsystem_event.This configuration attempts to enable Data Access audit logging across the organization and use project-level metric exploration to query System Event audit logs.
cloudaudit.googleapis.com%2Fpolicy, whereas cloudaudit.googleapis.com%2Fsystem_event records automated Google maintenance and infrastructure events._Default project sinks prevents centralized organization-wide analysis and requires duplicating alerting policies across every project.The objective was to monitor Google Cloud platform maintenance events within a single standalone project.
AUDIT action inside Cloud Service Mesh on ingress gateways, and route the resulting envoy access logs directly to Cloud Monitoring using MQL alerting rules.This solution attempts to use Cloud Service Mesh authorization audit policies on ingress gateways to capture service-to-service API calls.
AUDIT action in the same manner as mesh workloads.The goal was specifically to audit HTTP request paths and methods between microservices deployed inside a Kubernetes service mesh.
cloudaudit.googleapis.com%2Factivity and cloudaudit.googleapis.com%2Fpolicy) into a central project, create a logs-based metric filtered on policy denials and method calls, and attach a Cloud Monitoring alerting policy with notification channels.This architecture centralizes organization-wide Cloud Audit Logs into a dedicated security logging project, establishes custom logs-based metrics targeting specific policy violation streams, and triggers automated alerts via Cloud Monitoring.
cloudaudit.googleapis.com%2Factivity) and logs access blocks enforced by perimeter controls (such as VPC Service Controls and IAM) in Policy Denied logs (cloudaudit.googleapis.com%2Fpolicy).RequestMetadata.caller_ip), method names (protoPayload.methodName), and resource identities, facilitating precise metric filtering.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