CompTIA Security+ SY0-701 Practice Test 43
Question 420
A legal archive encrypts each client's case file with its own random symmetric data-encryption key. Administrators want to rotate a central protection key without decrypting and re-encrypting terabytes of archived files. The protected key vault can perform cryptographic wrapping operations. Which design best meets that requirement?
- Save every plaintext file key in the same directory as its encrypted case file
- Wrap the per-file data keys under a protected key-encryption key and rewrap those keys when rotating the protector
- Use a single permanent unrotated key for all files so no mapping is required
- Replace encrypted archive files with public hashes and assume the original contents are recoverable
Explanation
Correct Answer
B:Envelope encryption separates bulk data encryption from protection of the smaller data keys. Each file is encrypted under its own data-encryption key, and that key is stored wrapped under a centrally controlled key-encryption key. When rotating the central protector, authorized software can unwrap and rewrap the small keys under the new version without reading and re-encrypting every file's data. The vault or HSM should enforce access policy, log key use and manage key versioning and recovery. Rotation must preserve access to needed historical keys until rewrapping is verified; otherwise archives could become unreadable. This directly fits the archive's performance and custody requirements while preserving per-file key separation.
Incorrect Answers
A:A plaintext data key stored alongside ciphertext gives anyone who steals the archive both the protected file and the means to decrypt it. Separate key custody is essential to envelope encryption. The archive may store wrapped keys next to ciphertext, but only when a protected key-encryption key is needed to unwrap them.
C:A single long-lived key would create a broad compromise domain: exposure of that secret could affect every client's archive. It also makes selective revocation and controlled rotation harder. The archive specifically needs independent per-file data keys, so replacing them with one unrotated key solves administrative effort by weakening the underlying security design.
D:A cryptographic hash is intentionally one-way and cannot reconstruct the original legal file. Hashes are useful for checking content integrity against a trusted reference, not for reversible confidentiality storage. The organization still needs encrypted contents and protected decryption keys to retrieve case files when authorized. The archived legal case requires authorized recovery of its original plaintext.
Question 421
A benefits portal recently renewed its TLS certificate. The certificate's subject and validity dates are correct, and browsers with cached issuer data still connect, but fresh mobile clients report that they cannot establish a path to a trusted issuer. A packet capture shows the server sends only its leaf certificate, although the issuer is an intermediate CA. Which deployment correction addresses the failure without weakening certificate authentication?
- Disable client-side hostname verification while retaining the new leaf certificate
- Add the renewed leaf certificate to every managed mobile device's trusted root store
- Reissue a new leaf with the same hostname and key, leaving the server configured to send no intermediate certificates
- Configure the server to transmit its valid intermediate CA certificate chain to a root already trusted by clients
Explanation
Correct Answer
D:A TLS server should present its leaf certificate and the appropriate public intermediate issuer certificates so clients can build a valid certification path to a root in their existing trust store. The missing intermediate explains why fresh clients fail even though some previously cached clients connect. Operations should install the correct chain in the server or reverse proxy, leave the root trust decision with clients, and retest hostname matching, expiration and chain-building from an uncached client. This fixes the deployment rather than overriding trust checks. It does not require distributing a server private key or disabling authenticated encryption.
Incorrect Answers
A:Hostname verification checks whether a trusted certificate identifies the name the user requested; chain construction asks whether a recognized issuer vouches for it. Switching off hostname checks cannot supply a missing intermediate, and it permits a certificate for an unrelated service to appear acceptable. It would make the portal less safe without repairing the specific path-building error.
B:Adding a server leaf to client trust stores could make a connection appear trusted under a locally configured exception, but it is not the normal solution for a missing intermediate chain. It creates brittle endpoint distribution and pinning problems, particularly when certificates rotate. The mobile clients already trust the intended public root; the server should transmit the intermediate needed to build a valid path. Private keys and root-trust settings should not be weakened to compensate for incomplete server configuration.
C:Reissuing the leaf may address an expiration, incorrect hostname or changed public key, but the stem says those properties already validate and that the missing object is the intermediate issuer. A new leaf that continues to omit the chain will not fix path building for clients lacking cached issuer certificates. The server needs to supply the appropriate intermediate chain, while clients continue validating to their existing trusted root.
Question 422
An inventory system sends JSON events to a billing service over HTTPS. Both systems already possess a separately managed secret, and the receiver must reject a payload modified between the sender and the queue, even if an intermediate queue worker is compromised. The services do not require publicly verifiable signatures. Which message-level verification design fits the existing trust arrangement?
- Append a plain SHA-256 checksum next to the JSON, using the payload as the only input
- Authenticate each canonicalized event with an HMAC using the shared secret, and verify the tag before processing
- Encode the JSON in Base64 and compare the original and received string lengths
- Rely solely on the receiver's TLS certificate even though the payload passes through the queue
Explanation
Correct Answer
B:An HMAC combines a cryptographic hash with a secret known to the legitimate communicating services. The receiver recomputes the tag over the exact agreed message bytes and compares it safely before accepting the event. A queue worker who changes payment amounts without the secret cannot create a matching tag. Use canonicalization or sign raw transmitted bytes consistently, protect and rotate the shared secret, and consider timestamps or unique event identifiers to reject replays. HMAC demonstrates possession of the same secret, not public non-repudiation; that is appropriate because the task expressly avoids externally verifiable signatures. HTTPS remains useful for transport confidentiality but is not sufficient to protect queued content afterward.
Incorrect Answers
A:An unkeyed hash detects an accidental mismatch if its expected value is obtained through a trustworthy independent channel. Here a compromised queue worker can modify the JSON and recalculate a plain SHA-256 checksum, so the receiver cannot distinguish an authorized sender from an editor. A message-authentication code is needed because authenticity, not only consistency, is required.
C:Base64 changes representation; it is reversible encoding, not encryption or an integrity guarantee. An attacker can edit the decoded JSON and encode the changed bytes again, often with the same overall length. Length comparisons miss modifications that preserve size and provide no evidence of which principal authored an event. The billing service needs a keyed cryptographic check.
D:A receiver-side TLS certificate authenticates the receiver to its HTTPS peer and secures that transport hop. It does not prove that a payload stored and forwarded by a separate queue was authored by the intended inventory service. Even mutually authenticated TLS on individual connections does not bind a tag to the unchanged business-event bytes throughout storage and forwarding.
Question 423
A cloud company discovers that an attacker copied the private key corresponding to its public HTTPS server certificate. The attacker also retained packet captures from six months of earlier connections. Those connections used ephemeral elliptic-curve Diffie–Hellman key exchange, and the ephemeral session secrets were never retained. Compared with a legacy static-RSA key exchange design, which security benefit is most relevant?
- Past encrypted sessions ordinarily remain protected from later theft of the certificate's long-term private key
- The stolen certificate key now allows the attacker to decrypt every prior ECDHE exchange automatically
- Ephemeral key exchange makes it unnecessary to validate a server certificate or its hostname
- The key-exchange mechanism also encrypts all offline database backups without additional controls
Explanation
Correct Answer
A:Forward secrecy separates short-lived traffic keys from the server's long-term authentication key. With properly implemented ephemeral ECDHE, a later theft of the certificate key does not by itself recover historical session secrets from recorded handshakes. The company should still rotate the compromised certificate key, revoke it as appropriate, investigate active impersonation and verify that ephemeral keys were not captured by endpoint compromise. Forward secrecy protects historical confidentiality under specified assumptions; it does not make the stolen long-term key harmless for future authentication. By comparison, older static-RSA key transport can expose captured past sessions when the corresponding private key is later obtained.
Incorrect Answers
B:This reverses the property of an ephemeral key agreement. If an attacker has only old packet captures and the later-stolen long-term signing key, the historical shared ECDHE secrets are not recoverable through that key alone. Endpoint memory disclosure, implementation defects or separately stolen session secrets could change the result, so the mechanism is not an unconditional guarantee against every compromise.
C:Certificates still authenticate who participated in the ephemeral key exchange. Without chain and hostname validation, an attacker can present its own key agreement and impersonate a service during a new connection. ECDHE provides key agreement and forward secrecy; it does not replace identity checking. The stolen certificate key also introduces a current authentication risk requiring independent response.
D:TLS protects application traffic during a network session. Key agreement does not automatically encrypt an unrelated database backup or make the stored archive unreadable to an attacker. Data-at-rest encryption needs its own algorithm, keys and access policies. Treating the two protections as interchangeable would overlook the backup system's separate confidentiality and recovery requirements.
Question 424
A fintech firm already signs settlement manifests through a central HSM containing a nonexportable private key. A recent incident showed that an application operator could change the HSM client's signing permissions and then authorize unexpected overnight signing transactions using a shared service credential. The firm will retain its HSM architecture. Which policy change best closes this authorization and accountability gap?
- Allow application operators to change HSM key permissions whenever a production change ticket exists, without independent approval
- Keep one shared client identity for all application operators and record only the total number of signatures per day
- Export the HSM signing key to a software escrow account used by administrators to approve urgent signing requests
- Separate key-policy administration from signing authorization, enforce scoped identities and approval controls, and retain attributable HSM operation logs
Explanation
Correct Answer
D:The HSM already provides private-key custody; the missing protection is governance of who may change signing policy and who may invoke the signing operation. Separate HSM policy administrators from application signing clients, require independent approval for high-risk permission changes, use unique scoped client identities and record attributable requests with tamper-resistant audit retention. Where business risk warrants it, require dual control for key-activation or sensitive policy changes and monitor anomalous signing. These restrictions directly prevent the operator from approving their own unauthorized signing path. Keeping the key nonexportable is still necessary, but repeating an HSM purchase would not solve this incident. The tested decision is authorization and separation of duties within an existing HSM service rather than choosing the HSM architecture itself.
Incorrect Answers
A:Change tickets support traceability but do not by themselves prevent an operator from granting their own signing privilege. The incident specifically involved unilateral permission changes followed by unauthorized operations, so the defect is a separation-of-duties and approval gap. An approved change process should identify independent authorization for sensitive key-policy changes and verify the resulting effective permissions. A ticket without a reviewer or technical enforcement leaves the same self-approval path intact even though the key remains inside the HSM.
B:A shared HSM client credential obscures which application or operator requested a signing operation. Aggregate counts might reveal unusual transaction volume but cannot reliably reconstruct who exercised authority on a particular manifest or detect a targeted misuse among normal signatures. The payment firm needs scoped workload identities, granular permissions and attributable operation records. Shared accounts may simplify deployment, but that convenience is incompatible with the specific investigative and authorization failures identified in the incident.
C:Exporting the signing key to software escrow would defeat the hardware nonexportability boundary and create a new secret that privileged administrators or attackers could copy. Escrow can be appropriate for some recovery requirements when implemented with strong controls, but it is not an authorization mechanism for day-to-day signing. The current risk arose from abuse of signing privileges, so the appropriate repair is to limit and independently approve those privileges while leaving the cryptographic key protected in the HSM.
Question 425
A biotechnology firm receives an unexpected cloud invoice after 240 GPU instances appear in a subscription used only for document storage. CloudTrail-like records show a stolen automation token launched the instances and mining software directed proceeds to an outside cryptocurrency address. The attacker made no political statement and the billing investigation found no confidential document downloads. What motive is most strongly supported?
- Financial profit from unauthorized consumption of the firm's cloud computing resources
- Ideological protest whose main evidence is public website defacement
- State-sponsored collection of laboratory research documents
- An approved GPU stress test requested by the cloud finance department
Explanation
Correct Answer
A:The attacker consumes metered compute paid for by the biotechnology firm while directing cryptocurrency rewards to a wallet the firm does not control. That is a clear financial incentive and an instance of cryptojacking through stolen cloud identity. A trustworthy classification distinguishes observed purpose from speculative actor identity; mining proceeds and abnormal instance creation support financial gain even if investigators cannot name the operator. The response should revoke the stolen token, isolate or terminate unauthorized resources without destroying useful evidence, review cloud roles and determine the billing impact. A financially motivated actor may also steal information, but that additional objective requires separate evidence not present in these logs.
Incorrect Answers
B:Hacktivism is plausible for disruptive operations carrying ideological messages, but the record does not show a manifesto, defacement or protest demand. The attacker instead ran revenue-generating software. Unwanted cloud expenditure can disrupt budgets, but an impact is not automatically the actor's primary motivation when the direct output is cryptocurrency revenue.
C:Espionage aims at acquiring protected intelligence or business information. Here investigators have evidence of unauthorized compute usage rather than collection of research files or sustained exfiltration. A sophisticated attacker might pursue multiple objectives, so document access should still be checked, but labeling this event espionage would exceed what the currently observed activity supports.
D:A legitimate stress test would have an authorized request, purpose, cost owner, timetable and workload records. Stolen automation credentials and mining proceeds paid to an external wallet contradict that explanation. Security should reconcile scheduled experiments and financial approvals, but it must not assume malicious resource consumption is approved merely because cloud administrators can normally start GPU instances.
Question 426
A systems integrator's contract for a municipal transport network expired last Friday. The client's identity team missed the offboarding task, and a former consultant used a still-active account to copy route-control configuration files to personal storage. Messages recovered from the consultant's account indicate resentment over an unpaid invoice. Which threat classification best captures the trust relationship that was abused?
- Classify the incident solely as an external unauthenticated breach because the consultant’s commercial contract has expired.
- Treat the copying as ordinary authorized contractor activity until the team can prove the credentials were technically invalid.
- Insider-style abuse of previously entrusted access after the consulting relationship ended
- Classify the event as a third-party supply-chain code compromise simply because the former consultant worked for a systems integrator.
Explanation
Correct Answer
C:The former consultant possessed knowledge and identity privileges originally entrusted by the organization, then used them outside the permitted purpose and period. This is insider-related misuse of access, even if the contractual engagement has ended; the critical failure is persistent credentials and insufficient monitoring of sensitive exports. Investigators should preserve evidence, revoke remaining sessions and tokens, examine whether other contractor accounts persist and coordinate lawful response with relevant stakeholders. Motivation may involve revenge, but the classification is primarily about abuse of prior trust. It differs from an unrelated external intrusion and from an approved handoff of configuration data.
Incorrect Answers
A:A former contractor may be outside the company’s current employment or contract boundary, but the incident did not involve an unknown unauthenticated entry. The consultant used an existing identity that had been entrusted with internal access and was not deprovisioned on time. That context is central to insider-style misuse and offboarding control failures. Describing the event only as an external unauthenticated intrusion would discard the access history established in the scenario.
B:An identity system can still accept a credential after the underlying contract ends, especially if the offboarding process fails. Technical sign-in success does not confer continuing authorization for copying protected route-control files to personal storage. The expired agreement, missing approval and personal destination create a meaningful trust violation. Investigators should preserve evidence and test intent, but they should not mistake a working account for a permitted business action.
D:Supply-chain compromise can involve a trusted vendor distributing altered software or exploiting a privileged maintenance channel. Nothing in the described evidence indicates malicious code was inserted into a supplier product. The known behavior is deliberate use of a still-active individual account to copy sensitive network configuration. The partner relationship matters for access governance, but it does not transform credential misuse into a software-supply-chain attack without further evidence.
Question 427
An online marketplace sees login attempts using millions of username-and-password pairs associated with publicly leaked databases. Attempts are spread across many unrelated customer accounts, each pair is tried only briefly, and successful logins are used to buy gift cards. Which technique and operating model best explain the campaign?
- A controlled password-reset drill performed by the marketplace's support staff
- Traditional exhaustive brute force against one account using a large list of generated variants
- Opportunistic credential stuffing that tests reused breach credentials across many accounts
- Password spraying that tries only a small set of commonly guessed passwords across all users
Explanation
Correct Answer
C:Credential stuffing takes username-password pairs obtained from one breach and tries them at other services on the assumption that some users reused credentials. Many modest-rate attempts across varied accounts, followed by gift-card purchases, match that mechanism. The retailer should correlate breached-pair indicators, device and network patterns, challenge anomalous sessions, enforce MFA where practical, and notify affected customers to rotate reused passwords. Distributed traffic can evade simple per-account lockout thresholds, so cross-account behavioral detection and rate controls are important. The evidence supports an opportunistic financial campaign rather than a specially tailored attack on one employee.
Incorrect Answers
A:A sanctioned reset exercise would use approved test identities or notifications and would not attempt purchases using unrelated real customers' credentials. The marketplace's evidence links previously exposed combinations to unauthorized access and financial abuse. Support staff should not classify actual credential reuse as internal testing merely because many authentication attempts occur.
B:A brute-force attack repeatedly guesses numerous possible secrets for a selected account or small target set. In this campaign the inputs are known username-password combinations from other breaches, and the effort is distributed across an enormous account population. That difference matters for detecting reuse patterns and coordinating compromised-account remediation instead of focusing only on one account's guess rate.
D:Password spraying typically tests one or a few popular password candidates over many different users, often to avoid lockouts. Here the attacker starts with millions of distinct leaked credential pairs, including account-specific passwords. Both attacks span many users, but their input sources and detection strategies differ; the available logs point to credential stuffing.
Question 428
A hospital's file servers display a ransom note signed with the name of a notorious crime syndicate. Investigators find that the malware configuration and command-and-control hosting do not match the group's previously documented campaigns, and the note can be copied from public reporting. The crisis team wants to publish definitive attribution. Which evidentiary treatment is most defensible?
- Accept the name written on the ransom note as proof of the real operator
- Conclude that all hospital employees are exonerated because the note names an outside group
- Treat the named group as an unverified claim and compare multiple independent indicators before attribution
- Discard conflicting technical evidence because the ransom note references a recognized group
Explanation
Correct Answer
C:Self-declared threat-group identity is an indicator to investigate, not a reliable verdict. Analysts should compare tooling, command-and-control infrastructure, timestamps, victimology and tactics with credible threat intelligence, while considering deliberate impersonation and shared criminal services. Conflicting observations should remain documented with confidence levels instead of being suppressed. Attribution can inform communication and threat hunting, but containment, key revocation and recovery should proceed on verified compromise facts even when actor identity remains uncertain. This approach avoids asserting an unsupported link between the hospital incident and a famous group based solely on branding that a copycat can reproduce.
Incorrect Answers
A:Attackers may copy notes, reuse branding, impersonate rivals or deliberately mislead responders. A widely recognized name can influence victims and the media without proving who operated the intrusion. Attribution should be supported by corroborating infrastructure, behavior and other evidence; naming a group from a note alone risks false claims and poorly targeted response.
B:A ransom note does not establish whether compromised insiders, negligent access management or third-party credentials played a role in initial access. The intrusion could involve multiple actors or access resale. Personnel conclusions require separate investigation and fair evidence, not a superficial inference from the supposed identity printed in the extortion message.
D:Suppressing contrary evidence introduces confirmation bias and can prevent discovery of the actual access path. A known gang name does not invalidate mismatched hosting, malware behavior or independently collected logs. Analysts must retain and test the discrepancies, especially because multiple unrelated operators can buy or borrow similar ransomware tooling. Such contradictions may reveal a rented ransomware package rather than operations by the group named in the note.
Question 429
A financial-services incident team discovers a crew that steals working VPN sessions, measures whether each can reach privileged administration panels, and posts the validated access for sale on a criminal marketplace. The crew has not deployed malware or requested payment from the victim company itself. Which role best describes its commercial objective?
- A hacktivist whose main goal is publishing policy messages on a defaced website
- An initial-access broker selling verified enterprise footholds to later intruders
- An authorized researcher performing coordinated disclosure under a defined testing scope
- A service provider conducting contractually scheduled remote administration
Explanation
Correct Answer
B:An initial-access broker specializes in obtaining and validating unauthorized entry into victim environments, then monetizes that access by selling it to ransomware operators, data thieves or other criminals. Confirmed VPN sessions and privilege notes increase the marketplace value of the foothold without requiring the broker to carry out later exploitation. Defenders should revoke stolen sessions, investigate original credential compromise and hunt for additional buyers who may already have used the access. The broker and the final payload operator may be different parties, so the absence of ransomware on the first day does not make the intrusion harmless. Evidence of resale directly supports this actor role.
Incorrect Answers
A:Hacktivists may compromise accounts, but their defining campaign objectives commonly involve ideological visibility or disruption. Here the recorded output is a priced marketplace listing of functional VPN footholds. Financial sale of access, rather than publication of political demands, explains why the crew tests reachability and documents privilege levels. Its marketplace prices and tested privileges provide more specific evidence of an access-resale business model.
C:Coordinated vulnerability disclosure follows documented authorization, a reporting channel and usually restrictions on accessing real client data. Selling authenticated enterprise sessions to unauthorized buyers is inconsistent with those boundaries. Even a technically sophisticated access test is not legitimate research when the actor lacks consent and intends to enable additional intrusions.
D:Managed support providers may connect remotely using designated identities, tickets and approved windows. Criminal marketplace listings and stolen VPN sessions show the opposite: unauthorized transfer of access to unknown third parties. The organization must not equate a valid connection with a legitimate service-provider activity when the credential source and business purpose contradict it.
Question 430
Two breaches affect different organizations. One attacker silently maintains access to a strategic aerospace laboratory and exports future propulsion designs without making demands. Another group encrypts a variety of retailers' systems and publishes payment instructions with deadlines. Which comparison most accurately describes their evidenced objectives?
- Both operations are security-awareness tests because the attackers used computer accounts
- The laboratory theft must be financially motivated because every intrusion primarily seeks direct payment
- The first incident shows intelligence collection, while the second most directly shows financial extortion
- Ransomware against commercial victims is necessarily political espionage rather than a profit-seeking operation
Explanation
Correct Answer
C:The aerospace attack prioritizes discreet access and acquisition of sensitive technical knowledge, supporting an espionage objective. The retailers face encryption plus explicit deadlines and payment instructions, which supports extortion for revenue. Either campaign could have secondary purposes, and the actor's nationality cannot be inferred with certainty from a motive alone. Nevertheless, evidence-based classification guides monitoring, response and risk communication: look for persistence and exfiltration in the first case, and contain propagation, preserve backups and address coercive demands in the second. The comparison is about observed goals, not a claim that every espionage event is state-directed.
Incorrect Answers
A:A legitimate exercise requires scope, rules of engagement and authorization. Covert extraction of strategic plans and coercive encryption with payment demands are not evidence of consent. The distinction being tested is attacker objective; mislabeling real compromise as training would delay incident response and obscure the very different recovery and disclosure needs.
B:Intellectual property can have monetary value, but silent sustained collection of aerospace plans without any payment mechanism primarily resembles espionage or strategic intelligence gathering. Analysts should classify what the operational evidence supports instead of assuming all attacks share the same direct financial motive. Attribution to a particular government also remains a separate question.
D:An attack against businesses is not automatically intelligence collection. Payment demands and broad coercive encryption are direct indicators of financial extortion, even if the attackers also stole files. Political or state-linked motives require additional signals, such as a sustained strategic target set or credible independent intelligence, rather than the simple fact that the victims operate companies.