CompTIA Security+ SY0-701 Practice Test 51
Question 500
A regional legal firm detects ransomware after an attacker gained a powerful backup administrator account. The attacker attempted to delete restore points, but a separate immutable backup copy remains protected from ordinary administrative modification. Before reconnecting the case management service, how should the recovery lead use that copy?
- Mount the immutable vault as writable media for the recovery team so restoration can use the existing high-privilege backup workflow.
- Restore the newest point straight into production without checking whether it already contains malicious modifications
- Verify protected recovery-point integrity and restore known-clean data into an isolated environment before controlled production return
- Restore directly to production from the protected vault, using successful backup metadata as the sole integrity and malware check.
Explanation
Correct Answer
C:An immutable copy helps preserve recovery material when attackers attempt to modify or delete standard restore points. The recovery team should validate access controls and integrity, identify an uncompromised point, restore it into an isolated environment, scan for persistence and confirm case-management functionality before staged return to production. Use independent credentials, retain security logs and rotate compromised secrets. Immutability alone does not guarantee that the backed-up content was clean when captured, so both source integrity and recovered system state require examination. This approach preserves the strongest remaining trust boundary while avoiding reinfection or accidental destruction during an urgent restoration.
Incorrect Answers
A:A familiar privileged recovery workflow may simplify operational scripts, but turning an immutable copy into ordinary writable storage weakens the very boundary that protected it from the compromised administrator. The attacker attempted to delete recovery points, so key and access isolation are crucial. Restores should read validated protected copies through a controlled process, not grant broad modification rights to the protected vault. Recovery speed is secondary to preserving clean source evidence.
B:The newest point may include malicious persistence, tampered case files or encrypted data if created after compromise. Restoring directly into live production risks reintroducing the threat and confusing investigators. Verify candidate backup timing and integrity, then test recovery in a contained environment before reconnecting business users. Clean-room testing helps detect retained ransomware components before the restored service handles client files.
D:Protected backup metadata can establish that an archive exists and that its retention controls were respected. It cannot alone prove the captured system state predates ransomware persistence or compromised application changes. Direct production restoration may reintroduce malware or corrupt records if the recovery point is not validated. The team should inspect an appropriate known-clean point in isolation before reconnecting the case management service under controlled conditions.
Question 501
A nonprofit's file servers were encrypted by ransomware, including online snapshots synchronized to the same compromised storage account. A separately authenticated offsite repository has retained historical recovery points under an immutable retention rule. The incident commander asks what this design contributes to recovery, without assuming the archived copies are automatically clean. Which answer is best?
- It retains protected historical copies outside the attacked snapshot path, providing candidates for verified clean restoration
- Restore the newest immutable snapshot without malware or application-integrity checks because write protection prevents tampering
- Copy the immutable archive into the compromised production account before confirming the restore point is clean
- An immutable archive is sufficient even if the organization has never tested access to its required encryption keys
Explanation
Correct Answer
A:Isolated immutable copies resist ordinary attacker deletion or encryption and offer historical points that the compromised online snapshot path cannot provide. Select a candidate before known malicious changes, validate its integrity and contents, test dependent services and restore using protected identities. Isolation and immutability increase the chance that recovery material survived, but do not prove that every backup contains a clean version of the application. Periodic restore drills and tested key recovery are required to convert preserved copies into actual resilience. The design reduces ransomware blast radius while still demanding careful evidence-based restoration.
Incorrect Answers
B:Immutability can stop an attacker from deleting or changing a preserved recovery point, but it cannot guarantee that malicious content was absent at the moment the snapshot was created. The most recent copy may already contain ransomware payloads or corrupted data. Responders should select a suitable recovery point, verify application consistency and inspect the restored system in isolation. The copy is valuable because it survived the attack, not because immutability certifies its cleanliness.
C:Reconnecting preserved backups directly to an account still under attacker control can expose recovery data or enable reinfection during restoration. An immutable repository protects historical bytes under its own controls, but its contents must be examined in a trusted isolated environment before being used to rebuild production. The organization should also rotate compromised administrative access and verify recovery readiness. Importing the archive too early forfeits some isolation benefit without establishing that the saved state is safe.
D:Encrypted backups cannot be recovered if the required keys are lost, inaccessible or compromised. The nonprofit needs separation of key custody and tested break-glass procedures to use its offsite copies. A repository's immutable status does not substitute for verified ability to decrypt and restore critical records during an outage. Encrypted backups without recoverable keys may be unusable despite perfect retention settings.
Question 502
A commercial data center powers its servers through redundant UPS units, but its cooling plant has only one upstream electrical feeder. During planned switch maintenance, the cooling feed fails while servers remain electrically powered and temperatures begin rising rapidly. Which resilience defect does the test demonstrate?
- Increase the runtime capacity of the existing server UPS equipment while leaving the cooling plant on its single, unprotected upstream electrical feeder
- Web servers require longer UPS runtime for routine software patch installation, independent of cooling
- Only inter-site application replication bandwidth failed while cooling continued to receive normal power
- Critical cooling has a single electrical-feed dependency even though server UPS systems never lost power
Explanation
Correct Answer
D:The servers' redundant UPS arrangement kept compute powered, but the single cooling feeder failed and threatened the entire room through rising temperature. Availability requires resilient supporting services, including cooling power and control systems, not merely protected server outlets. The facility should design an alternate supply or redundant cooling path, test transfer behavior and consider safe automated load shedding before temperatures exceed operating limits. A partial power design can be deceptive: working servers still become unavailable when environmental dependencies fail. The essential finding is a common facility failure mode outside the server UPS boundary.
Incorrect Answers
A:Additional UPS runtime can improve availability for the compute racks, but the exercise proved those racks never lost their protected power in the first place. The single electrical feeder serving the cooling plant failed and temperatures rose despite functioning server UPS units. Increasing server-side battery capacity does not create a redundant feed or generator transfer for the critical cooling equipment, so it leaves the demonstrated common-mode vulnerability unresolved.
B:Patch windows may require server availability, but nothing in the exercise shows a software upgrade exhausting UPS runtime. Cooling loss happened because the plant's only feeder failed. Extra server battery time might buy minutes, but it would not independently restore heat removal. The rising room temperature is an environmental dependency, not a failure of application update duration.
C:Replication bandwidth affects remote data synchronization, whereas temperature climbed because cooling machinery lost electricity. The scenario does not report an inter-data-center link fault. Investigators should follow the electrical and environmental dependency chain rather than attribute the event to application traffic. A link failure would not explain why powered servers are overheating immediately after the cooling supply stops.
Question 503
A healthcare portal has three recovery tiers: directory identity service, patient database and web front end. A drill restores web containers first, but staff cannot log in or retrieve records because neither identity nor database components are ready. The organization wants to fix its disaster runbook rather than merely start servers more quickly. What change is most useful?
- Continue restoring the web front end first and rely on repeated retry requests until downstream systems happen to recover
- Start identity and database restores without sequencing or checking whether one depends on the other
- Document and rehearse prerequisite-aware recovery order so identity and database services are available before web activation
- Recover the database first and activate the web tier immediately afterward, leaving the identity prerequisite unavailable
Explanation
Correct Answer
C:A recovery runbook must represent dependency order, readiness criteria, ownership and validation steps for the whole service. Restoring identity and database prerequisites first allows the web tier to authenticate users and retrieve records when it becomes available. Teams should test the sequence during realistic drills, including health checks, secrets access, network routes and failover triggers. Actual restoration success means the portal performs business functions within its RTO, not that one container responds to a health probe. Well-designed sequencing can coexist with safe parallel steps, but cannot ignore prerequisites exposed by the failed exercise.
Incorrect Answers
A:A web server can be healthy at the host level while its business workflows remain unusable without sign-in and data. Repeated retries do not remove missing dependencies; they may instead add load when services restart. The runbook should reflect complete application function, not only the speed of its most visible tier.
B:Parallelism can reduce recovery time when dependencies permit it, but uncoordinated startup can cause failed migrations, authentication errors or repeated application crashes. The team should identify which identity and database components must be ready before dependents initiate operations. Some tasks may run in parallel after those constraints are understood. Identity readiness might itself depend on database or network services, so ordering must follow tested prerequisites.
D:Restoring the data tier early can be appropriate because the portal cannot display patient records without it. But the scenario also states that staff cannot sign in while identity services remain unavailable. Starting the web containers as soon as the database is online would recreate a partly unusable portal. The runbook should explicitly validate both identity and data prerequisites before declaring the front end ready.
Question 504
A streaming subscription service switches its DNS alias to a healthy secondary region after detecting a primary outage in ninety seconds. Some users still connect to the failed region for nearly an hour because their resolvers cached the previous address with a 3,600-second TTL. What constraint should the recovery plan acknowledge?
- Lower the authoritative TTL immediately after the outage begins and assume all cached 3,600-second records will honor the new setting.
- DNS record caches can delay client movement until stored responses expire, even after rapid authoritative cutover
- Require every browser to bypass its local DNS cache, but assume upstream recursive resolvers cannot retain the old address.
- Improve failure detection from ninety seconds to ten seconds and assume that alone guarantees all clients switch regions within ten seconds.
Explanation
Correct Answer
B:A 3,600-second TTL permits many recursive or client caches to retain the old region's address for about an hour, subject to resolver behavior. Detecting an outage in ninety seconds therefore does not guarantee every client switches that quickly. Recovery architecture should choose appropriate TTLs in advance, consider health-aware global routing and test client behavior during failover. Lower TTLs can help but are not a guarantee because some clients and intermediaries cache differently. The practical issue is end-user recovery time across the DNS ecosystem, not only authoritative record update speed.
Incorrect Answers
A:Reducing TTL before a planned migration can limit how long fresh DNS answers remain cached. It generally cannot retroactively shorten a valid answer already stored by recursive resolvers under the earlier 3,600-second TTL. Changing authoritative records after an outage therefore may not move every client promptly. The recovery plan needs to anticipate stale caches, preplanned low TTLs where appropriate, and other routing or health techniques rather than assuming instant propagation.
C:Flushing a browser or operating-system cache may help some clients obtain a new answer, but their recursive DNS resolver can still serve the previously cached address until its TTL expires. The described hour-long behavior arises from resolver caching, not necessarily local browser state. Operators should account for multiple cache layers and cannot assume one client-side action clears the whole path. The recovery objective must reflect this distributed DNS behavior.
D:Faster health monitoring can initiate the DNS cutover sooner, which reduces one part of recovery delay. It does not invalidate DNS responses already cached at recursive resolvers or client devices. A resolver holding the prior destination can continue returning it despite the authoritative change. The recovery plan must model detection latency separately from address-cache expiration and connection behavior instead of treating the first alarm time as end-to-end recovery time.
Question 505
A private employee phone is enrolled for calendar access but its compliance agent reports device encryption disabled. Corporate BYOD policy requires encryption before any protected work data can be stored locally. The employee has a meeting in fifteen minutes and asks for a temporary exception. Which management response best respects the stated security condition?
- Permit calendar export into personal storage because a work container icon appears on the device
- Put the phone in an MFA bypass group so the calendar can sync before encryption is reenabled
- Withhold protected work data until encryption compliance is restored and apply the approved BYOD access policy
- Enforce only app-level MFA while ignoring the required at-rest encryption setting indefinitely
Explanation
Correct Answer
C:The device does not satisfy the organization's mandatory encryption rule, so conditional access or mobile management should block protected synchronization until compliance is restored. Explain the required device setting, offer a compliant alternate way to attend the meeting if available and document any formal, narrowly approved exception process rather than bypassing controls informally. Once verified encryption is enabled, access can resume under normal identity policy. MFA and application containers remain useful but do not compensate automatically for an unmet at-rest requirement. The decision follows the explicit BYOD condition rather than the urgency of one calendar event.
Incorrect Answers
A:A visual container indicator or managed application can help separate work and personal data, but it does not prove the device meets an explicit encryption requirement. Exporting calendar content into personal storage may worsen exposure. The policy calls for a measured device posture, not a cosmetic management label. The explicit encryption prerequisite applies whenever protected corporate information is stored on the device.
B:MFA protects login integrity, while local device encryption protects stored work data if the phone is lost or compromised. Exempting the phone from MFA would remove an unrelated safeguard and still leave encryption disabled. A convenience exception should not be invented outside the established BYOD governance process. Removing MFA could also weaken the sign-in path while doing nothing to secure offline data.
D:MFA can reduce account takeover but cannot encrypt calendar data already stored on an unprotected phone. The scenario's principal gap is device-at-rest protection. Ignoring that mandatory standard because an app prompts for MFA would treat two different controls as interchangeable. A lost phone could expose plaintext work calendar contents even after authentication safeguards blocked account reuse.
Question 506
A container admission controller validates signed images from the company's trusted build pipeline. Two days after deployment, runtime telemetry detects an unusual shell process and outbound connection inside a container whose image signature remains valid. What distinction should the security engineer explain to operations?
- A valid image signature guarantees all later behavior of the running container is authorized
- Runtime sensors make signature verification at deployment unnecessary because they can detect suspicious commands afterward
- Continuously re-signing the unchanged image removes malicious processes that appear after deployment
- Image signing attests trusted build provenance at admission; runtime monitoring evaluates subsequent execution and compromise
Explanation
Correct Answer
D:Image signatures and admission policies verify selected provenance and integrity properties of the container artifact before it starts. Runtime telemetry then observes processes, system calls, network behavior and changes that can occur after launch. A container can have a legitimate signed image and still become compromised through an exploitable application or stolen credential. The team should correlate the unusual process with parent execution, deployment events and outbound destinations, contain the affected pod as needed and preserve evidence. The proper answer retains both prevention at supply-chain entry and detective monitoring of actual workloads, rather than equating one with a guarantee of the other.
Incorrect Answers
A:A signature can show that a trusted key signed an image digest, but the running workload may later process malicious input, have a vulnerable dependency or execute unauthorized commands. It does not supply ongoing behavioral authorization. The suspicious shell still needs investigation despite valid image provenance. The new shell process might have been launched through a vulnerable endpoint after the signed image started.
B:Runtime monitoring is valuable after execution begins, but stopping untrusted images before admission prevents some supply-chain risks that detection alone might miss. The two controls work at different stages. Disabling signature enforcement would allow additional unauthorized artifacts into the cluster without resolving the observed runtime anomaly. Admission integrity should remain enforced while the runtime alert is investigated through workload telemetry.
C:Re-signing the same artifact proves the signer's approval of unchanged bytes; it does not remove a process launched during execution. An attacker may abuse application functions, injected commands or runtime credentials without changing the original image. Investigators must inspect live process activity and containment controls. The security team should inspect the live child process and its network destination, not repeatedly sign static bytes.
Question 507
A workstation indexing tool reads a department's approved shared directory and sends health status to one internal server. It runs continually as local Administrator on every employee laptop, although its vendor documentation confirms the required functions work under a restricted service identity. Which configuration change most directly limits compromise impact?
- Run it as a dedicated low-privilege account limited to the needed directory and status endpoint
- Move the indexing tool to a dedicated service account but retain local Administrator rights on every employee laptop.
- Permit only the vendor-signed indexing executable through application control while continuing to run it with full local administrative privileges.
- Run the indexing tool under a named service identity that can modify every user profile, not merely read the approved share.
Explanation
Correct Answer
A:Least privilege constrains the indexing tool to read only its designated files and reach its approved status destination. A dedicated service identity makes actions traceable and limits what an exploited application or malicious update could change. Validate required file permissions and update paths before removing local admin rights, and monitor for regression after rollout. The application's legitimate business purpose does not justify unlimited endpoint access. This is a direct reduction of the impact of process compromise rather than reliance on its current reputation or frequency of updates. Restricting local file permissions also reduces access to other employees' documents if the indexing process is hijacked.
Incorrect Answers
B:Creating a distinct service identity improves audit attribution and makes credential lifecycle management easier. It does not remove the unnecessary local Administrator permissions that enlarge the attack impact if the indexing process is compromised. The vendor has confirmed that restricted access is sufficient for reading the shared directory and reporting status. The service account’s actual rights must be reduced, not merely renamed.
C:Application control helps block unapproved executables and can verify a publisher or hash before launch. It does not make a signed application free of exploitable flaws, and malicious input could still cause the permitted process to act with its excessive privilege. The stated risk is that a routine indexing tool runs as local Administrator on every laptop. Execution allowlisting complements, but cannot replace, reducing the process permissions.
D:A named identity can support credential rotation and accountability, but it still needs permissions limited to the service’s functions. Giving it write access to all local profiles would permit unnecessary alteration of user data or settings if exploited. The indexing program only needs to read an approved directory and send status to one internal server. Those specific capabilities should define the account’s scope rather than a broad write grant.
Question 508
A government workstation is suspected of early-boot firmware tampering. The security team requires proof that approved firmware and boot loaders started before a disk-unlocking secret becomes available to the operating system. Which combination most appropriately supports trusted startup and conditional key release?
- Check only the user's password after startup, while permitting any unsigned firmware image to execute
- Use UEFI Secure Boot with measured boot and a validated platform-trust decision before releasing sensitive keys
- Depend solely on application allowlisting configured after the employee has logged in
- Release a full-disk key at power-on without examining boot measurements because encryption is enabled
Explanation
Correct Answer
B:Secure Boot can enforce an approved chain of signed boot components, while measured boot records relevant startup measurements into a trust mechanism such as a TPM. A policy can evaluate those measurements before authorizing release of sensitive key material, within the capabilities of the platform and management system. The organization should maintain trusted firmware, revocation updates and recovery workflows so legitimate upgrades do not silently bypass policy. Measurements provide evidence about startup state, not proof that every later application is safe. This combination addresses the exact period before disk secrets become available and provides a clearer basis for incident response to suspected firmware tampering.
Incorrect Answers
A:A password prompt occurs after low-level firmware and boot code have already executed. If the early boot chain is compromised, user login alone cannot establish its trustworthiness. The team specifically needs a verified sequence from boot components, not only an account credential check once the OS is running. Trust decisions about firmware must occur before untrusted code can intercept or manipulate the boot sequence.
C:Application allowlisting can constrain programs launched after the OS is operating, but it does not establish which firmware and boot loaders already ran. A malicious early component might influence the environment before allowlisting initializes. It remains a valuable later-stage control, not the requested root-of-boot trust mechanism. The workstation may already have exposed the disk key before post-login application rules become active.
D:Full-disk encryption protects stored data when decryption keys are withheld, but unconditional key release before validating startup state undermines protection against some early-boot tampering. The security goal is to bind unlock policy to trusted measurements or authorization, not simply enable encryption and expose the key regardless of boot integrity. Key release should be contingent on validated platform state if resistance to early tampering is required.
Question 509
A field-technician VPN concentrator enforces modern MFA but still runs obsolete management and file-transfer listeners on the same public interface. Traffic baselines show no legitimate use of those listeners, yet the operations team worries that an indiscriminate shutdown might interrupt required identity-provider callbacks. Which hardening implementation best reduces the exposure while safely preserving the supported VPN service?
- Keep the unsupported listeners exposed and rely on an intrusion-detection alert whenever a public client connects
- Map service dependencies, disable the unused listeners through an approved change, verify VPN and MFA functions, and retain rollback evidence
- Move the obsolete management listener to an unusual TCP port but leave it reachable by arbitrary Internet clients
- Remove every listener including the supported VPN service, then recover remote access only after users report outages
Explanation
Correct Answer
B:Least-functionality hardening should eliminate the obsolete listeners without inadvertently disabling the supported VPN and MFA integrations. The team should document which processes and ports are truly unused, examine identity-provider callbacks and operational dependencies, test the intended configuration, obtain the normal change authorization, and disable or uninstall the unnecessary components. A rollback plan and post-change connection tests establish that technicians can still authenticate and reach approved destinations. The critical decision here is not simply identifying unused services; it is executing a dependency-aware change on a high-availability remote-access system. Network exposure, authentication and management should be verified after the change, with continued monitoring for unexpected public listeners.
Incorrect Answers
A:Intrusion detection can identify scanning or misuse and is useful while the change is planned, but it does not remove the unnecessary Internet-facing code paths. An end-of-support file-transfer daemon remains available for pre-authentication bugs even when its connection events are logged. Since the traffic baseline indicates the services are unused, preserving them indefinitely for alerting alone leaves avoidable exposure. The safer workflow is to verify dependencies, remove unsupported listeners, and retain focused monitoring on the required VPN functions.
C:Port obscurity may reduce noise from unsophisticated automated scans, but it does not reduce the number of vulnerable services or establish user authorization. An Internet attacker can discover an open service regardless of whether it uses the conventional port. The administrator also risks losing operational visibility if monitoring expects the standard number. Restricting management to a controlled administrative path, or removing it if unnecessary, addresses the attack surface more directly than moving a vulnerable process to a different address or port.
D:Shutting down the functioning VPN service would indeed remove network reachability, but it would also prevent field technicians from performing their authorized duties and could hinder response during an incident. The question explicitly requires preserving current MFA and VPN access. A blanket shutdown is not a tested least-functionality change; it ignores the difference between supported required functions and obsolete unused ones. Maintenance should be scoped and validated so unnecessary components are disabled while essential identity integrations still function as expected.
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.