Google Professional Security Operations Engineer 1-10

表示モード
画像位置
文字位置
理解度の自動記録
STATUS FILTER

Choose confidence levels to display

Loading...
Q1Google Professional Security Operations Engineer
Show answer
Correct answer: B. Use the curated detections in the Cloud Threats category to monitor your entire cloud environment.
The fastest way to begin threat monitoring in a multi-cloud environment is to enable the curated detections in the Cloud Threats category.
These are detection rules pre-built by Google that immediately cover common cloud security threats, so you can detect and respond to incidents without waiting to develop custom rules.
Option C’s Applied Threat Intelligence is centered on IOC-based matching, so for the goal of monitoring multi-cloud threats comprehensively and immediately, the Cloud Threats category is the appropriate choice.
Generating rules with Gemini (A) or contacting support (D) lack immediacy.
Google Cloud official documentation: Curated detections overview
Q2Google Professional Security Operations Engineer
Show answer
Correct answer: D, E
When authentication succeeds but authorization fails, permissions must be granted on both the SIEM side and the SOAR side.
Granting the roles/chronicle.viewer role to the IdP group in IAM provides the permission needed to access the Google SecOps instance.
Additionally, granting Basic permissions to the relevant IdP group in the SOAR Advanced Settings ensures correct access at the application level.
The key point is that both the IAM role on the SIEM side and the permission grant in Advanced Settings on the SOAR side are required.
Option B’s Workforce Identity Federation concerns authentication (which is already succeeding) and does not resolve the authorization problem.
Google Cloud official documentation: Configure feature access (IAM roles)
Q3Google Professional Security Operations Engineer
Show answer
Correct answer: B. Extract IOCs from recent reports in the Reports & Analysis feature, implement detection rules and lists in Google SecOps, and check whether they are present within your organization’s environment.
To determine whether you have already been attacked, you need to obtain actionable intelligence (IOCs) and match it against your environment for any traces of activity.
The Reports & Analysis feature of Google Threat Intelligence provides threat reports that contain IOCs.
By extracting these IOCs and implementing detection rules and lists in Google SecOps, you can search past and present telemetry and identify whether the attack group was active in your organization’s systems.
The TTP research in option C is for designing future detections, and options A and D do not directly determine whether impact occurred.
Google Cloud official documentation: Google Threat Intelligence
Q4Google Professional Security Operations Engineer
Show answer
Correct answer: C. Add the IOCs to a new or existing reference list, and modify the YARA-L logic of the detection rules to use that reference list.
The most effective approach is to add the IOCs to a reference list in Google SecOps and update the detection rules’ YARA-L logic to reference that reference list.
By consolidating IOCs into a reference list and referencing it from YARA-L, you can reuse the IOCs across multiple rules, simplify maintenance, and keep detection logic consistent.
This prevents duplicating IOCs in multiple places.
Referencing the threat group (A) or sharing a collection (D) are not well suited for directly applying IOCs to detection rules.
Google Cloud official documentation: Use reference lists
Q5Google Professional Security Operations Engineer
Show answer
Correct answer: A. Add a view to the playbook for each Google SecOps role.
The correct approach is to add a view to the playbook for each Google SecOps role.
Views let you control the information displayed by role, so each SOC role sees only the information relevant to its responsibilities.
The Case Comment in B and the General Insight in D add information rather than controlling display by role, and the task creation in C is for assigning tasks.
Google Cloud official documentation: SOAR cases and playbook views
Q6Google Professional Security Operations Engineer
Show answer
Correct answer: A, B
The appropriate response is both to ensure coordinated incident handling by notifying the workload owner and executing the response playbook, and to review the detection while investigating the Pod and related resources to understand the attack and determine the appropriate remediation.
The key point is to run notification and playbook execution in parallel with technical investigation, without prematurely deleting or silencing important evidence.
Option C deletes the Pod that serves as evidence, and option D silences the alert, both of which are inappropriate from a forensic standpoint.
Google Cloud official documentation: Container Threat Detection overview
Q7Google Professional Security Operations Engineer
Show answer
Correct answer: A. Create a rule within Google Security Operations (SecOps) that scans past outbound network connections against the ingested threat intelligence. Run that rule as a retrohunt across the entire tenant.
The fastest and most effective way to identify unknown C2 nodes within 24 hours is to create a detection rule in Google SecOps that compares past outbound connections against the ingested threat intelligence, and run it as a retrohunt across the entire tenant.
A retrohunt scans historical telemetry at scale and at high speed, so you can surface matches without waiting for new events to occur.
The statistical method in B and the WHOIS matching in D are inferior in terms of time or accuracy for exhaustively surfacing matches within the specified time frame.
Google Cloud official documentation: Manage rules and retrohunts
Q8Google Professional Security Operations Engineer
Show answer
Correct answer: C. Implement a parser extension on top of the prebuilt parser.
The recommended approach is to implement a parser extension on top of the prebuilt parser.
A parser extension lets you map additional fields from the raw logs to UDM fields without changing the existing, stable parser.
This allows you to customize new fields while retaining the original parsing logic.
Developing a new custom parser (A) requires significant effort and risks replacing a parser that is running stably.
Google Cloud official documentation: Manage parser extensions
Q9Google Professional Security Operations Engineer
Show answer
Correct answer: C. Use the EDR integration to quarantine the compromised asset.
The most effective first step to contain the threat while preserving forensic data is to use the EDR integration to quarantine the compromised asset.
Quarantine separates the server from the network to prevent further malicious activity, and because it does not wipe or reboot the server, evidence such as the persistence mechanism and the unauthorized file modifications is preserved.
Rebooting (B) risks losing volatile evidence.
The blocking in A and D remains at the network level, whereas EDR quarantine is appropriate for containing the asset itself.
Google Cloud official documentation: SOAR marketplace integrations (EDR)
Q10Google Professional Security Operations Engineer
Show answer
Correct answer: B. Use the statistics feature of search, and configure a Google SecOps SOAR job to format and send the report.
Use the statistics feature of search to generate the required tabular metrics, and run a scheduled SOAR job to perform the CSV export, ZIP compression, and email delivery every Monday.
A configuration that builds tabular data with search statistics and uses a SOAR job to automate CSV conversion, compression, and scheduled email delivery best matches the requirements.
This meets the exact formatting and delivery requirements with minimal manual work.
SOAR Reports is intended for standardized reports, whereas a SOAR job can more flexibly satisfy the granular requirements of CSV conversion, ZIP compression, and email delivery on a specific day of the week.
Google Cloud official documentation: Schedule and run SOAR jobs