You save $69.98
SY0-701 Premium Bundle
- Premium File 1044 Questions & Answers
- Last Update: Nov 18, 2026
- Training Course 167 Lectures
- Study Guide 1003 Pages
You save $69.98
A SOC automation rule sees a low-severity antivirus alert and a confirmed privileged login from an unknown device within one minute. Which escalation design is best?
Correlation provides a stronger case for timely response than either event alone. A human can validate the host, account and timing before disruptive steps. The ticket should include evidence links, severity rationale and proposed containment boundaries. The escalation record should explain which corroborated events raised the confidence level so the responder can challenge the alert if needed.
One uncertain endpoint signal may not warrant immediate isolation, but its proximity to a privileged login from an unknown device changes the combined risk. Correlation can reveal account misuse that neither event proves on its own. The SOC should examine device identity and timing and route the enriched case to a responder rather than suppress cross-signal investigation.
The combined event deserves timely triage, but automatic mass account shutdown based on one identity’s suspicious activity would disrupt unrelated users. A better escalation sends corroborated context and a prioritized investigation to an authorized responder before taking broad high-impact action.
Successful authentication supports that some factors were accepted, not that the device or session is safe. A stolen session, compromised endpoint or coerced factor can coincide with unusual host behavior. The automation should retain both observations and escalate the combined context for human validation, rather than allow authentication success to override other threat indicators.
A software team wants its CI pipeline to prevent deployment of a build with a critical vulnerable dependency while letting low-risk findings go through a documented exception review. Which automation fits?
Security gates can combine build scanning, vulnerability severity and risk exceptions without treating every finding identically. Approval should be limited and auditable. The team must ensure the tested artifact is the one promoted to production. A documented risk exception should identify the affected build, owner and expiration, with the protected deployment gate able to enforce its decision.
Scan reports improve visibility but do not provide the requested preventive gate. A critical known vulnerability could be released before the meeting occurs. Automated control should block or explicitly route risky builds through a documented approval process, while preserving verifiable package and build identity for remediation.
Transitive dependencies can execute within the deployed application and may contain exploitable flaws despite not appearing directly in a manifest. Ignoring them creates a blind spot in the critical-risk gate. The CI control needs validated dependency inventory, severity evaluation and an exception path that covers the actual released artifacts.
A zero-exception policy can create unnecessary disruption and may incentivize teams to disable scanning. The task explicitly allows reviewed low-risk exceptions. A more effective gate records severity, exploit context, ownership, expiration and approval, while reliably stopping critical unaccepted risks before promotion.
A security orchestrator calls a cloud API to quarantine compromised instances. Its automation token can also delete all tenant audit logs, although no workflow needs that capability. What should be changed?
A narrowly scoped service identity can perform intended quarantine without changing audit or billing settings. Token expiration, secure storage and API logs reduce abuse risk. The organization should validate that the orchestrator still functions under the restricted role. The integration should support prompt token revocation and separate read-only monitoring from the narrowly authorized containment operation.
Broad owner privileges expand the impact of a stolen or misused token. Automation should not receive unrelated destructive authority. Retry behavior should be solved through error handling, not excess permissions.
Moving a high-privilege credential into broadly accessible configuration or logs changes where it can be stolen; it does not narrow the power of the token or protect its lifecycle. An attacker could still delete tenant audit logs. The orchestrator needs a restricted quarantine-only identity and auditable key handling.
Trusted systems can have bugs or be compromised. Audit records help reconstruct automated containment and detect unusual calls. Deleting them would make token misuse harder to discover. Even trusted automation can be compromised or misconfigured, making API audit events essential to attribution and recovery.
An incident automation tool proposes isolating every machine that shares an IP prefix with one suspicious endpoint. Several business-critical servers would be affected. What control should prevent unnecessary disruption?
High-impact actions should consider corroborating evidence, dependencies and a defined approval path. A responder may isolate the confirmed host first while assessing lateral exposure. The automation should record why it acted and provide rollback if an alert was wrong. The playbook can require human signoff for mass quarantine while allowing tightly scoped automatic isolation of high-confidence individual threats. Broad containment should also have a reversible response and named decision authority, so operators can restore healthy critical assets if suspicion is disproven.
High severity on one machine does not prove that every neighboring asset is infected. Bulk isolation could interrupt unrelated business-critical services and amplify incident impact. The automation needs evidence of propagation, per-asset criticality and bounded containment authority; otherwise a human should approve broad actions after confirming their expected operational consequences.
Changing the grouping criterion does not fix the problem of taking disruptive action without per-asset evidence or an approved response threshold. Business-unit tags can include healthy systems supporting essential workflows. A proportionate control should assess confidence, the likely blast radius and appropriate human authorization before mass isolation or shutdown.
An appropriate automatic response for a single user workstation can be unsafe for clustered databases or services requiring coordinated failover. The playbook must incorporate asset criticality and thresholds for high-impact changes. Without those checks, an innocuous endpoint alert can trigger a preventable regional outage under the cover of standardized automation.
An organization relies on a custom incident orchestration platform maintained by one developer. It has no failover and the developer is leaving. Which security concern is most important?
Unmaintained custom logic can fail during incidents, and a single maintainer can leave critical knowledge unavailable. The organization should document dependencies, arrange support coverage and test recovery or replacement. Continued investment should reflect business risk, not only short-term development cost. A single unsupported orchestrator may fail during the very incident it is meant to coordinate; test manual fallback and failover.
Source control is an important safeguard against lost code, but rebuilding a security orchestrator also requires credentials, deployment dependencies, runbooks and competent maintainers. The single developer’s departure and absence of failover remain operational response risks. A repository copy alone does not prove another team can recover the platform or safely operate it during an incident.
Comments can help a future maintainer interpret some code, but they cannot operate a missing failover platform or transfer undocumented access, alert rules and deployment processes. The system needs handover, redundancy and supportability planning to address the stated single-person dependency.
A second configuration copy may make recovery preparation easier, yet it is not functional failover when both sites depend on one live control service and one person’s knowledge or credentials. The departure risk and common-mode outage remain. Real resilience requires tested restoration, separate authorized maintainers and attention to control-plane and secret-management dependencies.
A hospital's EDR detects a suspicious process, but the alert alone does not show successful access to sensitive files. What should govern formal incident declaration?
A documented incident threshold helps distinguish suspicious events from confirmed unauthorized actions. Correlating endpoint, identity and resource telemetry supports proportionate declaration and response. The hospital should retain evidence and escalate quickly when the impact or confidence warrants it. The incident threshold should be expressed in observable events and impact so analysts make consistent declarations across shifts.
EDR confidence can justify prompt triage or containment, but it does not necessarily establish access to sensitive records or the incident’s confirmed severity. A suspicious process may be blocked before it acts or may be a false positive. Declaration criteria should incorporate corroborated behavior, affected assets, evidence of unauthorized access and organizational escalation thresholds.
A confirmed unauthorized execution or disruption can meet documented incident criteria even when no sensitive file was read. Requiring proof of data exfiltration for every incident conflates an incident with a particular type of reportable privacy breach. Analysts should escalate substantiated malicious actions according to policy while separately investigating whether patient information was accessed.
Signed programs may be abused, vulnerable or delivered through compromised build systems. Signing does not establish every behavior is authorized. The EDR event still warrants investigation. A valid signature establishes some publisher and integrity properties, not a guarantee that a process cannot be abused or compromised.
A production plant discovers malware on an engineering workstation connected to safety-critical controllers. Full network isolation might stop the plant. What containment decision is best?
Containment must reduce attack spread without introducing greater process hazards. OT specialists can help identify safe network cuts and alternate control paths. The plant should preserve forensic evidence and validate that critical loops remain stable during changes. For safety-sensitive controllers, isolation must preserve necessary control signals while blocking the demonstrated malicious communications path.
Removing an internet path can reduce command-and-control and data theft but does not prevent the infected engineering station from issuing dangerous commands on the OT network. The plant’s immediate concern is preserving controller safety while constraining malicious local paths. Targeted isolation must consider the industrial process and authorized engineering functions.
Broad controller disconnection could cause unsafe process conditions. Emergency shutdown may be necessary in some cases but should follow safety engineering and incident procedures. Uncoordinated action is not the default best approach.
Keeping compromised connectivity open increases risk of controller access or further infection. A delayed response without safeguards is not acceptable. The team should act promptly with targeted controls suited to industrial availability.
After confirming a malicious scheduled task on a web server, responders have isolated the host. What sequence best describes eradication?
Eradication targets the attacker's foothold and contributing weaknesses after containment. Responders should preserve necessary evidence, remove malicious mechanisms and validate clean state. Reconnecting before verification risks recurring compromise through residual persistence. Validation should confirm that the original entry path is closed and persistence no longer starts after a reboot. Responders should preserve investigation evidence and verify scheduled tasks, service identities and exposed entry points before the separate recovery decision reconnects the system.
Removing one scheduled task may stop an observed trigger, but compromised credentials or additional persistence can reactivate the threat after reconnection. Eradication requires searching for related artifacts, closing the entry path and confirming the host is clean before the recovery stage. Otherwise, containment ends while the attacker may retain another means of access.
Deleting one file may remove an observable symptom but does not eradicate persistence or the entry path. The scheduled task can relaunch a payload, and compromised credentials may allow reinfection. Eradication requires removing all malicious artifacts and access mechanisms, fixing the weakness and validating that cleanup succeeded before recovery.
Replacing application files can remove one malicious artifact but leaves the exploited configuration and reusable credentials available to the attacker. A sound eradication plan addresses the root foothold, persistence, secrets and validation evidence. Restoring an apparently clean application without those fixes can lead to immediate re-compromise when connectivity resumes.
An e-commerce application has been rebuilt after an intrusion. It passes a simple ping test, but data integrity and user authentication have not been checked. What recovery gate should be required?
Recovery validation checks that the service is functional and that compromise mechanisms are gone. Authenticated transactions, integrity checks and log coverage should be tested under controlled conditions. The shop can then reopen in stages while monitoring for recurrence. Recovery acceptance should include functional transactions and security checks, not only successful machine boot or service startup.
A ping response only confirms limited connectivity and may originate from a load balancer. It does not validate application security or transaction data. Recovery needs evidence covering actual user workflows.
A rebuilt image may still contain vulnerable dependencies, misconfiguration or restored stolen credentials. Incident response should verify clean state and close the original entry path. Rebuild alone is not conclusive.
Public credentials would create immediate account abuse and compromise. User acceptance can occur with test accounts and approved roles. Restoring normal service should not weaken privileged access. Sharing privileged credentials with customers creates a new compromise path and is unrelated to verifying service recovery.
A company's incident review finds that phishing reports repeatedly wait two days before reaching the SOC. Which lessons-learned action is most meaningful?
Updating the escalation path and testing new reporting behavior addresses the observed delay. Ownership, channels and service targets should be clear to employees. Follow-up exercises can show whether incidents now reach responders quickly. Measure whether the updated route reduces time to report and time to containment during realistic future exercises.
Reminders may help people recognize phishing, but the measured defect is delay between report receipt and SOC review. Leaving the queue and ownership unchanged provides no evidence that the bottleneck will improve. Lessons learned should update routing, responsibility and measurable time-to-triage controls, then test the revised process.
A higher priority label is useful only when it causes the right team to receive and act on a report promptly. If messages still sit in the wrong queue for two days, changing a field does not fix escalation. The organization needs an accountable workflow with arrival-time measurement and follow-up verification.
Moving the metric's starting point can make a dashboard appear better while concealing the actual exposure window. The two-day delay remains a security problem regardless of which timestamp is shown to management. A useful improvement measures the full submission-to-triage interval and tests whether new escalation paths shorten it.
A remote support team wants to rehearse phishing escalation duties without sending actual malicious messages or isolating production endpoints. Which exercise is best?
A tabletop walks participants through a realistic incident timeline and the communications, containment and decision roles they would use. It can surface playbook gaps without endangering employees or production. The team should record action owners and follow-up tests for identified deficiencies. The drill should include realistic decision points, communications handoffs and safe escalation without sending harmful payloads to actual staff.
Collecting real credentials would create unnecessary security harm and is outside the stated simulation requirements. Training can use safe mock artifacts and controlled identities. The exercise does not need an actual attack against staff.
Broad unexpected shutdown could disrupt operations and distract from incident communications. Disruptive technical exercises require separate approval and safety planning. A tabletop is more appropriate for the requested low-risk rehearsal.
A generator exercise tests infrastructure continuity rather than phishing escalation roles. It may be valuable in a separate business continuity program. The team's current objective is incident response coordination. A generator test exercises site power continuity, not the phishing-driven incident response communication and role decisions being rehearsed.
Please check your mailbox for a message from support@examlabs.com and follow the directions.