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

Verified by experts
3 products

You save $69.98

SY0-701 Premium Bundle

  • Premium File 1044 Questions & Answers
  • Last Update: Nov 18, 2026
  • Training Course 167 Lectures
  • Study Guide 1003 Pages
$79.99 $149.97

Purchase Individually

  • Premium File

    1044 Questions & Answers
    Last Update: Nov 18, 2026

    $76.99
    $69.99
  • Training Course

    167 Lectures

    $43.99
    $39.99
  • Study Guide

    1003 Pages

    $43.99
    $39.99

CompTIA Security+ SY0-701 Practice Test 5

Question 40

An organization uses a fleet of mobile devices, a cloud-based code-signing service, and a regulated database. It wants to keep private-key operations isolated. Which THREE statements are defensible design choices? Select THREE answers.

  1. A software-only encrypted file storing the code-signing private key on each build worker provides equivalent isolation to an HSM because the key is encrypted at rest.
  2. A shared HSM can centralize controlled cryptographic operations for a signing service or regulated workload.
  3. A TPM on a mobile device can be used as the single shared key service for all cloud build workers without a network signing architecture.
  4. A device secure enclave can help isolate private keys and operations from the general application environment, subject to platform capabilities.
  5. A cloud HSM guarantees the authorization of the software being signed, so separate build approvals and provenance controls can be removed.
  6. A TPM can provide hardware-backed protection for device-specific secrets and measured platform functions.

Explanation

Correct Answers

B:

A managed HSM can keep signing keys within a controlled cryptographic boundary while allowing authorized services to request operations. That is suitable for centralized code signing and some regulated workloads requiring separation of duties and audit trails. Capacity, availability and access policy must be engineered for the actual service. HSM authorization should bind a signing request to the permitted service and generate evidence for after-the-fact accountability.

D:

A secure enclave is intended to isolate particular sensitive operations from ordinary application processes, which can be valuable for device-bound authentication or signing. Its exact guarantees depend on the platform and implementation. It is not interchangeable with an enterprise signing service for every workload, but it is a valid key-isolation choice. The device team must verify platform-specific isolation and recovery semantics before relying on enclave storage for business continuity.

F:

A TPM is a hardware security component that can support device-bound key protection, measurements and attestation-related functions. It can make extraction harder than storing a key in a general user-space file, although it does not eliminate all compromise risks. The fleet can use it for appropriate device-level operations. Evidence about TPM-backed identity should be tied to the actual enrolled device rather than treated as proof of a human user.

Incorrect Answers

A:

Encrypted storage can protect a key while the worker is inactive, but a signing job normally needs the plaintext key or access to decrypt operations in the worker environment. Compromise of that worker can therefore expose signing authority. A well-controlled HSM holds key material in a separate boundary and can restrict individual signing operations.

C:

A TPM is primarily attached to a particular platform and can secure device-bound secrets and measurements. It is not automatically a remotely accessible, shared enterprise signing service. Using one device TPM for every distributed build would create access, availability and governance problems; the organization still needs an explicit signing-service design.

E:

An HSM protects specified cryptographic operations but does not judge whether a submitted program is trustworthy. If a compromised pipeline is authorized to request signatures, the HSM may sign malicious artifacts correctly. The code-signing service still needs controlled release approval, artifact provenance, separation of duties and a revocation procedure.

Question 41

A university uses a managed key service for encrypted research databases. Several applications share a long-lived encryption key, and a departure has exposed a risk that past credentials were copied. Which key-management response is most appropriate?

  1. Rotate to a new encryption key and immediately destroy all previous key versions before verifying that historical backup snapshots can be decrypted.
  2. Rotate and reauthorize key access under a documented plan, retain required decrypt capability for existing data, and audit past access.
  3. Revoke the departed person’s interactive university account, but leave the shared application key and every workload’s existing key grants unchanged.
  4. Place the shared key in a central secrets vault with permanent read permissions for every research service, then treat vault placement as sufficient rotation.

Explanation

Correct Answer

B:

Rotating keys and tightening access can limit the future value of copied credentials, while access reviews and audit logs clarify potential misuse. Existing ciphertext may still require controlled use of prior key versions or re-encryption. The decision should include ownership, dependency testing and secure retirement after data migration. The university should inventory which applications still need previous key versions before setting final destruction dates.

Incorrect Answers

A:

Key rotation limits exposure only if existing encrypted information remains recoverable through retained old versions or a verified re-encryption plan. Destroying the prior key before checking archived copies could cause permanent data loss. A safe rotation inventory identifies ciphertext dependencies, verifies restore capability, and retires keys only when authorized data no longer needs them.

C:

Disabling the employee account is appropriate but incomplete when credentials might have been copied and a single key is shared among multiple applications. Existing service identities and access tokens may remain usable independently of that account. The incident requires review of key use, scope, credential revocation, and planned rotation with continuing decrypt capability.

D:

A vault can centralize custody and provide useful logging, but broad permanent grants preserve the same excessive access surface. Simply moving the key does not revoke copied values or rotate the material protecting old ciphertext. The university should reauthorize individual workloads, rotate where feasible, and confirm the vault enforces least privilege.

Question 42

A financial consortium considers placing transaction proofs on an open public ledger instead of its existing signed, append-only audit repository. Which conclusion best compares the two approaches?

  1. Use a public ledger's consensus history as the sole assurance control and remove validation of transaction records before they are submitted.
  2. Keep the signed private audit repository but permit updates to the upstream transaction feed without retaining who changed the source records.
  3. Both approaches must be evaluated for who can append entries, verify signatures, detect rewrites and trust the underlying business data.
  4. Move proofs to an open ledger but permit anonymous transaction insertion, assuming that a publicly verifiable timestamp also proves which consortium member approved the entry.

Explanation

Correct Answer

C:

A consortium should compare independent verification, write permissions, signed provenance and resistance to silent history changes under both designs. An appropriately protected signed, append-only repository may already meet some requirements without needing a blockchain. Neither option independently proves business truth or compensates for compromised signers. A decision matrix should include participant independence, performance, key compromise response and how wrong inputs are corrected.

Incorrect Answers

A:

Consensus can make a record sequence resistant to undetected alteration under specific trust assumptions, but it cannot verify that the original amounts, identities, or approvals were true. If a signer submits an inaccurate transaction, the ledger can durably preserve that inaccuracy. Input controls and signer accountability remain necessary.

B:

A protected append-only destination does not preserve the provenance of information already altered in a mutable upstream system. The consortium needs signed source events, custody of ingestion identities, and checks that feed changes are authorized. Otherwise the repository can faithfully log a compromised or inaccurate input stream.

D:

Publicly verifiable ordering or timestamps are not the same as authenticated organizational approval. If entries can be submitted anonymously, the consortium may lose the ability to attribute business decisions even while history remains tamper-evident. Membership credentials and signer checks must be evaluated separately from ledger consensus.

Question 43

An identity platform stores password-verifier hashes. An attacker may obtain the database and perform offline guessing. Which configuration most directly raises the cost of each guess while preventing identical passwords from sharing identical stored verifiers?

  1. Use a fast general-purpose hash without a salt so every login is quick.
  2. Encrypt the user interface HTML and store plaintext passwords in the database.
  3. Apply one fixed organization-wide salt to every password and calculate a fast general-purpose hash for each stored verifier.
  4. Use a unique random salt per password and a suitably configured password-stretching function with a measured work factor.

Explanation

Correct Answer

D:

A unique salt prevents straightforward equality comparisons and broad reuse of precomputed guesses across accounts. A memory-hard or suitably slow password-hashing construction raises the attacker’s cost per offline candidate. Tuning must balance measured login latency and server resources without inventing a universal work factor. The database should retain parameters needed to verify legitimate passwords. Using per-account salt and calibrated cost parameters is especially important when the attacker can perform unlimited offline trials.

Incorrect Answers

A:

A very fast general-purpose digest makes large-scale offline guessing comparatively cheap. Without unique salts, equal passwords often yield equal verifiers, enabling attackers to reuse work across accounts. Login speed is not the only design concern; resistance to offline guessing matters after database theft.

B:

Protecting an HTML interface does not make stored plaintext passwords safe. A database breach would expose immediate reusable secrets without any guessing work. Password storage should use a purpose-built verifier construction, not merely encrypt the page that collects credentials. No browser-side cosmetic protection can compensate for plaintext credentials exposed through a database breach.

C:

A common salt may reduce the usefulness of some precomputed tables but still allows two users with the same password to have matching stored verifiers under that fixed salt. The quick digest also permits rapid offline password guesses. A different unpredictable salt for each password plus a deliberately expensive password-hashing algorithm addresses both weaknesses simultaneously.

Question 44

A manufacturing supplier sends a digitally signed calibration certificate. A customer verifies that the signature mathematically matches the document, but the signing certificate was revoked after a report of private-key theft. There is no independently trusted signing timestamp showing when the document was signed. What can the customer conclude about the document’s provenance?

  1. A mathematically valid signature proves that the authorized supplier approved the document, even if the private key might have been stolen before signing.
  2. The signature may confirm that the bytes match the signing key, but trusted signer attribution still requires certificate, revocation, key-custody and reliable signing-time evidence.
  3. Certificate revocation proves the signed calibration values were modified during delivery, regardless of whether signature verification succeeds.
  4. Matching the visible supplier name and a locally calculated file hash is sufficient evidence of authorized approval, so key-revocation history can be ignored.

Explanation

Correct Answer

B:

Cryptographic verification links the document bytes to the corresponding signing key, but provenance also depends on whether that key was legitimately controlled when signing occurred. Revocation following suspected theft creates a material trust question. Without a trusted timestamp establishing a pre-compromise signing time, the customer should not claim the certificate proves authorized supplier approval. Investigators should preserve the signature, chain, revocation evidence and issuer communications.

Incorrect Answers

A:

A cryptographically valid signature demonstrates that a particular private key signed those bytes; it does not demonstrate who controlled a compromised key at the time. A thief could produce a mathematically valid signature. The customer must evaluate the signer’s public-key identity, certificate status and reliable signing-time evidence before attributing the document to an authorized supplier.

C:

Revocation concerns trust in a key or certificate, not the arithmetic of the document digest. A legitimately signed file can remain byte-for-byte unchanged after the signing credential is revoked. The customer has to distinguish integrity of the submitted bytes from authority of the signer at an uncertain time; asserting document modification would overstate the evidence.

D:

The visible name can be typed by anyone and a locally calculated digest only identifies the bytes currently in hand. Neither proves that an authorized supplier keyholder approved them. A compromised or untrusted signing credential can still generate matching hash and signature values. Provenance requires verifying the trusted key relationship and relevant signing-time circumstances.

Question 45

A municipal investigation team embeds an invisible provenance marker in images published to external reviewers. The team claims the technique protects confidentiality in the same way as strong encryption. Which response is technically accurate?

  1. An invisible provenance watermark can use steganographic embedding, but it does not by itself encrypt image contents or provide cryptographic proof against alteration.
  2. The presence of any steganographic content guarantees that attackers cannot extract or alter the hidden bits.
  3. Apply a robust invisible watermark that survives ordinary recompression, then treat its presence as cryptographic proof the image was not altered.
  4. A watermark makes cryptographic integrity verification unnecessary for any later modification dispute.

Explanation

Correct Answer

A:

Hiding a provenance marker in image data is a watermarking technique that may use steganographic embedding. Concealment of a marker is not equivalent to encrypting the image: the image remains readable, and the embedded mark may be discovered, altered, or lost after editing. For a high-assurance modification dispute, retain an authenticated original and a verifiable signed digest or comparable integrity evidence. The marker helps attribution but does not substitute for confidentiality or cryptographic authenticity controls.

Incorrect Answers

B:

Steganographic marks are not universally resilient to editing, recompression or deliberate extraction. Their concealment depends on the embedding method and transformations applied. Claims of guaranteed secrecy or immutability are not supported by the fact that a marker is visually unobtrusive.

C:

Watermarks can help track distribution or provenance, and some are designed to survive routine image processing. Their presence is not a cryptographic integrity proof for all pixels, however; a signer-controlled digest and verifiable signing identity are different evidence needed for high-confidence modification claims.

D:

A watermark may add contextual evidence but does not prove that every pixel is unchanged after publication. For high-assurance integrity, the agency should retain trusted original files and use signed digests or other verifiable provenance mechanisms. Marks and signatures serve different evidentiary roles.

Question 46

A cloud service presents a TLS certificate signed by an unfamiliar self-signed issuer. The client has no trusted root or approved pin for that issuer. What should the administrator conclude?

  1. Accept the self-signed issuer if its subject and issuer names match and the certificate signature verifies using the key it contains.
  2. Accept the certificate if the subject alternative name matches the server and the connection negotiates current TLS encryption, leaving the unknown issuer unvalidated.
  3. The trust chain cannot be validated using the current trust store; establish a controlled trust anchor or obtain a certificate from a trusted issuer.
  4. Add the issuer to every workstation trust store on first observation without independently verifying its fingerprint or ownership.

Explanation

Correct Answer

C:

The unfamiliar issuer is outside the client’s approved trust anchors, so the presented chain cannot establish trusted server identity. The team can use a properly managed internal root or a recognized third-party CA where appropriate, with correct names and lifecycle controls. Bypassing validation would conceal rather than solve the identity problem. The cloud operator should test a valid hostname against the new trust chain before enabling production access.

Incorrect Answers

A:

A self-signature can be mathematically valid even on a certificate generated by an untrusted party. Signature verification with a key supplied in the same untrusted certificate does not establish why this issuer should be trusted. The client needs an independently approved trust anchor or an authenticated, narrowly scoped pin and hostname validation.

B:

Hostname matching and strong TLS negotiation are necessary checks in many use cases, but they cannot establish an unauthenticated issuer as an authorized signing authority. An attacker can generate a matching self-signed name and offer modern ciphers. A trustworthy chain or independently managed pin is still required to authenticate the destination.

D:

Installing an unknown issuer as a broadly trusted root may extend an impersonation risk across unrelated applications, especially if the initial connection is intercepted. Trust-anchor enrollment should use an authenticated out-of-band source, defined purpose and lifecycle controls. The scenario supplies neither approved identity proof nor a reason for fleet-wide trust.

Question 47

A hospital validates partner TLS certificates but its network sometimes loses connectivity to online status services. Which TWO statements correctly describe CRLs and OCSP in this situation? Select TWO answers.

  1. A CRL provides a CA-issued list of revoked certificate identifiers that a client can obtain and consult, subject to update timing.
  2. When OCSP is unreachable, treat the certificate as valid if its expiration date is in the future, without considering a documented revocation-failure policy.
  3. Use a successful OCSP response to override an untrusted issuer, because revocation status is stronger evidence than certificate-chain trust.
  4. Use a cached CRL beyond its next-update validity period whenever the hospital cannot reach the distribution point, without marking its freshness as uncertain.
  5. OCSP permits a client to query a status responder about a particular certificate, subject to responder availability and trust validation.

Explanation

Correct Answers

A:

A certificate revocation list is signed status information published by an issuer and can be checked for a listed certificate serial number. Its freshness depends on retrieval and validity intervals. A cached CRL may support some offline checks, but the client still needs appropriate trust and update policy. The hospital must define how expired cached lists affect connection handling rather than silently accepting stale status.

E:

OCSP can provide status for a specific certificate through a responder, allowing potentially fresher checks than a periodically obtained list. The response must be authenticated and the client’s handling of network failures must follow its approved validation policy. An unreachable responder does not by itself establish revocation. The team should verify responder trust and choose a documented failure policy for critical partner connections.

Incorrect Answers

B:

Certificate validity dates do not tell the client whether an otherwise unexpired certificate was revoked. Some applications may explicitly fail open under stated risk assumptions, but the scenario gives no authorization for silently bypassing status requirements. A responder outage should be handled according to the chosen validation policy and recorded as unavailable evidence.

C:

An OCSP response answers a status question about a particular certificate under a recognized issuer or trusted responder relationship. It does not independently establish that the issuing CA belongs to the intended partner. Path validation, hostname checks and revocation status are complementary, not competing, identity checks.

D:

A cached CRL can be helpful during temporary connectivity loss while it remains valid under the client’s policy. An expired list may miss newly revoked certificates and is not equivalent to fresh status. The hospital must define how status unavailability affects high-risk partner sessions rather than silently extending old evidence indefinitely.

Question 48

In a retailer's private test PKI, an internal certificate authority receives a certificate signing request (CSR) for *.example.test, intended for app.example.test and payroll.example.test. Which TWO checks should the internal certificate reviewer perform before issuance? Select TWO answers.

  1. The CSR should include the plaintext private key so the CA can perform all future TLS negotiations.
  2. Hostname validation becomes unnecessary when a CSR contains a wildcard.
  3. The wildcard *.example.test matches an immediate subdomain label such as app.example.test, but not the bare example.test name or arbitrary deeper subdomains.
  4. The wildcard automatically authorizes anyone who possesses the certificate to operate every business system in the organization.
  5. The CSR's public key and requested subject alternative names match the intended internal endpoint identities and the applicant is authorized to use those internal DNS names.

Explanation

Correct Answers

C:

A single-label wildcard can cover the two immediate hostnames in this internal test namespace, but it does not cover the apex or hosts with additional subdomain labels. The certificate team must check name matching before issuance and document where the wildcard key may be installed. The reserved .test namespace is used here under a private CA rather than to imply public CA validation of a real internet domain.

E:

A certificate request binds a public key to the proposed identities. Before signing it, the private CA must verify that the requesting service is authorized to use the internal test namespace and that requested SANs correctly describe the intended application and payroll endpoints. A CSR does not submit its plaintext private key to the CA. Independent permission to operate the named services is still required beyond possession of the eventual TLS certificate.

Incorrect Answers

A:

The applicant keeps the private key secret; the CA uses the public key in the CSR and domain validation to issue the certificate. Sending the plaintext private key to a CA would create unnecessary exposure and defeat key-custody responsibilities. Issuance does not require that disclosure.

B:

Wildcard certificates still require hostname matching and trusted chain checks, just like more narrowly named certificates. A wildcard only changes which hostnames may satisfy name validation. Omitting name checks would allow certificate presentation outside its intended scope and weaken server authentication.

D:

A TLS certificate establishes a form of endpoint identity and key binding for specified names. It does not grant application authorization or permission to administer payroll systems. Systems still need account controls, role enforcement and appropriate key custody even if a single wildcard certificate is accepted.

Question 49

During an outage at a logistics hub, an intruder encrypts dispatch databases and leaves a message demanding cryptocurrency within 24 hours. Investigators find no attempt to extract proprietary routing algorithms. What motivation is most strongly supported by the available evidence?

  1. Financially motivated extortion by a criminal actor, while attribution of the actor's identity remains open.
  2. Economic espionage masked by ransomware, because logistics route data might be valuable even if this investigation has not found collection activity.
  3. Insider sabotage using a planted ransom note to disguise retaliation, because loss of dispatch availability could also harm the logistics company.
  4. Ideological disruption disguised as extortion, because logistics services could be politically symbolic even without a published manifesto.

Explanation

Correct Answer

A:

The ransom demand and deliberate encryption impose operational pressure to pay for restoration, directly supporting financial extortion as a motive. That classification does not require identifying a named criminal group. Investigators should preserve the note, affected system images and payment indicators while independently checking whether data was also stolen.

Incorrect Answers

B:

The dispatch environment may contain valuable operational intelligence, so a disguised espionage hypothesis can be investigated. However, the case supplies no extraction of route data or other espionage indicators. A direct cryptocurrency demand paired with encrypted dispatch systems supports immediate financial extortion more strongly; investigators should not promote a possible alternate motive into the primary supported finding.

C:

A disgruntled insider could hypothetically stage an outage and forge a demand to misdirect investigators, but there is no evidence of insider access, grievance, or false-flag activity. The stated attacker demanded payment in exchange for an encrypted-data disruption. Treat insider sabotage as a possible line of inquiry rather than the best-supported current motive.

D:

Ideological attackers sometimes target symbolic logistics infrastructure, and a false payment demand is theoretically possible. But the scenario offers no advocacy statement, political objective, or credible group claim. In contrast, the specified cryptocurrency deadline is direct evidence of monetization, making extortion the more defensible initial classification.

Question 50

An industrial plant's engineering repository exports 8 GB overnight. Access records show a valid badge and VPN session for an employee, but the same token was previously used from a supplier network. What conclusion about insider versus external threats is justified first?

  1. The incident must be malicious insider theft because an employee badge appears in the log.
  2. The supplier is definitely responsible because its network once used the token.
  3. Both insider misuse and an external actor using stolen access remain hypotheses until the session and identity evidence are correlated.
  4. The export cannot be an attack because the system accepted a valid credential.

Explanation

Correct Answer

C:

The appropriate initial classification preserves competing explanations while gathering token issuance details, device posture, badge events and VPN source information. Valid authentication is not a reliable identity guarantee when credentials might be stolen. This evidence-based approach protects the plant from premature accusations without delaying containment of the suspicious export.

Incorrect Answers

A:

A badge record proves a credential was presented, not that the associated person performed every later digital action. Stolen or shared credentials could explain the export. Without matching endpoint, token issuance and physical presence evidence, an unequivocal insider accusation would overstate what the industrial plant can demonstrate.

B:

The previous supplier-network event is suspicious and should be investigated, but it does not identify the export's operator by itself. Legitimate vendor sessions, proxy services and stolen tokens have different implications. The team needs session continuity and authorization records before attributing malicious responsibility to a particular outside party.

D:

Authorized-looking sessions can be exploited by insiders or by attackers controlling credentials. The unusually large transfer may violate job scope despite a successful login. Access logs establish what the system permitted, not whether the action was intended or genuinely authorized by the person whose account appears.

CompTIA Security+ (SY0-701) Practice Tests

Purchase Individually

  • Premium File

    1044 Questions & Answers
    Last Update: Nov 18, 2026

    $76.99
    $69.99
  • Training Course

    167 Lectures

    $43.99
    $39.99
  • Study Guide

    1003 Pages

    $43.99
    $39.99

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

You save
10%

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

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

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

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

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

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