CompTIA Security+ SY0-701 Practice Test 56
Question 550
A managed security team automates daily account reviews across ten customer cloud tenants. A developer discovers administrator credentials for every tenant stored in the script repository. The team wants scheduled jobs to keep functioning while preventing one tenant's breach from exposing all others. Which credential architecture should replace the current approach?
- Move the ten administrator passwords into one encrypted file that every tenant's service can decrypt
- Deploy one shared cloud service principal for all ten customers, granting it the minimum read rights needed in each tenant
- Leave passwords in the repository but rotate them yearly and rely on repository access controls
- Use a centrally governed secret service and separate narrowly scoped workload identities for each tenant
Explanation
Correct Answer
D:Separate per-tenant workload identities prevent a job for one customer from automatically gaining permissions across the other nine. A protected secret manager can handle exceptional credentials, access policy, rotation, auditing and retrieval only at runtime; ideally cloud federation avoids static passwords altogether. Grant each automation only the account-review actions it needs, with tenant-specific trust relationships and short-lived tokens. This design contains compromise and makes access revocation and investigation tractable. Central management does not imply a single global administrator credential: segmentation of identity and permissions is essential to preventing cross-tenant blast radius.
Incorrect Answers
A:Encryption at rest is valuable but does not solve shared, broad credential retrieval: if all scripts can decrypt the file, a compromise of one workload may expose all ten tenant accounts. The design should also minimize what each job can access and how long a stolen credential stays useful. Central protection without per-tenant isolation is an incomplete improvement.
B:Reducing administrative rights is useful, but using one principal across independent customer tenants creates a common identity and trust dependency. If its credential or token is compromised in one workflow, the attacker may gain access to the other tenants where that principal is trusted. The design needs separate customer-scoped workload identities and centrally governed secret custody, not merely one broadly reusable identity with reduced role names.
C:Source control access restrictions lower casual exposure but cannot safely govern powerful secrets embedded in commits and copied into builds. Historical versions may preserve older credentials, and annual rotation leaves a long exposure period. The organization should remove them from source history where practical, replace them and move to scoped runtime credentials.
Question 551
An incident-response orchestration service receives a low-confidence malware alert on the virtual machine hosting an emergency department's patient records. Its draft playbook would immediately delete the VM to prevent further infection. The clinical team cannot restore the workload from a fresh backup in minutes. How should this high-impact playbook be governed?
- Disconnect the VM's only network interface immediately without assessing whether it supports bedside data entry
- Authorize deletion automatically after a five-minute timer when no analyst explicitly rejects the request
- Grant the SOAR service temporary administrator rights during incidents and permit it to delete the VM without further review
- Require a qualified human decision with clinical-impact evaluation before performing destructive deletion
Explanation
Correct Answer
D:Automated playbooks should separate reversible low-impact tasks from destructive changes affecting safety-critical workloads. Collect evidence and, if justified, propose targeted containment while alerting the incident commander and clinical operations. Require a named authorized reviewer to consider confidence, clinical dependencies, recovery capability and alternatives before authorizing VM deletion. Record the rationale and approval in the incident trail. This human-in-the-loop gate does not prohibit useful automation: enrichment, host investigation and non-disruptive protective actions may continue. It prevents one ambiguous alert from triggering a permanent outage that may harm patients more than the suspected threat.
Incorrect Answers
A:Network isolation can be appropriate for confirmed malicious activity, but the stem identifies patient-care dependencies and low-confidence evidence. An unconditional disconnect could impair urgent treatment or records access. The team should coordinate containment choices with clinical safety stakeholders and verify that essential workflows remain available, rather than treating isolation as automatically safe.
B:A short automatic-approval timeout does not constitute meaningful human authorization, particularly during an emergency when the on-call analyst may be unavailable. Deletion has severe and possibly irreversible consequences. High-risk actions require explicit informed review, while lower-risk evidence gathering or rate limiting can still be automated for response speed. Silence after five minutes could reflect staffing or network delay rather than informed consent to erase evidence.
C:Temporary privileges reduce the lifetime of automation access but do not correct a dangerous decision rule. A powerful credential still enables immediate destructive action on incorrect evidence. Privilege scoping, approval gates and documented exceptions are distinct safeguards; the orchestration system must limit both what it can do and when it may do it.
Question 552
A fleet-response service calls an endpoint isolation API for 200 laptops after confirmed credential abuse. The API returns 170 successes and 30 network timeouts. Some timed-out requests might actually have completed at the endpoint. The incident commander needs an accurate containment picture without imposing disruptive duplicate operations. What should orchestration do next?
- Mark all 200 laptops as contained because most API calls reported success
- Mark every timeout as a confirmed failure and stop checking those endpoints
- Blindly resend all 200 requests without verifying resulting endpoint states or retry safety
- Query each uncertain endpoint, reconcile completed isolation, retry safely and escalate unresolved devices
Explanation
Correct Answer
D:Treat partial success as a set of separate confirmed, failed and unknown endpoint outcomes. Query device posture or the isolation API to determine which timeouts already completed, then retry only unresolved operations using idempotency keys or supported safe replay behavior. Escalate devices that remain unconfirmed and keep incident records aligned with each target's actual state. This prevents false assurance while avoiding unnecessary repeated disruptions to devices already quarantined. The orchestrator should preserve request identifiers, response codes and timestamps to support both operational handoff and later investigation of the remaining footholds.
Incorrect Answers
A:A majority success rate cannot prove containment of the remaining 30 laptops. An attacker needs only one uncontained endpoint to retain a foothold. Incident reporting must distinguish confirmed isolation from unknown or failed outcomes, with ownership for each unresolved target rather than declaring a fleet-wide success. The unconfirmed devices must remain individually visible in the containment dashboard until their actual status is checked.
B:A timeout means the orchestrator did not receive a conclusive response; it is not proof the endpoint rejected the request. Some isolation operations might have executed before the acknowledgment was lost. Investigators should inspect authoritative endpoint state, retry where necessary and maintain evidence of what remains uncertain. A discarded timeout also prevents reconciliation of possible isolation that completed despite transport or API response failure.
C:Mass reruns may be acceptable for a verified idempotent API, but the stem does not guarantee the operation is safe or necessary for all 200 devices. Blind retries obscure the original outcome and can overload services or repeat disruptive actions. Reconciliation should identify only unresolved targets and apply retry rules based on the API's semantics.
Question 553
A research administrator is suspected of copying proprietary laboratory designs onto personal storage. The administrator's assigned laptop is still powered on, but the service desk has a request to reimage it for reuse tomorrow. Corporate counsel authorizes an investigation and requires defensible evidence. What should the incident team do before the scheduled reimage?
- Copy only the user's Documents folder to an open shared drive and rely on file names as proof of integrity
- Export browser history without custody records, then allow the service desk to erase the original device
- Secure the laptop, preserve relevant evidence with integrity hashes and custody records, and defer destructive reimaging
- Return the laptop to its user while management decides whether forensic collection is worth the effort
Explanation
Correct Answer
C:Authorized responders should prevent further tampering, document device state and acquisition scope, collect relevant volatile and persistent evidence when justified, and hash images or exports to demonstrate later integrity. Record who handled the laptop, when transfers occurred and where the evidence was secured. Defer reimaging until the investigative and legal preservation requirements have been met. Chain of custody does not by itself prove the employee committed wrongdoing, but it makes the collection process defensible and helps distinguish original artifacts from subsequent handling. Coordinate with counsel on privacy and scope rather than indiscriminately copying unrelated personal data.
Incorrect Answers
A:A user-folder copy can miss deleted files, external-device artifacts, application caches and system events that establish whether exfiltration occurred. A shared drive may also permit unauthorized modifications and access. Defensible preservation requires appropriately scoped acquisition and a trustworthy custody trail, not merely a convenient archive of visible files. For example, a browser artifact outside Documents could identify the destination of the suspected sensitive-file transfer.
B:Browser data may be useful but represents one subset of possible activity, and custody records are necessary to show who collected and handled evidence. Wiping the source before approved forensic acquisition destroys potentially irreplaceable artifacts. The service desk's operational task must be paused until authorized investigators document and preserve what the case requires.
D:Returning a suspected evidence device to ordinary use creates opportunities for evidence deletion, additional changes or further data loss. The investigation has already been authorized and a destructive maintenance action is pending. Preserve the relevant device under controlled custody while counsel and incident response coordinate; do not allow routine workflow to erase or alter it.
Question 554
A hospital SOC labels a suspected compromised executive account as a high-severity incident because the identity can approve sensitive changes. The privacy office is still determining whether any protected patient information was actually accessed. A communications manager proposes issuing a mandatory breach notification solely because the SOC used the label 'high.' Which statement is correct?
- A SOC high-severity label automatically proves that regulatory notification conditions have been met
- Any privacy-office consultation means personal information was exposed, regardless of the evidence
- Operational incident severity and statutory breach-notification analysis are distinct decisions using different criteria
- The SOC must downgrade the event until the privacy team proves reportable access to records
Explanation
Correct Answer
C:Incident classification prioritizes technical work based on potential or observed harm, whereas breach-notification obligations depend on applicable law, affected data, evidence of unauthorized acquisition or access and prescribed assessment procedures. A high-risk credential incident warrants urgent containment even before data exposure is established. Privacy counsel and responsible officers should make the legal decision from the facts and record their reasoning and any deadlines. The two workflows should share evidence and communicate, but neither must wait for the other's final label. This separation avoids both underreacting technically and making unsupported assertions about reportable data compromise.
Incorrect Answers
A:Operational severity may reflect potential business impact, attacker capability or urgency, not a verified compromise of legally protected information. Notification laws may impose specific definitions, risk factors and timelines. Treating one internal severity label as automatic proof can lead to inaccurate external statements and premature conclusions about what data were involved.
B:Involving the privacy team is appropriate precisely because exposure and notification obligations are uncertain. Consultation does not establish that an unauthorized disclosure occurred. Investigators need the records accessed, identities involved, containment facts and applicable legal thresholds before making that determination; the event can remain severe for operational response independently. The privacy team may determine that only an attempted, unsuccessful access occurred and no notification trigger was met.
D:Downgrading the incident merely because protected-data access is unconfirmed would suppress response urgency despite an executive account's potential impact. Severity can legitimately reflect privilege level and the ability to cause future harm. The legal assessment should proceed separately, and incident severity can be updated when new evidence changes the technical risk picture.
Question 555
A ransomware attack disables shared infrastructure used by three subsidiaries. One local IT team wants to power off core routers, another wants to rebuild servers first, and customer service staff from each subsidiary are drafting different public statements. No one is authorized to settle cross-company impacts. Which incident-response organizational action should occur immediately?
- Allow each subsidiary’s local incident lead to authorize core network shutdowns without a common commander or cross-company impact review
- Exclude legal and business leaders until the technical team fully finishes forensic analysis
- Designate an incident commander with clear decision rights and coordinated technical, business and legal leads
- Require each subsidiary to publish its own incident verdict before any common containment decision
Explanation
Correct Answer
C:A named incident commander establishes an authoritative decision structure for shared dependencies, while functional leads supply technical facts, patient or customer impact, legal obligations and communications plans. Define who approves disruptive containment, how subsidiaries escalate conflicting needs and which spokesperson gives verified updates. This does not require every technical action to wait for a board meeting; delegated authority and predefined procedures support prompt choices. A common incident log and decision rationale help later reconstruction. Without coordination, otherwise reasonable local responses can damage shared infrastructure or create inconsistent public statements, worsening the incident across business boundaries.
Incorrect Answers
A:Local incident leads can make timely decisions within delegated scope, and their site knowledge is valuable during a ransomware incident. However, the shared infrastructure connects three subsidiaries, so an uncoordinated core-router shutdown could hamper recovery or affect other businesses unexpectedly. A formally designated incident commander must coordinate authority, legal and customer communications, containment dependencies and emergency escalations across the affected organizations.
B:Technical containment can have contractual, customer, privacy and operational consequences that require involvement from accountable business and legal representatives while events are unfolding. Waiting until forensics ends can cause missed deadlines or unsafe service decisions. Specialist teams should coordinate under an incident leader rather than operating in separate sequential silos.
D:Separate uncoordinated public statements may expose unverified facts and create contradictory obligations while containment is still ongoing. A declaration by each subsidiary does not establish who may isolate shared networks or authorize restoration. The immediate gap is command authority and coordinated information flow; regulatory notification can be handled through assigned legal and communications leads.
Question 556
A security appliance detects malware callbacks from a hospital department's scheduling workstation. The department shares switches and service paths with cardiac telemetry and medication dispensing systems. An analyst suggests disconnecting the entire building immediately, though the medical team has not evaluated the effect on patient monitoring. What containment plan is most appropriate?
- Turn off the shared network core without consulting clinical operations because preventing propagation always dominates availability
- Keep all network paths open and merely increase log collection until the malware stops communicating
- Quarantine every device in the department without first identifying critical clinical relay equipment
- Coordinate targeted containment with medical safety owners, preserving indispensable patient-care dependencies
Explanation
Correct Answer
D:Patient safety and cyber containment must be managed together. Identify the compromised workstation and command-and-control route, consult clinical engineering and medical leadership, then isolate or block the smallest effective set of hosts and traffic while preserving critical telemetry and dispensing links. Use approved downtime procedures and manual alternatives when necessary, and monitor for lateral movement. Document the risks, authority and evidence supporting the decision. Targeted action may need to expand if the threat spreads, but a broad immediate shutdown without dependency assessment is not automatically safer. The correct approach controls malicious activity without ignoring life-critical operational constraints.
Incorrect Answers
A:An indiscriminate shutdown could interrupt telemetry and medication services whose availability is safety critical. The apparent reduction in cyber exposure may create immediate clinical harm. Before changing shared infrastructure, responders need the topology, dependency inventory and contingency procedures, along with clinical decision makers who understand treatment impact. In this hospital, stopping shared routing might simultaneously block urgent radiology and bedside medication-verification traffic.
B:Passive monitoring alone leaves known malicious communication active and permits the infection to spread or continue exfiltrating. In many cases immediate limited containment is warranted, but it must be tailored to the affected endpoints and essential service paths. More logs can support investigation yet cannot replace action against a verified active threat.
C:Department membership does not identify whether a device is a direct malware host, a clinical relay or an essential gateway for unaffected care. Quarantining everything can interrupt monitoring and may be unnecessary. Scope and dependencies should be verified before applying isolation, with alternatives such as narrow blocking rules or segmented paths where feasible.
Question 557
During an authorized investigation into an active remote-control session on a Windows engineering workstation, responders observe a live network connection and suspect the attacker placed temporary encryption material in memory. The device is still running, and a standard disk image is planned. Which collection sequence best protects the evidence likely to disappear on power loss?
- Shut off power immediately and assume the later disk image will recreate every live session and RAM key
- Acquire only a standard disk image first and postpone volatile evidence collection until the workstation has been powered off
- Document the live system and acquire relevant volatile memory and connection evidence before orderly shutdown
- Clear page files and local event logs to reduce the size of the eventual forensic image
Explanation
Correct Answer
C:Following approved live-response procedures, record system time, logged-in users, processes and active connections, then collect memory or other volatile artifacts needed to understand the remote session. Use trusted tools, document their effect on the system, preserve integrity where feasible and maintain custody records. Only then shut down or isolate according to the incident's containment plan and image persistent storage. Volatile-first is not an absolute rule overriding immediate safety: responders may isolate rapidly if the active attacker poses unacceptable risk. Here the stated evidentiary objective specifically requires preserving memory-resident state before it disappears.
Incorrect Answers
A:RAM contents and active network sessions may vanish or change when power is removed, so a later disk image cannot reliably recreate them. Immediate shutdown may still be necessary to stop severe harm, but the question states that investigators are authorized and specifically need volatile evidence. Acquisition order should reflect that evidentiary volatility rather than treating persistent storage as comprehensive.
B:A forensic disk image can preserve persistent files, logs and configuration when it is acquired correctly. Yet the question highlights an active remote-control session and possible encryption material residing only in RAM. That volatile state may disappear when power is removed. Capturing memory and current connection data under documented authority before shutdown is therefore more probative than collecting only persistent storage and expecting the image to reconstruct lost sessions.
D:Deleting page files and event logs destroys or alters potential evidence of process execution, authentication and attacker activity. It makes the collection easier to store at the cost of investigatory value and may violate legal preservation instructions. Instead retain those artifacts and document any unavoidable changes introduced by live collection.
Question 558
A malware-infected laptop connects to a suspicious domain whose DNS records rotate among multiple cloud addresses each hour. Investigators have timestamps from the device's proxy browsing records and historical DNS query responses. A simple match to the domain's current IP misses several sessions. Which correlation method best reconstructs the contacted service?
- Treat a high number of DNS lookups as proof of successful data transfer to every resolved address
- Compare all old proxy connections against only the domain's address returned in the present hour
- Join time-matched DNS response history, proxy URLs and host identity to the recorded connections
- Discard the DNS response timeline and rely on the latest firewall destination to identify every earlier session
Explanation
Correct Answer
C:Historical DNS answers provide the address-to-name mapping as observed at relevant times. Combine the querying host, response timestamp and returned IPs with proxy URLs, session timing and destination records to reconstruct which hostname the infected laptop attempted to use. Account for DNS caching, proxy resolution behavior and clock synchronization before drawing firm conclusions. A successful name-to-IP match may establish contact but not by itself prove data theft; bytes transferred, method and application evidence are still needed. This approach preserves temporal context rather than assuming rotating infrastructure has a single permanent address.
Incorrect Answers
A:DNS lookup frequency can support a suspicion but cannot prove a subsequent connection or the movement of data. Some queries are cached, blocked or unrelated to observed application requests. Analysts should correlate actual proxy and network records rather than treating name resolution alone as evidence of successful exfiltration. A name lookup alone cannot show that the requester downloaded content or transmitted the proprietary files under investigation.
B:A fast-changing domain can resolve to different addresses at different times and locations. Today's answer is not authoritative evidence of what a given laptop saw earlier. Comparing only current DNS records can create false negatives or misattribute historical connections, particularly when content delivery and geographic routing are involved. Preserved historical response values give stronger temporal attribution than a new resolver query after the incident.
D:A current firewall record cannot reconstruct earlier domain resolutions when the addresses changed. Ignoring historical responses sacrifices the evidence that connects particular sessions to a domain at the time of activity. The investigation needs a timestamp-aware join across log sources, not a timeless IP label applied to every packet. Matching session timestamps to the earlier answers avoids assigning the wrong hostname to a reused cloud address.
Question 559
A Linux server's monitoring agent reports a root-owned interactive shell that appeared during a period of suspicious SSH activity. The process is gone, but audit records include parent process IDs, sudo events and session identifiers; the authentication service retains successful and failed logins. Investigators need to identify which logged-in principal launched the shell. What is the strongest evidence strategy?
- Assign the shell to whoever logged in most recently before the alert without linking the session to the process
- Use the user's shell history alone as proof of the authenticated person who started the privileged process
- Correlate process parentage, sudo or execution audit events and authentication session identifiers
- Reboot the server and identify the historical initiator from the processes that start afterward
Explanation
Correct Answer
C:Trace the privileged shell's process ID and parent chain to its invoking program, then correlate execution or sudo events with audit session IDs and the successful SSH login records. Check timestamps, identities and terminal or connection information for consistency. This can connect the root-level process to the original authenticated user even when privileges changed after login. Audit gaps or shared credentials can still limit certainty, so record the evidence and competing possibilities rather than inferring identity solely from root ownership. The decisive element is a linked session-to-process chain across independent logs.
Incorrect Answers
A:The latest login may be unrelated to the shell, particularly on a shared server with concurrent sessions and automation jobs. Temporal proximity is a lead, not a reliable linkage. Parent process and session identifiers can distinguish a privileged shell spawned by one session from another user's unrelated login. On the shared host, an unrelated scheduled automation job may also have spawned its own concurrent privileged process.
B:Shell history may be disabled, incomplete or manipulated, and commands can be executed outside an interactive shell. It does not establish which authenticated principal owned the process at creation time. Audit and authentication records provide more direct attribution when their session and process relationships are preserved. Noninteractive sudo invocations and erased history entries make this single artifact especially weak for attribution.
D:After reboot the suspected session and its transient process tree are gone. New processes may share numeric IDs without having any causal connection to the earlier shell. Rebooting before preservation can also destroy valuable volatile evidence. Investigators should use the retained historical logs and captured process lineage instead of inferring old activity from a new boot.
Question 560
A cloud storage bucket was accessed during an overnight incident. Administrative audit records show that its policy changed, but those records do not identify individual object reads. The storage service separately retained object-level access events for the relevant period, and investigators have not yet obtained them. Leadership asks which customer documents were downloaded, by which principal and when. Which evidence should the team collect and correlate?
- Treat the bucket's policy-change event as conclusive proof that every stored file was retrieved
- Use only aggregate network-flow volume to infer the exact object names accessed by each requester
- Collect object-level data-plane read logs and correlate them with control-plane policy and identity events
- Compare the bucket's item count before and after the incident and interpret unchanged count as no exfiltration
Explanation
Correct Answer
C:Control-plane auditing captures actions such as changing a bucket policy or configuring permissions. Object-level data-plane logs record reads against individual storage objects, including request time, principal and relevant object identifiers when enabled. Correlate both with identity, access-key and network context to build the event sequence and determine which files were accessed after the policy change. Verify that object-read logging was actually enabled during the relevant period; enabling it afterward cannot recreate missing events. Together these sources distinguish access configuration from observed use, supporting defensible scope estimates rather than assuming every object was downloaded merely because a policy was altered.
Incorrect Answers
A:An administrative event shows that a setting or policy changed, not whether any particular object was subsequently read. A change could enable access without being used, or a read could occur under an existing permission. Establishing actual downloads requires request-level evidence tied to individual object keys. Investigators also need principal identity and request time for the suspicious patient-report object keys.
B:Network-flow records can indicate connections and transfer volumes but generally do not identify specific cloud object names within encrypted API operations. Many requests may share the same service endpoint. Flow data can corroborate data movement, yet object-level access events are needed to establish which files a principal actually retrieved. Encrypted object requests can transfer multiple different files over one connection, defeating inference from volume alone.
D:Downloading an object usually does not remove it, so the inventory count can remain identical even after complete exfiltration. Counts help detect deletion or creation, not object-read activity. Without read-level logging and any available supporting access records, analysts cannot conclude that unchanged stored items mean no sensitive data left the bucket.