Google Professional Security Operations Engineer (PSOE) Practice Test
Detect, Hunt, and Respond with Google SecOps.
500 scenario-based practice questions covering all 6 exam sections: platform operations, data management, threat hunting, detection engineering, incident response, and observability. Mapped to the official exam guide.
No credit card required · Upgrade to 500 questions for $11.99
500 Exam-Style Questions
7-Day Money-Back Guarantee
Is this for you?
You already triage alerts in Google SecOps and want practice choosing between a UDM search, a stats search and a retrohunt for a specific hunting question
You write YARA-L rules and want to test yourself on composite detections, rules that read risk values from data tables, and cutting repetitive false-positive alerts
You have to decide when SCC built-in detectors such as Event Threat Detection are enough and when a custom Google SecOps rule is needed, and want scenarios that force that call
You own log ingestion and want questions on Bindplane collection of Windows Event logs, parser extensions, aliasing fields for entity enrichment, and ingestion cost
Not for you if:
If your job is securing Google Cloud workloads through IAM, network security, data protection and compliance rather than running a SOC, the Professional Cloud Security Engineer (PCSE) exam is the closer fit
If you are looking for copied live exam questions: CertSharp does not offer braindumps, and every PSOE question is written against the official exam guide
The Google Professional Security Operations Engineer (PSOE) is a professional-level Google Cloud certification. The exam has 50–60 questions, runs 120 minutes, costs $200, and requires a passing score of Not published by Google. CertSharp provides 500 exam-style PSOE practice questions — 30 free with no credit card — each with a detailed explanation.
The PSOE guide is written as tasks inside three named platforms, Google SecOps, Security Command Center and Google Threat Intelligence, so questions read like SOC work orders rather than definitions. It follows the whole chain from telemetry and parsers through hunting, rules, playbooks and dashboards, and it repeatedly asks you to use AI features such as the Triage and Investigation Agent and natural-language prompts for hunting and rule writing.
Choosing telemetry and complementary tools
Platform operations asks you to prioritize sources such as SCC, GTI, Cloud Logging and Chrome Enterprise, and to justify running Cloud Logging, SCC built-in detectors and Google SecOps rules side by side. You also decide how service accounts, API keys, IAM conditions and Workforce Identity Federation give analysts and automations the access they need, including access through MCP.
Parsers, normalization and entity context
You need to judge whether a default parser is enough or needs an extension, evaluate normalization into UDM and new ingestion labels, and keep log costs down. The guide also tests the difference between event and entity data sources, matching them through aliasing fields, and loading GTI or third-party IOCs into the Entity Context Graph.
Detection rules that carry risk
Detection engineering covers YARA-L rules for new or low-prevalence processes, domains and IP addresses, composite detections that correlate activity over longer periods, and Risk Analytics with curated detections. You also configure SCC threat detectors such as Container Threat Detection, Cloud Run Threat Detection and Virtual Machine Threat Detection, and measure coverage against MITRE ATT&CK.
Playbooks, cases and feed health
Incident response questions ask which steps to automate in SOAR playbooks, which enrichments matter for a threat profile, and how a playbook updates findings in SCC or notifies stakeholders. Case management covers tags, SLAs, stages and closure reasons, and observability ends with Cloud Monitoring threshold alerts and silent source detection for feeds that stop sending logs.
Why CertSharp
Built for Exam Day, Not Just Study Time
Study guides teach concepts. We prepare you for the actual PSOE exam.
1
Google SecOps scenarios cover UDM searches, YARA-L 2.0 rules, parsers, and feeds the way the exam frames them
2
Detection engineering and incident response questions go beyond definitions, asking you to pick the rule logic or playbook step that fits the case
3
Covers all three platforms named in the exam guide: Google SecOps, Security Command Center, and Google Threat Intelligence
4
Every question carries an explanation that says why the right answer fits and why each distractor does not, with a link to Google documentation
Free Sample Questions
PSOE Practice Questions (Free Sample)
Real PSOE exam-style questions from our 500-question Google Professional Security Operations Engineer bank, each with the correct answer and a detailed explanation.
Question 1 — PSOE
An engineer wants to detect a password spray, where one source IP fails to log in to many different accounts in 15 minutes. Which rule logic is right?
A
Match on the source IP over 15m and require count_distinct of target user IDs above a threshold
B
Match on the target user over 15m and require a high total count of failures for that single account
C
Match on the hostname over 15m and require at least one successful login from a trusted subnet
D
Use a single-event rule that fires on the first failed login from any external source address
Correct answer: A — Explanation
A spray spreads few attempts across many accounts, so the grouping key is the source and the measure is distinct accounts. Grouping by user catches brute force instead, the trusted subnet condition is unrelated, and a single-event rule would alert on harmless isolated failures.
Question 2Data managementEasy
Okta System Log events must be ingested into Google SecOps. The vendor exposes a REST API that SecOps can poll with an API token. Which feed source type is appropriate?
A
A webhook feed that the security team has to call from a scheduled script each minute
B
A forwarder syslog input listening on port 514 on a Linux virtual machine
C
A Cloud Storage feed that watches a bucket where Okta stores its system log archive
D
A third-party API feed configured with the Okta log type and the API token
Show answer & explanation
Correct answer: D — A third-party API feed configured with the Okta log type and the API token
SecOps provides third-party API feeds that poll supported vendor APIs with credentials such as an API token, and Okta is one of those sources. A webhook feed receives pushed data rather than polling, Okta does not write archives into your bucket, and syslog is not the delivery method for this system log.
Question 3Incident responseMedium
A team wants a playbook to start just for alerts generated by one specific detection rule. How should it be configured?
A
Use an Alert Type trigger that matches the rule generator name of that detection
B
Create a custom list containing the rule and ask analysts to check it before starting playbooks
C
Rename the rule to match the playbook name and expect the platform to link them
D
Attach the playbook to the case after it is created and run it by hand each time
Show answer & explanation
Correct answer: A — Use an Alert Type trigger that matches the rule generator name of that detection
The Alert Type trigger matches on the rule generator field of an alert, so a playbook can be limited to alerts from one detection. Manual attachment is not automation, and renaming or lists do not link the rule to the playbook.
Question 4Detection engineeringEasy
Which prompt is most likely to produce a useful draft rule?
A
Create a rule that matches failed Okta logins and assigns a high risk score
B
Generate a rule that is secure and follows the usual practices of other companies
C
Create the best possible detection rule using the available data and common sense
D
Write a rule for bad logins that finds hackers in my network and handles them quickly
Show answer & explanation
Correct answer: A — Create a rule that matches failed Okta logins and assigns a high risk score
A good prompt names the event, the data source, and the desired score. Gemini in Google SecOps creates single-event rules from a natural language prompt, so a specific prompt gives a testable draft. The other prompts are vague and give the model no testable behavior.
Question 5Threat huntingEasy
During an active incident, IR needs to know within the hour whether lateral movement started from a compromised server. Which hunter contribution has the most value?
A
A retrohunt of a broad lateral-movement rule over the previous year of telemetry, queued until resources allow
B
A focused search of authentication and remote-service events with the server as principal, as a host list
C
A tenant-wide report of authentication failures over the last quarter, grouped by source country and user
D
A ranked inventory of exploitable vulnerabilities on the server, taken from the SCC security graph
Show answer & explanation
Correct answer: B — A focused search of authentication and remote-service events with the server as principal, as a host list
IR needs a fast, scoped answer, and authentication and remote-service events with the compromised server as the source show where it connected next. A retrohunt is queued by available resources and covers far more than this server, a tenant-wide quarterly report is too broad and slow, and a vulnerability ranking shows exposure, not movement that already happened.
Question 6ObservabilityMedium
A GTI report on an emerging campaign lists several file hashes and domains. How can an analyst best use this report to measure local exposure?
A
Search ingested telemetry for those hashes and domains, and chart any matches
B
Copy the report text into a case wall note and close the case as informational
C
Delete the related detection rules so duplicates are avoided
D
Export the report to Cloud Storage and wait for the next quarter
Show answer & explanation
Correct answer: A — Search ingested telemetry for those hashes and domains, and chart any matches
Searching ingested telemetry for the report's indicators shows whether the organization was touched, and charting matches communicates exposure. Pasting text into a note measures nothing, deleting rules reduces coverage, and waiting a quarter leaves exposure unknown.
Question 7Platform operationsMedium
A hunter is looking for users who authenticated from many different countries in a day. Which statistics aggregation gives the number of unique countries per user?
A
count applied to the event ID field, which returns the number of login events instead
B
max applied to the country field, which returns the single greatest country value
C
count_distinct applied to the login country field, grouped by user in the match section
D
array_distinct applied to the country field, which returns a list of values rather than a number
Show answer & explanation
Correct answer: C — count_distinct applied to the login country field, grouped by user in the match section
count_distinct returns the number of unique values, so applying it to the country field grouped by user gives distinct countries per user. count tallies events, array_distinct returns a list of values, and max returns just one value from the field.
Question 8Data managementMedium
A SOAR playbook should enrich file hashes with Google Threat Intelligence verdicts. How is access to the GTI API typically configured?
A
Attach the API key to the ingestion labels of the case so playbooks can read it
B
Share the analyst's personal login session with the playbook through the browser
C
Configure the Google Threat Intelligence integration with an API key, stored in the integration settings and used by the playbook actions
D
Embed the API key in each playbook step as plain text so the action can use it
Show answer & explanation
Correct answer: C — Configure the Google Threat Intelligence integration with an API key, stored in the integration settings and used by the playbook actions
SOAR integrations keep credentials such as the API key in the integration configuration, and the playbook actions use it when calling the service. Embedding keys in steps spreads secrets, labels are not a secure store and are not used for credentials, and playbooks cannot reuse browser sessions.
Question 9Incident responseHard
A detection rule produces many cases that analysts close as Not malicious. How can the SOC use case data to reduce this waste?
A
Change the closure reason to Malicious so that the rule appears effective to the detection engineering team
B
Count false positive closures per rule to find noisy rules, then tune them with exclusions
C
Disable each rule that produced at least one false positive during the quarter review
D
Delete the closed cases so that the rule looks cleaner in the monthly reports
Show answer & explanation
Correct answer: B — Count false positive closures per rule to find noisy rules, then tune them with exclusions
Counting benign closures per rule identifies noisy detections, which can then be tuned with the evidence from those cases. Deleting cases, misclassifying closures, or disabling rules at the first false positive harms data quality or coverage.
Question 10Detection engineeringMedium
A team wants high-fidelity curated alerts with minimal analyst workload at first. Which setting best fits that goal?
A
Enable the broad category first because wider coverage yields a smaller analyst queue
B
Enable the broad category with alerting on and set its severity label to low in the rule meta
C
Enable the precise category and keep the broad category off until the team has capacity
D
Enable neither category and wait for Risk Analytics to switch rule sets on by itself
Show answer & explanation
Correct answer: C — Enable the precise category and keep the broad category off until the team has capacity
Precise rules aim for high-confidence results and lower volume, while broad rules cast a wider net and generate more to triage. Broad coverage increases the queue rather than shrinking it, features do not switch on by themselves, and severity labels do not change how many alerts occur.
Want more PSOE practice questions?
Take the free PSOE practice test: 30 questions per session with instant explanations. Unlock all 500 questions plus timed exam mode for $11.99 one-time.
Everything you need to know about Google Professional Security Operations Engineer
What is the Google Professional Security Operations Engineer certification?
The Google Cloud Professional Security Operations Engineer certification validates your ability to detect, monitor, analyze, investigate, and respond to security threats using Google Security Operations (SecOps), Security Command Center (SCC), and Google Threat Intelligence (GTI). Google lists the exam at 2 hours and a $200 registration fee (plus tax where applicable), with 50-60 multiple choice and multiple select questions.
How hard is the Google Professional Security Operations Engineer exam?
It is a professional-level exam that tests hands-on judgment rather than definitions: writing and tuning YARA-L detection rules, choosing ingestion and parser approaches, running UDM and stats searches, and designing response playbooks. Google recommends 3+ years of security industry experience including 1+ years using Google Cloud security tooling.
Is the Google Professional Security Operations Engineer certification worth it?
It is worth considering if you work in or want to move into a SOC, detection engineering, or threat hunting role on Google SecOps. It shows hands-on skill with SecOps SIEM and SOAR, SCC, and GTI. Value depends on whether your employer or target roles use Google security tooling.
What experience do I need before taking the exam?
Google lists no formal prerequisites. The recommended experience is 3+ years of security industry experience including 1+ years using Google Cloud security tooling. Hands-on time in a Google SecOps tenant helps more than any amount of reading.
What topics are on the Google Professional Security Operations Engineer exam?
The exam guide has six sections: Platform operations (~13%), Data management (~20%), Threat hunting (~18%), Detection engineering (~20%), Incident response (~18%), and Observability (~11%). Topics include log ingestion and parsers, entity context, GTI IOCs, YARA-L rules, SCC threat detectors, SOAR playbooks, case management, and dashboards.
How many questions are on the Google Professional Security Operations Engineer exam?
Google lists 50-60 multiple choice and multiple select questions with a 2-hour time limit. Google does not publish a passing score.
How long should I prepare for the Google Professional Security Operations Engineer exam?
It depends on your SecOps experience. Many candidates with daily SOC experience plan several weeks, while those new to Google SecOps often need longer. Spend your time in a SecOps environment writing rules and searches, then use practice questions to find weak domains, especially Data management and Detection engineering, which carry the most weight.
What is the difference between Professional Security Operations Engineer and Professional Cloud Security Engineer?
Professional Cloud Security Engineer focuses on securing Google Cloud workloads: IAM, network security, data protection, and compliance. Professional Security Operations Engineer focuses on running security operations: ingesting logs, writing detection rules, hunting threats, and responding to incidents in Google SecOps, SCC, and GTI. They are separate exams and neither is a prerequisite for the other.
How much does the Google Professional Security Operations Engineer exam cost?
Google lists the registration fee as $200 (plus tax where applicable). You can take the exam online-proctored from a remote location or onsite at a testing center.
Is there a free Google Professional Security Operations Engineer practice test?
Yes. CertSharp offers a free Google Professional Security Operations Engineer practice test: 30 free questions per session with detailed explanations, no credit card required. The full 500-question bank, including timed exam mode with 60 questions, is $11.99 one-time with lifetime access, or $9.99/month for all certifications with Pro.
Also on CertSharp
Related to the PSOE Exam
Where PSOE candidates often go next, each with its own 500-question bank.