Free Security-Operations-Engineer Exam Braindumps
Professional Security Operations Engineer Questions 36–40 (page: 9)

Updated On: 10-Feb-2026

You work for a large international company that has several Compute Engine instances running in production. You need to configure monitoring and alerting for Compute Engine instances tagged with compliance=pci that have an external IP address assigned.
What should you do?

  1. Create a custom Event Threat Detection module that alerts when a Compute Engine instance with the compliance=pci tag is assigned an external IP address.
  2. Deploy the compute.vmExternalIpAccess organization policy constraint to prevent specific projects or folders with the compliance=pci tag from creating Compute Engine instances with external IP addresses.
  3. Create a custom Security Health Analytics (SHA) module. Configure the detection logic to scan Cloud Asset Inventory data for compute.googleapis.com/Instance assets, and Search for the compliance=pci tag.
  4. Use the PUBLIC_IP_ADDRESS Security Health Analytics (SHA) detector to identify Compute Engine instances with external IP addresses. Determine whether the compliance=pci tag exists on the instances.

Answer(s): D

Explanation:

The correct approach is to use the PUBLIC_IP_ADDRESS SHA detector, which already identifies Compute Engine instances with external IPs. You can then check for the compliance=pci tag on those instances to scope the findings. This leverages built-in SHA functionality instead of creating custom modules, providing efficient monitoring and alerting for PCI-tagged instances with external IPs.



Your company's analyst team uses a playbook to make necessary changes to external systems that are integrated with the Google Security Operations (SecOps) platform. You need to automate the task to run once every day at a specific time. You want your solution to minimize maintenance overhead.
What should you do?

  1. Write a custom Google SecOps SOAR job in the IDE using the code from the existing playbook actions.
  2. Create a Google SecOps SOAR request and a playbook trigger to match the request from the user to start the playbook with the relevant actions.
  3. Create a Cron Scheduled Connector for this use case Configure a playbook trigger to match the cases created by the connector that runs the playbook with the relevant actions.
  4. Use a VM to host a script that runs a playbook via an API call.

Answer(s): C

Explanation:

The best solution is to create a Cron Scheduled Connector in Google SecOps and configure a playbook trigger to execute based on the cases generated by the connector. This allows the playbook to run automatically at a specific daily time with minimal maintenance overhead, leveraging built-in scheduling and orchestration rather than requiring custom jobs or external scripts.



You have discovered that a server that hosts an internal web application has been accidentally exposed to the internet for 48 hours. Logging is enabled on the server. You want to use Google Security Operations (SecOps) to run a UDM search against the server logs to identify whether there have been any successful exploitations against it.
What event field search should you use?

  1. Perform a search for antimalware or endpoint security events by using the product_event_type UDM field.
  2. Perform a search for sign-on activity for user accounts that are not expected on the server by using the principal.user.userid UDM field.
  3. Perform a search for network traffic where the principal is rarely seen by using the principal.ip UDM field.
  4. Perform a search for process launches and commands that are rarely seen by using the metadata.event_type UDM field.

Answer(s): D

Explanation:

To check for successful exploitations, you need to look for abnormal process launches and commands that indicate post-exploitation activity. In Google SecOps UDM, this is done by searching with the metadata.event_type field, which classifies events such as process execution. Unusual or rarely seen processes provide strong indicators of compromise.



You have been tasked with creating a YARA-L detection rule in Google Security Operations (SecOps). The rule should identify when an internal host initiates a network connection to an external IP address that the Applied

Threat Intelligence Fusion Feed associates with indicators attributed to a specific Advanced Persistent Threat 41 (APT41) threat group. You need to ensure that the external IP address is flagged if it has a documented relationship to other APT41 indicators within the Fusion Feed. How should you configure this YARA-L rule?

  1. Configure the rule to detect outbound network connections to the external IP address. Create a Google SecOps SOAR playbook that queries the Fusion Feed to determine if the IP address has an APT41 relationship.
  2. Configure the rule to establish a join between the live network connection event and Fusion Feed data for the common external IP address. Filter the joined Fusion Feed data for explicit associations with the APT41 threat group or related indicators.
  3. Configure the rule to check whether the external IP address from the network connection event has a high confidence score across any enabled threat intelligence feed.
  4. Configure the rule to trigger when the external IP address from the network connection event matches an entry in a manually pre-curated reference list of all APT41-related IP addresses.

Answer(s): B

Explanation:

The correct configuration is to join live network connection events with Fusion Feed data on the external IP address and filter for explicit associations with APT41 or related indicators. This ensures that the detection not only matches direct IP addresses but also flags those with documented relationships to APT41 in the Fusion Feed, providing broader and more accurate detection than static lists or general confidence scores.



You are writing a detection rule in Google Security Operations (SecOps) SIEM that sends a risk score to the alert. You have access to Google Threat Intelligence (GTI) data through your Google SecOps subscription. You need to ensure that the threat score output in the detection logic informs the alert's risk score and is available for future detections.
What should you do?

  1. Use the outcomes section of your detection logic to pull UDM enrichment fields from the event data. Apply logic to determine the total risk outcome, and store the risk score as the risk_score variable
  2. Use the match section of your detection logic to filter out irrelevant entities. Store the remaining entities as the risk_score variable.
  3. Configure a feed in Google SecOps SIEM to ingest GTI data to automatically enrich the appropriate entities.
  4. Create a Google SecOps SOAR playbook to query GTI that uses the VirusTotal integration to enrich the alert. Modify the risk_score context value to match.

Answer(s): A

Explanation:

The correct method is to use the outcomes section of the YARA-L detection logic to apply logic on UDM enrichment fields (including GTI data), calculate the total risk outcome, and store it in the risk_score variable.
This ensures the risk score is attached to the alert and available for correlation in future detections.



Viewing page 9 of 28
Viewing questions 41 - 45 out of 133 questions


Post your Comments and Discuss Google Security-Operations-Engineer exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!