Pass CompTIA SY0-701 Exam in First Attempt Easily
Real CompTIA SY0-701 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

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
$79.99 $149.97

Purchase Individually

  • Premium File

    1044 Questions & Answers
    Last Update: Nov 18, 2026

    $76.99
    $69.99
  • Training Course

    167 Lectures

    $43.99
    $39.99
  • Study Guide

    1003 Pages

    $43.99
    $39.99

CompTIA Security+ SY0-701 Practice Test 31

Question 300

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?

  1. Retain the antivirus event as low priority because its signature alone has limited confidence, and suppress escalation of the nearby privileged login unless another malware alert arrives.
  2. Automatically disable every account that shares the privileged employee’s organizational unit as soon as the two events correlate, without analyst review.
  3. Treat the privileged login as normal because password and multifactor checks succeeded, ignoring the device anomaly and nearby antivirus detection.
  4. Correlate the events, raise priority based on combined risk and route to a human responder with context.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

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.

B:

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.

C:

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.

Question 301

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?

  1. Implement severity-aware security gates with evidence, approved exception workflow and verifiable build identity.
  2. Generate dependency scan reports on every pull request but permit production deployment regardless of critical findings, relying on a later weekly security meeting.
  3. Block only directly declared vulnerable packages and suppress transitive dependency findings, even when those libraries ship into the final runtime artifact.
  4. Require all findings, including low-risk informational warnings, to block releases permanently unless the software vendor declares them absent.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

Question 302

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?

  1. Grant the token organization-wide owner privileges to simplify retries.
  2. Limit the integration token to required quarantine actions, protect its lifecycle and audit API use.
  3. Store the automation credential in a configuration variable readable by all development pipelines and their ordinary build-log viewers, instead of limiting API permissions.
  4. Stop logging API calls because the orchestrator is trusted.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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.

C:

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.

D:

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.

Question 303

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?

  1. Automatically quarantine all hosts in the same routed subnet when one endpoint alert is high severity, without verifying whether the hosts share a compromise mechanism.
  2. Replace bulk network isolation with an immediate shutdown of every server in the affected business unit, using a broad asset tag instead of the IP prefix.
  3. Apply confidence thresholds, asset criticality and human approval for high-impact bulk isolation.
  4. Use the incident playbook’s ordinary low-risk workstation quarantine rule for every asset, including critical servers, without a separate high-impact approval threshold.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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.

B:

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.

D:

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.

Question 304

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?

  1. Technical debt, supportability and single-point-of-failure risk threaten the reliability of automated response.
  2. Preserve the incident playbook source in version control and treat that alone as an adequate recovery plan, without a trained replacement owner or tested restoration.
  3. Add extensive comments to the orchestration source code but leave sole-maintainer credentials, deployment knowledge and recovery procedures untransferred.
  4. Replicate the platform configuration into another region but retain its single control service, shared signing keys and sole authorized maintainer.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

Question 305

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?

  1. Declare a confirmed major data breach whenever EDR assigns a high-confidence process-execution alert, using the detection score as a substitute for investigating access to protected files.
  2. Keep the event classified as harmless until investigators prove that patient files were exfiltrated, even if corroborated endpoint logs establish unauthorized code execution.
  3. Assume compromise is impossible because the process was signed.
  4. Apply defined incident criteria using corroborated behavior, asset impact and evidence of unauthorized activity.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

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.

B:

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.

C:

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.

Question 306

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?

  1. Block the infected workstation’s internet access but leave its engineering-to-controller access unrestricted because preventing exfiltration is sufficient containment.
  2. Use targeted isolation and approved OT coordination to constrain malicious paths while preserving necessary safety functions.
  3. Disconnect every controller without consulting process-safety personnel.
  4. Leave the infected workstation active and unrestricted until the next annual maintenance.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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.

C:

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.

D:

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.

Question 307

After confirming a malicious scheduled task on a web server, responders have isolated the host. What sequence best describes eradication?

  1. Identify and remove the persistence and malicious artifacts, correct exploited weaknesses and verify cleanup before restoring service.
  2. Remove the malicious scheduled task but restore the host to the network before rotating the exploited service credentials or verifying other persistence mechanisms.
  3. Delete the initial malware executable and close the alert, while retaining the malicious scheduled task and the exploited service-account credentials.
  4. Reinstall the web application from a trusted release but retain the vulnerable server configuration and the service-account tokens believed to have been stolen.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

Question 308

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?

  1. Treat network reachability as proof that the site is secure and ready for customers.
  2. Stop incident response permanently because rebuilding always removes every issue.
  3. Confirm trusted build integrity, authentication, data consistency and security monitoring before restoring normal connectivity.
  4. Publish administrator passwords to customers for a user-acceptance test.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

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.

B:

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.

D:

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.

Question 309

A company's incident review finds that phishing reports repeatedly wait two days before reaching the SOC. Which lessons-learned action is most meaningful?

  1. Send a general phishing-awareness reminder after each review while retaining the same two-day manual routing queue and unassigned escalation owner.
  2. Change the escalation process, assign accountable owners and test whether reporting time improves on later exercises.
  3. Increase the severity label on every phishing ticket but leave the slow routing workflow and notification destination unchanged.
  4. Redefine response time to start when a SOC analyst first opens the report rather than when the employee submitted it, then close the lessons-learned action.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

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.

C:

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.

D:

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.

Question 310

A remote support team wants to rehearse phishing escalation duties without sending actual malicious messages or isolating production endpoints. Which exercise is best?

  1. An incident-response tabletop with simulated events, role decisions and documented debrief.
  2. A real credential-harvesting attack against unaware employees.
  3. Unannounced shutdown of all production authentication systems.
  4. A generator test at the company's alternate data center only.

Explanation

Correct Answer

A:

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.

Incorrect Answers

B:

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.

C:

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.

D:

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.

CompTIA Security+ (SY0-701) Practice Tests

Purchase Individually

  • Premium File

    1044 Questions & Answers
    Last Update: Nov 18, 2026

    $76.99
    $69.99
  • Training Course

    167 Lectures

    $43.99
    $39.99
  • Study Guide

    1003 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports