CompTIA Security+ SY0-701 Practice Test 52
Question 510
EDR has already isolated an accounting workstation after analysts observed malicious SMB lateral movement. A routine operating-system patch is available, and the installer now succeeds on the quarantined host, but responders have not determined whether attacker persistence or compromised credentials remain. Management proposes reconnecting it immediately because the patch completed. Which next sequence is defensible?
- Preserve investigative evidence, eradicate persistence or rebuild from trusted media, rotate exposed credentials, validate patches and controls, then authorize reconnection
- Reconnect after the patch installer succeeds, because patch completion removes every process and credential the intruder may control
- Wait for the next scheduled monthly patch window and restore full network reachability first so the workstation can fetch routine updates
- Restore the user's files onto the still-compromised OS and treat recovery of document access as proof that lateral movement has ended
Explanation
Correct Answer
A:The host has already been contained, so the next decision is whether it is safe to restore trusted operations rather than how to issue the first isolation command. Responders should preserve volatile and persistent evidence as appropriate, determine the intrusion scope, remove malicious persistence or rebuild the device, revoke compromised sessions and credentials, and apply verified patches. Endpoint protection, configuration baselines and monitoring should pass restoration checks before the incident commander authorizes controlled reconnection. A patch alone treats one vulnerability but cannot prove the attacker has lost access. This distinction between immediate containment, eradication and normal maintenance scheduling is the skill tested here and differs from the separate initial-isolation question.
Incorrect Answers
B:A successful operating-system patch can close a specific vulnerability, but it does not guarantee that a backdoor, malicious scheduled task, or stolen token has been removed. The workstation was already isolated for confirmed malicious lateral traffic, and rejoining it before validating eradication could allow that activity to resume. Patch status is one restoration prerequisite, not the entire incident response decision. Investigators should establish how persistence and credentials were affected before approving network access, rather than equating an installation status code with trust.
C:A normal maintenance window is designed for scheduled vulnerability treatment of otherwise healthy systems. This host is in an active incident and has been deliberately quarantined, so routine timing does not justify reconnecting it in order to collect updates. Containment can remain effective while responders preserve evidence and prepare trusted recovery media. Necessary security patches can be included in a controlled restoration workflow. Returning the endpoint to production first would recreate the lateral movement path before trust has been reestablished.
D:Recovering a user's documents is an availability step, but placing those documents on a compromised system does not remove malware or invalidate stolen sessions. The file restore may also reintroduce malicious content if backups are not checked. Security recovery must establish a trustworthy execution environment and access state, not merely make documents available again. Analysts should validate restored files separately and ensure the endpoint's containment remains in effect until the eradication and verification steps are complete.
Question 511
A university employee resigns, leaving a leased laptop, three assigned software licenses, a badge and a service API token. These assets are recorded in different systems and only the directory account is scheduled for disablement. The security manager asks for a lifecycle control that prevents forgotten entitlements and missing devices. Which solution is most effective?
- Disable the directory user and assume procurement will eventually collect the remaining assets without ownership links
- Use invoices as the only inventory and omit mappings from staff identities to service credentials
- Maintain an authoritative ownership and entitlement inventory integrated with joiner-mover-leaver offboarding tasks
- Track the leased laptop but treat application licenses and machine credentials as unrelated to employee departures
Explanation
Correct Answer
C:An authoritative asset and entitlement inventory links people, devices, software seats, badges and credentials to accountable owners and service relationships. Offboarding can then trigger collection, lease return, license reclamation, key revocation and verification of completed steps. The university should reconcile CMDB, HR, IAM and procurement data, with exceptions reviewed by designated stakeholders. A service API token may be owned by a team rather than one person; that dependency still needs documented ownership and rotation when a custodian departs. The benefit is traceability across the full lifecycle rather than a single directory disablement pretending to close all exposures.
Incorrect Answers
A:Directory deactivation reduces interactive login risk but does not necessarily revoke API keys, recover hardware or release costly licenses. Without a relationship between identity and assets, the organization cannot prove that the offboarding checklist covers all resources. Manual procurement follow-up may miss critical entitlements. A still-valid service token could retain access long after the directory login is disabled.
B:Purchase receipts reveal what was bought but often not who currently uses a device, license or service secret. If the token is omitted from staff ownership records, it may survive the employee's departure. Lifecycle governance needs current assignment and revocation evidence, not just historic expenditure. The responsible team should record who can revoke machine credentials after an employee departure.
D:Physical equipment is one part of asset management. Unused software accounts and long-lived API secrets can create cost and security exposure after a leaver's account is disabled. Treating those assignments as outside offboarding leaves important residual access routes and prevents a complete custody record. Both security and finance need evidence that all assigned assets were returned or deprovisioned.
Question 512
Finance finds no corporate purchase orders for a document-sharing SaaS provider, yet identity-provider logs show hundreds of employees authenticating to it and approving third-party access grants. Many use personal payment cards and browser-only clients. Which discovery method best establishes the unapproved service footprint?
- Look only at procurement and approved-app catalog entries because personal-card subscriptions are not company assets
- Collect voluntary SaaS lists from employees but exclude sign-in and OAuth consent data from analysis
- Scan installed desktop applications and ignore cloud tools used exclusively through browsers
- Correlate identity-provider sign-ins, proxy traffic and OAuth grants with procurement and sanctioned-application inventories
Explanation
Correct Answer
D:Shadow IT is best found by reconciling multiple independent signals: user sign-ins, network requests, OAuth app grants, corporate purchasing and the approved SaaS catalog. The organization can identify which services are used, which corporate data scopes were authorized and which subscriptions lack security review. Investigate business need, migrate or sanction acceptable tools and revoke unsafe grants with appropriate communication. The absence of a procurement record is not proof of absence; personal-card adoption is common. Correlation can also reveal vendor risk, retention concerns and account lifecycle gaps that a one-dimensional software inventory would miss.
Incorrect Answers
A:Purchasing records omit tools acquired outside the corporate procurement process. The missing invoices are part of the shadow-IT signal, not evidence that employees are not using the service. Discovery needs technical observations as well as business inventory to capture unsanctioned browser applications. A browser login through a personal subscription may leave no corporate finance trail at all.
B:Self-reported inventories are helpful but may omit forgotten subscriptions or underestimate permissions granted through single sign-on. Authentication and consent telemetry can reveal actual use and data-access scope. Excluding it removes an independent evidence source that could identify risky integrations even when employees believe the product is harmless. Unknown OAuth permissions may allow a SaaS provider to read confidential documents after the session ends.
C:Browser-only SaaS leaves little or no installed agent on an endpoint. An installed-software scan can miss the entire service despite intensive daily use. Web proxy and identity telemetry provide a more complete view of cloud access than endpoint package inventories alone. The identity logs provide evidence of browser-based usage that installed-package scans cannot detect.
Question 513
After a storage-server refresh, a contractor stacks removed solid-state drives in an unlocked closet. Nobody records serial numbers, sanitization status or final custody, although several drives formerly stored restricted customer records. What immediate security and asset-management risk should be escalated?
- Assume the contractor's work order proves all removed drives were securely destroyed without examining device identifiers
- Record only newly installed drive serial numbers because the old units are no longer in active service
- Check encryption on replacement disks while keeping untracked former storage devices in the unlocked closet
- Potential loss or disclosure of restricted-data media with no documented chain of custody or verified disposal
Explanation
Correct Answer
D:Removed storage can still hold recoverable customer information, and unlocked, untracked drives present a direct exposure and evidence problem. Secure the units, identify each serial number and owner, preserve custody records, and perform approved sanitization or physical destruction appropriate to media type and data classification. For solid-state drives, ordinary file deletion may not reach all cells; vendor-supported crypto-erase or verified destruction might be required. Obtain verifiable disposal evidence and reconcile it to the asset register. The risk remains even though the original servers were successfully refreshed, because end-of-life handling is part of the information lifecycle.
Incorrect Answers
A:A removal work order can show a maintenance activity occurred, but it is not equivalent to evidence that each specific data-bearing unit was sanitized or destroyed. An unlocked closet permits unrecorded access. Serial-level mapping and witnessed disposition are needed to close the custody gap. A verified destruction record should match the serial number of the individual retired drive.
B:Old media retain potential confidentiality obligations after they stop serving production workloads. An inventory limited to new disks cannot show where the removed units went or whether they were securely processed. Hardware lifecycle management extends through transfer, return and disposal. The agency still needs to prove where each data-bearing removed disk was transferred or destroyed.
C:Encryption on replacement drives improves future storage protection but does not retroactively secure customer information on removed disks. The firm must determine whether old volumes were encrypted and how keys were controlled, but should still secure and account for the actual retired media immediately. Old disks can retain data even after new encrypted drives are installed in the chassis.
Question 514
A municipal agency plans to delete all backup sets after thirty days to reduce storage bills. However medical records in some archives have statutory retention obligations, while older customer marketing data may have exceeded its permitted retention period. Which method should govern disposal decisions?
- Apply the shortest operational backup cycle universally and try to restore legally held data from somewhere else later
- Classify backup contents by retention obligations and legal hold, then dispose of sets eligible for verified secure deletion
- Keep every backup for the longest statutory period identified anywhere in the agency
- Retain every backup forever because a future legal request might theoretically arise
Explanation
Correct Answer
B:Retention and disposal should follow records classification, regulatory obligations, contractual requirements and active legal holds. The agency can define schedules by dataset and backup type, suspend deletion where holds apply and securely dispose of records once permitted. Where mixed content complicates deletion, redesign backup segmentation or document a controlled exception rather than applying the wrong blanket period. Maintain disposition evidence and review holds regularly. The objective is both avoiding premature destruction and limiting unnecessary long-term personal-data exposure. A single short or indefinite retention window fails because different information classes have different lawful requirements.
Incorrect Answers
A:A uniform thirty-day deletion can destroy records that the agency has a legal duty to retain. Once a backup is securely erased, a later restoration may be impossible. The retention plan must map actual record categories and holds before deletion instead of hoping another copy exists. A legal hold must be resolved before deletion irreversibly removes records needed for evidence.
C:Keeping all archives for the maximum period prevents some premature deletions but may retain unrelated personal data without purpose, increasing breach impact and compliance risk. A legal hold on one category does not automatically justify indefinite or maximal retention of every other dataset. Data-class separation is a better governance response.
D:Unlimited retention creates growing confidentiality, cost and privacy obligations and may violate deletion requirements after a lawful purpose expires. The possibility of a hypothetical future request does not override a defined records schedule. The agency should honor actual holds and dispose of eligible material securely and verifiably. Retention schedules should limit unnecessary long-term storage of personal information when no exception applies.
Question 515
A logistics company uses an edge firewall that no longer receives firmware security fixes. A replacement is funded for the next quarter, but the device must remain operational for current freight routes. The asset owner asks what governance evidence should justify those three months of exposure. Which option is strongest?
- Run repeated vulnerability scans and record their output as if scanning repaired the unsupported firmware
- Limit admin login to a VPN but ignore other vulnerable services the device exposes to users
- Record a time-bound owner-approved risk exception with network restrictions, monitoring and a committed supported replacement date
- Declare the appliance safe indefinitely when the current logs show no successful attack attempts
Explanation
Correct Answer
C:An unsupported firewall remains exposed to flaws that may never receive fixes. For a limited business necessity, the owner can approve a documented exception with scope, business rationale, expiry, restricted reachability, compensating monitoring and a specific migration plan. Review risk if threat conditions change, and ensure the replacement is a supported platform with tested routes and policies. The exception acknowledges residual exposure; it does not state that monitoring or a VPN makes old firmware safe. Accountability and a dated remediation path are central to responsible risk management during the quarter.
Incorrect Answers
A:Scanning improves awareness of defects and may confirm exposure, but it does not provide unavailable vendor patches. Repeated scans can also introduce operational risk to fragile network devices. Compensating controls and replacement planning are still necessary to treat the unsupported appliance's residual risk. The manufacturer will not supply patches, so direct network exposure still needs compensating restrictions.
B:Restricting administrative access is helpful but does not necessarily protect every reachable vulnerable service. The owner should review firmware flaws, traffic reachability and segmentation rules across the device's broader attack surface. A narrow login restriction alone may leave exploitable data-plane or management components exposed. The risk review must consider how the firewall processes traffic, not only how operators log in.
D:Lack of visible exploitation does not prove that an exposed unsupported appliance is safe. Logs can be incomplete, and future flaws may remain unpatchable. A permanent exception would contradict the stated plan to replace the device and ignore evolving risk that must be reviewed by accountable owners. The replacement deadline and time-bounded exception remain necessary even when current monitoring is quiet.
Question 516
A scanner reports a configuration weakness on a customer support portal. Later, under a signed and time-limited testing authorization, a penetration tester uses the weakness to obtain another user's protected account details and records the exact impact. Management asks how the two pieces of evidence differ. Which answer is correct?
- An authenticated scan proves account takeover whenever it identifies a suspicious setting, even without attempting access
- A permitted exploit trial is only an inventory scan because it targets the same web endpoint
- Repeating the scan creates proof of practical unauthorized access without a demonstrated exploitation path
- Scanning identified a candidate weakness; controlled penetration testing demonstrated exploitability and business impact
Explanation
Correct Answer
D:Vulnerability scanning identifies potential weaknesses through automated probes, version information and configuration checks. A controlled penetration test can demonstrate how a weakness is exploited under approved rules of engagement, providing stronger evidence about practical impact. Here the tester accessed protected details that the scanner only predicted might be exposed. Retain both artifacts, state scope and assumptions, and ensure testing did not exceed authorization or damage customer data. A demonstrated exploit path guides remediation priority but does not imply that criminals previously used it. The distinction is discovery versus validated exploitation, not a claim that scanning is useless.
Incorrect Answers
A:A configuration flag can indicate likely exposure but may have compensating controls or false positives. An authenticated scan does not automatically show that a protected account was actually accessible to an unintended user. Practical validation supplies additional evidence, subject to safe authorized scope. The scan finding should remain a hypothesis until a controlled test demonstrates a real authorization bypass.
B:An authorized tester actively exercised the weakness and observed exposure of another user's data. That is a different activity and assurance level from collecting configuration information. Sharing the same endpoint does not make an exploitation demonstration equivalent to passive or automated discovery. The tester confirmed protected account data exposure, which a simple discovery probe had not shown.
C:A repeated scan can increase confidence that the misconfiguration persists, but it still may not prove access to another customer's account. Evidence of exploitability requires observing the security boundary being crossed, with documentation of test steps and limitations. Duplicate reports alone do not establish impact. A repeat configuration finding increases confidence but does not establish the demonstrated business impact.
Question 517
A Linux fleet runs a distribution package whose upstream version number is listed in a security scanner's vulnerability rule. The distribution vendor says it backported the fix into the same visible version identifier, and the team has a signed package build record. What should the vulnerability analyst do before declaring these servers exploitable?
- Treat the upstream version string as conclusive proof that the vulnerable code remains present
- Disable vulnerability scanning across the whole fleet so package-version false positives stop appearing
- Accept every distribution package as secure without examining the specific build or advisory
- Verify distribution security advisories, installed build metadata and the affected code path to determine whether the backport applies
Explanation
Correct Answer
D:Upstream versions are useful signals, but enterprise Linux distributions commonly backport security fixes while retaining a stable upstream package version. Validate the vendor's advisory, package release suffix and signed installed build, then inspect or test whether the vulnerable code path remains. Document the evidence so scanner exceptions are narrowly justified and can expire when configurations change. If the vendor backport does not apply to that host, prioritize remediation accordingly. The right outcome is evidence-based vulnerability status, not unconditional acceptance or rejection of the scanner's version match. Recorded remediation decisions should identify the precise package release and relevant vendor bulletin.
Incorrect Answers
A:Distribution maintainers may patch a vulnerability without adopting a newer upstream version number. A scanner that relies only on that string can generate false positives. The analyst needs build-level and vendor-advisory evidence, not a binary conclusion from the user-visible package name alone. Vendor backport evidence may contradict the vulnerable-version heuristic despite the unchanged upstream number.
B:Disabling all scanning would hide unrelated vulnerabilities and configuration defects. A single parsing limitation calls for improved validation, exception evidence or scanner configuration, not a permanent loss of visibility across servers. Finding management should preserve the reason a specific reported issue was adjudicated. Create evidence-backed exceptions for affected package builds rather than disabling unrelated fleet detections.
C:Backport claims still require checking the exact installed package build and the applicable vendor bulletin. Different architectures or repository channels may not carry the same fix. Assuming all distributor packages are safe without evidence would create a false-negative risk equivalent to trusting the scanner blindly. A host may use an old repository or unpatched build even under the same distribution name.
Question 518
An emergency web application hotfix has been deployed to the Internet-facing service. The package manager reports success, but the original vulnerability allowed an unauthorized object modification and the affected endpoint has not been retested. What verification would justify closing the security finding?
- Run an authorized targeted validation against the deployed endpoint to confirm the original exploit condition is no longer possible
- Close the finding solely because the installer returned a successful exit code and lists a new version
- Rely exclusively on a vendor advisory stating the issue is fixed, without checking the running application
- Defer verification until next month's broad scan despite the hotfix being deployed under emergency change
Explanation
Correct Answer
A:A targeted scan or safe authorized retest checks that the actual production behavior no longer permits the previously observed unauthorized action. Use representative roles, the affected path and documented acceptance criteria, while avoiding unnecessary changes to live data. Package installation is a prerequisite but not conclusive evidence of effective remediation; configuration, caches or an incomplete rollout can leave an endpoint vulnerable. Capture results and update the ticket only when the tested condition passes. This authoring decision concerns post-remediation validation, not a full penetration campaign or unrelated performance measurement. Validate both the business action and access denial, not merely the reported package number.
Incorrect Answers
B:An installation result confirms that a package transaction completed according to the installer, not that the intended code path is corrected on every instance. A misconfigured deployment or still-running old process could leave the application exposed. Closure requires evidence from the service actually serving requests. The target may still route requests to instances running an older application binary.
C:Vendor advisories establish what a published fix is designed to address, but cannot prove the organization's running service incorporated it correctly. Application-specific configuration and deployment routing matter. Local targeted validation is necessary to confirm the exploit path has been closed under the environment's real access controls. The vendor's patch claims must be corroborated against the actual deployed and reachable code.
D:A routine monthly scan can provide later assurance, but waiting leaves a high-risk emergency finding unverified in the meantime. A carefully scoped validation can be performed without disrupting the application. The security team should not mark remediation complete or defer all evidence collection until the next broad schedule. The emergency finding should not remain unverified through another month of public exposure.
Question 519
A vulnerability-scanning team requests a single Domain Administrator account to conduct credentialed checks on all Windows and Linux servers. The proposed password would sit in a static scan configuration for a year, readable by multiple operators. The security architect wants detailed findings with minimal identity risk. Which design is preferable?
- Use scoped dedicated scan accounts with only necessary platform permissions, protected credentials, rotation and audit logs
- Create a single Domain Administrator scan identity stored in a password vault with rotation and detailed access logging.
- Run only unauthenticated external-port scans and assume they produce the same operating-system and package findings as credentialed checks.
- Reuse each administrator’s personal privileged account for scanning and put encrypted copies of those credentials into the scanner configuration.
Explanation
Correct Answer
A:Credentialed scanning can improve patch and configuration coverage without granting every scan process domain-wide administrative authority. Create purpose-built identities with bounded permissions on target platforms, securely store credentials, rotate them and review scan usage. Where a tool genuinely requires elevated rights, restrict that elevation to the smallest system set and window. Monitor logs and protect scanner infrastructure because it becomes a high-value credential holder. This balances depth of findings against blast radius if the scanning system is compromised. Generic convenience should not be mistaken for an authorization requirement. Scanner credentials should be distinct from human administrator accounts and reviewed against actual check requirements.
Incorrect Answers
B:A secure vault and rotation reduce exposure of privileged credentials, and access logs can establish who checked them out. These features do not justify a Domain Administrator account for routine checks across disparate platforms. If compromised, that shared identity could control a large portion of the environment. The scanning service should instead receive documented, platform-specific read access sufficient for its checks, with separated accounts and narrowly scoped privileges.
C:External scans are useful for reachability and service fingerprinting without distributing host credentials. They usually cannot inspect all installed software, local security configuration or package patch levels that a properly scoped authenticated scan can review. The organization explicitly wants detailed findings, so removing credentialed assessment entirely sacrifices necessary visibility. Protected, least-privilege scan identities preserve depth without defaulting to domain-wide administrative authority.
D:Encrypting scanner configuration can reduce accidental disclosure of stored passwords, but copying personal administrator credentials into an automation platform expands their use and makes attribution harder. Scanner execution may outlast the operator’s session and require different permission boundaries. The organization should keep interactive administration separate from dedicated service assessment, with narrowly assigned rights, accountable ownership, rotation, and audit logging for each scan identity.
Question 520
An ICU's cardiac telemetry monitor requires a manufacturer update to remove a management-interface vulnerability, but applying it now would interrupt essential patient monitoring. The bedside telemetry stream uses a different approved network port. A firewall currently allows guest-wireless clients to reach the vulnerable management interface. Which bounded interim control most directly reduces exposure while clinicians plan a safe update window?
- Increase password complexity on the monitor but leave the exposed pre-authentication management endpoint available to guest clients
- Deny the guest-to-management route, restrict maintenance access to named biomedical engineering stations, preserve bedside telemetry and document the clinical patch deferral
- Rate-limit guest traffic to the management port while preserving universal guest reachability for emergency convenience
- Disable every service on the monitor, including the required telemetry channel, before clinicians authorize an alternate monitoring method
Explanation
Correct Answer
B:The temporary control should remove the unnecessary guest route to the vulnerable management plane while keeping the separately defined clinical telemetry port available. Firewall policy can allow maintenance only from named biomedical engineering stations with approved authentication and logging. Clinicians should validate telemetry continuity, sign off the time-limited patch deferral, and schedule the manufacturer's update under a safe maintenance plan. This differs from applying a generic network zone or a virtual patch to all device traffic: the case identifies one unnecessary pre-authentication management path that can be closed immediately without stopping patient monitoring. Residual risk still exists on authorized paths, so observation and update scheduling remain necessary.
Incorrect Answers
A:Password complexity helps against guessed credentials but does not eliminate exposure to a flaw that can be reached before authentication. The relevant attack path is the management listener being available from an untrusted guest network. Keeping that route open merely with stronger account passwords does not address a vulnerable pre-login interface. Password policy may remain a supporting control after the network path is restricted, while the manufacturer update is scheduled according to patient-safety needs.
C:A rate limiter may slow repeated connection attempts or some denial-of-service behavior, but it still permits unauthorized clients to communicate with the vulnerable management service. A guest user could deliver a malicious packet within the allowed rate. Because bedside telemetry runs on a separate approved port, administrators can remove the unsafe management reachability without interrupting clinical monitoring. The correct interim action limits the callers and functions that can reach the vulnerable interface, rather than simply reducing their traffic volume.
D:Stopping every network service would remove the attack path, but the device is currently providing clinically required telemetry. Doing so without a validated substitute could directly affect patient safety, which the scenario explicitly rules out. A security control for medical equipment must be assessed with the clinical owner and biomedical engineering team. More selective firewall restrictions can block guest management access while preserving the separate monitoring stream until the manufacturer patch is safely implemented.