Question 500
A nightly backup identity unexpectedly reads payroll data from a service it has never used. The finding has been corroborated and the response team has authorization to act. What action should the incident owner take to reduce the immediate risk?
- Restore auditing and investigate the modifying administrator
- Remove unauthorized grants and examine the initiator's session
- Revoke excessive access and rotate proven compromised app credentials
- Disable unauthorized anonymous links and review access grants
Explanation
Correct Answer
C:Changes should restore minimal function while interrupting misuse; this is the relevant response decision mechanism for Service principal unusual resource access given “A nightly backup identity unexpectedly reads payroll data from a service it has never used”.
Incorrect Answers
A:In SIEM audit policy tampering, reinstating coverage and preserving remote records limit the blind spot; the reported Service principal unusual resource access case calls for a different response decision conclusion because changes should restore minimal function while interrupting misuse.
B:For the alternative Privileged identity rare administrative action situation, both the newly privileged principal and grant actor require examination; by contrast, for Service principal unusual resource access response decision, changes should restore minimal function while interrupting misuse.
D:For the alternative Public sharing policy violation situation, closing share paths prevents further access while retrieval evidence is preserved; by contrast, for Service principal unusual resource access response decision, changes should restore minimal function while interrupting misuse.
Question 501
A staff member with legitimate system access modifies salary data outside an approved payroll cycle and deletes the change ticket. Which evidence collection choice best supports this investigation?
- Payroll row-change audit, account session and approval history
- Vault checkout audit, approval workflow and accessed secret inventory
- DLP evidence, policy scope and legal approval record
- DLP records, file classification and sanctioned-transfer approvals
Explanation
Correct Answer
A:The Unauthorized change to payroll records evidence “A staff member with legitimate system access modifies salary data outside an approved payroll cycle and deletes the change ticket” is decisive for corroboration because before-and-after values identify the alteration and its responsible principal.
Incorrect Answers
B:In Privileged vault secret retrieval anomaly, the records show which credentials were exposed and whether requests were authorized; the reported Unauthorized change to payroll records case calls for a different corroboration conclusion because before-and-after values identify the alteration and its responsible principal.
C:For the alternative Employee privacy during insider case situation, an incident indicator does not by itself justify unrestricted monitoring of private content; by contrast, for Unauthorized change to payroll records corroboration, before-and-after values identify the alteration and its responsible principal.
D:In Suspected employee intellectual-property export, data labels and destination context distinguish approved handoff from suspicious transfer; the reported Unauthorized change to payroll records case calls for a different corroboration conclusion because before-and-after values identify the alteration and its responsible principal.
Question 502
Malware is removed from a privileged admin laptop, but a hidden persistence mechanism may remain after local cleanup. Which evidence collection choice best supports this investigation?
- EDR findings, forensic timeline and trusted baseline image
- Endpoint process state joined to post-remediation proxy events
- Privileged access timeline and identity inventory
- Isolated restore logs, checksums and application consistency tests
Explanation
Correct Answer
A:In the Trusted endpoint rebuild case, the scope of compromise determines whether local remediation is sufficient; the observation “Malware is removed from a privileged admin laptop, but a hidden persistence mechanism may remain after local cleanup” makes this corroboration choice the fitting one.
Incorrect Answers
B:The choice is relevant to Incident eradication verification, where continued connections may reveal surviving persistence or an uninvolved second host; for corroboration in Trusted endpoint rebuild, the scope of compromise determines whether local remediation is sufficient.
C:For corroboration in Trusted endpoint rebuild, Credential recovery after domain compromise is a different mechanism: potentially exposed accounts and service dependencies define safe rotation order; here, the scope of compromise determines whether local remediation is sufficient.
D:The choice is relevant to Ransomware isolated restore validation, where a staged restore proves usable data and configuration dependencies; for corroboration in Trusted endpoint rebuild, the scope of compromise determines whether local remediation is sufficient.
Question 503
A remote office retains events on disk while the central SIEM displays a growing delay during a WAN outage. How should the analyst classify the activity at this stage?
- Multi-path duplicate logging
- Security telemetry time synchronization drift
- Schema mapping regression in log parsing
- Insufficient protected log retention
- Unprotected log transport
- Log forwarder buffering backlog
Explanation
Correct Answer
F:In the Forwarder queue saturation case, agents can queue events locally when collectors are temporarily unreachable; the observation “A remote office retains events on disk while the central SIEM displays a growing delay during a WAN outage” makes this classification choice the fitting one.
Incorrect Answers
A:In Duplicate event ingestion, two feeds can deliver the same source event twice and inflate detections and costs; the reported Forwarder queue saturation case calls for a different classification conclusion because agents can queue events locally when collectors are temporarily unreachable.
B:For the alternative Clock skew across security sensors situation, unsynchronized source clocks can invert an investigation timeline without changing actual causality; by contrast, for Forwarder queue saturation classification, agents can queue events locally when collectors are temporarily unreachable.
C:In SIEM parser field loss, a changed event format can break field extraction while raw ingestion continues; the reported Forwarder queue saturation case calls for a different classification conclusion because agents can queue events locally when collectors are temporarily unreachable.
D:For the alternative Immutable log retention requirements situation, accessible archives need retention and tamper controls appropriate to the investigation period; by contrast, for Forwarder queue saturation classification, agents can queue events locally when collectors are temporarily unreachable.
E:In Secure syslog transport mismatch, plain UDP syslog lacks transport confidentiality and native reliable delivery guarantees; the reported Forwarder queue saturation case calls for a different classification conclusion because agents can queue events locally when collectors are temporarily unreachable.
Question 504
A stolen workforce identity logs into Azure and then accesses an AWS application through federated SSO. What record is most useful for confirming this specific pattern?
- Google SecOps normalized event records and rule matches
- Identity-provider sign-ins linked to cloud role-session audits
- Admin Activity audit log methodName and authenticationInfo
- Cloud function execution logs and VPC or egress telemetry
Explanation
Correct Answer
B:In the Cross-cloud incident correlation case, federation identifiers help connect access paths that use different native principal names; the observation “A stolen workforce identity logs into Azure and then accesses an AWS application through federated SSO” makes this corroboration choice the fitting one.
Incorrect Answers
A:In Google Security Operations threat correlation, normalized fields permit multi-source detection when parsers are configured correctly; the reported Cross-cloud incident correlation case calls for a different corroboration conclusion because federation identifiers help connect access paths that use different native principal names.
C:In Google Cloud audit log principal investigation, the actor and method establish the API operation being investigated; the reported Cross-cloud incident correlation case calls for a different corroboration conclusion because federation identifiers help connect access paths that use different native principal names.
D:For the alternative Cloud function unusual outbound connections situation, runtime and network evidence tie unexpected connections to a deployed revision; by contrast, for Cross-cloud incident correlation corroboration, federation identifiers help connect access paths that use different native principal names.
Question 505
An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation. Which working hypothesis is best supported by these facts?
- Fragmented virtual-SOC coordination
- Broken co-managed ownership transition
- Unclear managed-SOC response authority
- Incomplete follow-the-sun case transfer
Explanation
Correct Answer
C:Given “An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation”, outsourced monitoring does not automatically delegate containment rights or define customer approval boundaries; that best addresses classification in Managed SOC provider accountability.
Incorrect Answers
A:That option fits Virtual SOC tool integration since a distributed SOC needs consistent taxonomy and central case routing despite having no single physical operations room; it does not fit the Managed SOC provider accountability classification scenario, where outsourced monitoring does not automatically delegate containment rights or define customer approval boundaries.
B:This option addresses Co-managed SOC handoff because shared SOC operations require one case owner when separate teams contribute findings to the same incident; the Managed SOC provider accountability classification question instead turns on the fact that outsourced monitoring does not automatically delegate containment rights or define customer approval boundaries.
D:This option addresses Follow-the-sun SOC transfer because continuous global coverage depends on structured handovers of evidence, decisions and pending actions; the Managed SOC provider accountability classification question instead turns on the fact that outsourced monitoring does not automatically delegate containment rights or define customer approval boundaries.
Question 506
Container nodes show sustained CPU saturation and an unapproved process connecting to mining pools. What lasting monitoring control should be added after the case?
- Enforce secure boot and monitor privileged driver loading
- Segregate backup administration and enforce protected retention
- Patch the exploited weakness and monitor lateral traffic surges
- Enforce image provenance and monitor unexpected miner traffic
Explanation
Correct Answer
D:Admission controls and runtime detection reduce repeat deployments; this is the relevant ongoing detection improvement mechanism for Cryptojacking in production cluster given “Container nodes show sustained CPU saturation and an unapproved process connecting to mining pools”.
Incorrect Answers
A:This option addresses Kernel rootkit suspected on endpoint because reducing unsigned or unexpected kernel code helps prevent persistence; the Cryptojacking in production cluster ongoing detection improvement question instead turns on the fact that admission controls and runtime detection reduce repeat deployments.
B:That option fits Ransomware backup recovery selection since separate credentials and immutable copies mitigate destructive attacker access; it does not fit the Cryptojacking in production cluster ongoing detection improvement scenario, where admission controls and runtime detection reduce repeat deployments.
C:This option addresses Worm-like propagation across segments because reducing reachable attack surface prevents recurrence after cleanup; the Cryptojacking in production cluster ongoing detection improvement question instead turns on the fact that admission controls and runtime detection reduce repeat deployments.
Question 507
A serverless workload begins contacting an unapproved Internet host after a dependency update. What security condition most directly explains the pattern?
- Federated identity investigation across clouds
- Google SecOps security analytics and detection
- Security Command Center cloud security posture findings
- Serverless egress anomaly
- Google Cloud administrative audit trail
Explanation
Correct Answer
D:Given “A serverless workload begins contacting an unapproved Internet host after a dependency update”, managed execution does not eliminate compromised code or supply-chain risk within functions; that best addresses classification in Cloud function unusual outbound connections.
Incorrect Answers
A:For classification in Cloud function unusual outbound connections, Cross-cloud incident correlation is a different mechanism: one compromise can span providers through common identity trust and session federation; here, managed execution does not eliminate compromised code or supply-chain risk within functions.
B:The choice is relevant to Google Security Operations threat correlation, where the platform supports log search and rule-based analytics over ingested security telemetry; for classification in Cloud function unusual outbound connections, managed execution does not eliminate compromised code or supply-chain risk within functions.
C:For classification in Cloud function unusual outbound connections, Google Cloud Security Command Center posture is a different mechanism: SCC provides centralized security findings and posture visibility for supported GCP assets; here, managed execution does not eliminate compromised code or supply-chain risk within functions.
E:For classification in Cloud function unusual outbound connections, Google Cloud audit log principal investigation is a different mechanism: cloud Audit Logs can record administrative actions with principal identity and target resource; here, managed execution does not eliminate compromised code or supply-chain risk within functions.
Question 508
An incident begins as a single infected laptop but investigators discover the same command channel on domain controllers. Which evidence collection choice best supports this investigation?
- Image hashes, custody signatures and transfer timestamps
- Approved communications plan and confirmed incident findings
- New affected-asset list and incident severity policy
- Incident action log and team ownership assignments
Explanation
Correct Answer
C:For corroboration in Incident severity change during response, critical hosts warrant reevaluation using the same approved prioritization rubric; this applies to the reported “An incident begins as a single infected laptop but investigators discover the same command channel on domain controllers”.
Incorrect Answers
A:For corroboration in Incident severity change during response, Evidence transfer between response teams is a different mechanism: these artifacts document integrity and who controlled the evidence; here, critical hosts warrant reevaluation using the same approved prioritization rubric.
B:The choice is relevant to Public incident communications control, where external statements must be grounded in validated facts and designated authority; for corroboration in Incident severity change during response, critical hosts warrant reevaluation using the same approved prioritization rubric.
D:The choice is relevant to Incident commander coordination gap, where a shared chronology shows who made changes and what evidence might have been lost; for corroboration in Incident severity change during response, critical hosts warrant reevaluation using the same approved prioritization rubric.
Question 509
A downloaded spreadsheet spawns a shell interpreter that retrieves code from an untrusted website. Which working hypothesis is best supported by these facts?
- Wide low-frequency password spraying
- Offline cracking of service-account tickets
- Ransomware impact activity
- Document-driven script execution
Explanation
Correct Answer
D:In the Malicious Office macro delivery case, a macro or embedded automation can launch child processes and pull a second-stage payload; the observation “A downloaded spreadsheet spawns a shell interpreter that retrieves code from an untrusted website” makes this classification choice the fitting one.
Incorrect Answers
A:In Password spraying across employees, an attacker spreads guesses across accounts to avoid per-user lockout thresholds; the reported Malicious Office macro delivery case calls for a different classification conclusion because a macro or embedded automation can launch child processes and pull a second-stage payload.
B:For the alternative Kerberoasting service-ticket harvesting situation, service ticket material can be collected and attacked offline when accounts use weak secrets; by contrast, for Malicious Office macro delivery classification, a macro or embedded automation can launch child processes and pull a second-stage payload.
C:In Ransomware file encryption, mass file modification plus recovery-suppression commands indicates an attempt to encrypt data and hinder restoration; the reported Malicious Office macro delivery case calls for a different classification conclusion because a macro or embedded automation can launch child processes and pull a second-stage payload.
Question 510
A server starts using a rare TLS client profile to contact an Internet host despite having no approved outbound integrations. The analyst has not yet established malicious intent or downstream impact. Which interpretive boundary is most relevant to this situation?
- Bytes sent do not tell whether the content was confidential
- TLS fingerprints are not stable or unique malware identifiers
- Scanning traffic does not itself prove any server was breached
- NXDOMAIN spikes can also reflect misconfigured legitimate software
- Constant periodicity can be ordinary service polling
Explanation
Correct Answer
B:In the Anomalous TLS client fingerprint case, library updates and common client stacks can change or share fingerprints; the observation “A server starts using a rare TLS client profile to contact an Internet host despite having no approved outbound integrations” makes this interpretation limit choice the fitting one.
Incorrect Answers
A:That option fits Unusual outbound data volume since packet size and direction need data classification and endpoint context; it does not fit the Anomalous TLS client fingerprint interpretation limit scenario, where library updates and common client stacks can change or share fingerprints.
C:That option fits East-west port scan detection since connection attempts establish exploration, not successful authentication or code execution; it does not fit the Anomalous TLS client fingerprint interpretation limit scenario, where library updates and common client stacks can change or share fingerprints.
D:This option addresses Domain-generation algorithm surge because broken search suffixes and failed service discovery create many misses; the Anomalous TLS client fingerprint interpretation limit question instead turns on the fact that library updates and common client stacks can change or share fingerprints.
E:That option fits Regular command beacon intervals since patch agents and monitoring clients also contact servers on regular schedules; it does not fit the Anomalous TLS client fingerprint interpretation limit scenario, where library updates and common client stacks can change or share fingerprints.