Google Professional Security Operations Engineer Exam Questions

Comprehensive and Detailed Explanation

The correct answer is Option C. The incident description makes it clear that endpoint containment (by EDR) was insufficient, as the attacker successfully pivoted to privileged service accounts and began post-compromise activities (credential dumping, scheduled tasks).

The goal is to automate containment and minimize dwell time.

Option A is an enrichment/investigation action, not a containment action.

Option B is the opposite of automation; adding a manual approval step increases dwell time and response time.

Option D is a detection engineering task (creating a YARA-L rule), not a SOAR playbook (response) action.

Option C is the only true automated containment action that directly addresses the new threat. The anomalous behavior of the privileged accounts would raise their Entity Risk Score within Google SecOps. A modern SOAR playbook can be configured to automatically trigger on this high-risk score and execute an identity-based containment action. Revoking tokens and suspending sessions for the compromised high-privilege accounts is the most effective way to immediately stop the attacker's lateral movement and malicious activity, thereby accelerating containment and minimizing dwell time.

Exact Extract from Google Security Operations Documents:

SOAR Playbooks and Automation: Google Security Operations (SecOps) SOAR enables the orchestration and automation of security responses. Playbooks are designed to execute a series of automated steps to respond to an alert.

Identity and Access Management Integrations: SOAR playbooks can integrate directly with Identity Providers (IdPs) like Google Workspace, Okta, and Microsoft Entra ID. A critical automated containment action for compromised accounts is to revoke active OAuth tokens, suspend user sessions, or disable the account entirely. This action immediately logs the attacker out of all active sessions and prevents them from re-authenticating.

Entity Risk: Detections and anomalous activities contribute to an entity's (e.g., a user or asset) risk score. Playbooks can be configured to use this risk score as a trigger. For example, if a high-privilege account's risk score crosses a critical threshold, the playbook can automatically execute identity containment actions.

Google Cloud Documentation: Google Security Operations > Documentation > SOAR > Playbooks > Playbook Actions

Google Cloud Documentation: Google Security Operations > Documentation > SOAR > Marketplace integrations > (e.g., Okta, Google Workspace)

Google Cloud Documentation: Google Security Operations > Documentation > Investigate > View entity risk scores

Comprehensive and Detailed Explanation

The correct solution is Option B. This question requires a low-latency (5 minutes) notification for a silent source.

The other options are incorrect for two main reasons:

Dashboards vs. Notifications: Options C and D are incorrect because dashboards (both in Looker and Google SecOps) are for visualization, not active, real-time alerting. They show you the status when you look at them but do not proactively notify you of a failure.

Metric-Absence vs. Metric-Value: Google SecOps streams all its ingestion health metrics to Google Cloud Monitoring, which is the correct tool for real-time alerting. However, Option A is monitoring the 'total ingested log count.' This metric would require a threshold (e.g., count < 1), which can be problematic. The specific and most reliable method to detect a 'silent source' (one that has stopped sending data entirely) is to use a metric-absence condition. This type of policy in Cloud Monitoring triggers only when the platform stops receiving data for a specific metric (grouped by collector_id) for a defined duration (e.g., five minutes).

Exact Extract from Google Security Operations Documents:

Use Cloud Monitoring for ingestion insights: Google SecOps uses Cloud Monitoring to send the ingestion notifications. Use this feature for ingestion notifications and ingestion volume viewing... You can integrate email notifications into existing workflows.

Set up a sample policy to detect silent Google SecOps collection agents:

In the Google Cloud console, select Monitoring.

Click Create Policy.

Select a metric, such as chronicle.googleapis.com/ingestion/log_count.

In the Transform data section, set the Time series group by to collector_id.

Click Next.

Select Metric absence and do the following:

Set Alert trigger to Any time series violates.

Set Trigger absence time to a time (e.g., 5 minutes).

In the Notifications and name section, select a notification channel.

Google Cloud Documentation: Google Security Operations > Documentation > Ingestion > Use Cloud Monitoring for ingestion insights

Comprehensive and Detailed 150 to 250 words of Explanation From Exact Extract Google Security Operations Engineer documents:

The requirement to detect activity that is *unusual* compared to a *user's established baseline* is the precise definition of **User and Endpoint Behavioral Analytics (UEBA)**. This is a core capability of Google Security Operations Enterprise designed to solve this exact problem with **minimal effort**.

Instead of requiring analysts to write and tune custom rules with static thresholds (like in Option A) or configure external metrics (Option B), the UEBA engine automatically models the behavior of every user and entity. By simply **enabling the curated UEBA detection rulesets**, the platform begins building these dynamic baselines from historical log data.

When a user's activity, such as data download volume, significantly deviates from their *own* normal, established baseline, a UEBA detection (e.g., `Anomalous Data Download`) is automatically generated. These anomalous findings and other risky behaviors are aggregated into a risk score for the user. Analysts can then use the **Risk Analytics dashboard** to proactively identify the highest-risk users and investigate the specific anomalous activities that contributed to their risk score. This built-in, automated approach is far superior and requires less effort than maintaining static, noisy thresholds.

*(Reference: Google Cloud documentation, 'User and Endpoint Behavioral Analytics (UEBA) overview'; 'UEBA curated detections list'; 'Using the Risk Analytics dashboard')*