The answer is digital signature, because only the vendor’s private key can produce a signature that verifies with the corresponding public key, proving both authenticity and integrity. A digital signature uses asymmetric cryptography: the vendor signs the update with their private key, and the customer validates it using the vendor’s public key. If the signature checks out, the update is confirmed as coming from the vendor and unaltered, since any tampering would break the cryptographic verification. On the Security+ SY0-701 exam, this concept tests your understanding of how digital signatures differ from hashing—hashing alone ensures integrity but not authenticity, as it lacks a private key component. A common trap is confusing a hash value for a signature; remember that a hash only detects changes, while a digital signature also proves the source. Memory tip: “Sign with private, verify with public—hash is just a fingerprint, a signature is a sealed envelope.”
SY0-701 General Security Concepts Practice Question
This SY0-701 practice question tests your understanding of general security concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Package verification steps:
1. sha256sum update.zip = 9f7c2a4b6f1d8e4c...
2. Vendor website shows the same hash
3. openssl dgst -sha256 -verify vendor_pub.pem -signature update.zip.sig update.zip
Verified OK
Audit note:
The security team wants proof of origin, not just proof that the file content stayed the same.
Based on the exhibit, which cryptographic mechanism provides proof that the update came from the vendor and was not altered?
Package verification steps:
1. sha256sum update.zip = 9f7c2a4b6f1d8e4c...
2. Vendor website shows the same hash
3. openssl dgst -sha256 -verify vendor_pub.pem -signature update.zip.sig update.zip
Verified OK
Audit note:
The security team wants proof of origin, not just proof that the file content stayed the same.
A
Hashing, because matching SHA-256 values alone prove the file came from the vendor.
Why wrong: A hash can confirm integrity if the expected value is trustworthy, but it does not prove who created the file or the hash. If an attacker can alter both the file and the published hash source, the match becomes meaningless. The exhibit asks for proof of origin, which requires more than a checksum comparison.
B
Symmetric encryption, because only the vendor and the customer share the secret key.
Why wrong: Symmetric encryption protects confidentiality, but it does not provide a strong public proof of origin for software distribution. Both sides would need the same secret key, and sharing that key widely would make distribution and verification harder. The scenario is about authenticity and tamper evidence, which are better addressed by signatures.
C
Digital signature, because only the vendor's private key can produce the verified signature.
Digital signature is correct because the signature check proves both integrity and authenticity. The vendor signs the update with a private key, and anyone with the matching public key can verify that the file has not changed and that the signer possessed the private key. That is exactly the proof of origin the audit note is asking for.
D
Salting, because adding random data makes the update file easier to trust.
Why wrong: Salting is used with password hashing to make precomputed attacks harder. It is not a mechanism for proving software origin or file integrity. Adding a salt would not tell the customer who created the update or whether it was altered after signing. The concept belongs to password storage, not software verification.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Digital signature, because only the vendor's private key can produce the verified signature.
Option C is correct because a digital signature uses the vendor's private key to sign the update, and the customer verifies it using the vendor's public key. This asymmetric cryptographic mechanism ensures both authenticity (the update came from the vendor) and integrity (the update was not altered), as only the vendor's private key can produce a signature that validates with the corresponding public key.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Hashing, because matching SHA-256 values alone prove the file came from the vendor.
Why it's wrong here
A hash can confirm integrity if the expected value is trustworthy, but it does not prove who created the file or the hash. If an attacker can alter both the file and the published hash source, the match becomes meaningless. The exhibit asks for proof of origin, which requires more than a checksum comparison.
✗
Symmetric encryption, because only the vendor and the customer share the secret key.
Why it's wrong here
Symmetric encryption protects confidentiality, but it does not provide a strong public proof of origin for software distribution. Both sides would need the same secret key, and sharing that key widely would make distribution and verification harder. The scenario is about authenticity and tamper evidence, which are better addressed by signatures.
✓
Digital signature, because only the vendor's private key can produce the verified signature.
Why this is correct
Digital signature is correct because the signature check proves both integrity and authenticity. The vendor signs the update with a private key, and anyone with the matching public key can verify that the file has not changed and that the signer possessed the private key. That is exactly the proof of origin the audit note is asking for.
Related concept
Read the scenario before looking for a memorised answer.
✗
Salting, because adding random data makes the update file easier to trust.
Why it's wrong here
Salting is used with password hashing to make precomputed attacks harder. It is not a mechanism for proving software origin or file integrity. Adding a salt would not tell the customer who created the update or whether it was altered after signing. The concept belongs to password storage, not software verification.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse hashing with digital signatures, thinking that a hash match alone proves the source, when in fact hashing only verifies integrity, not authenticity or non-repudiation.
Trap categories for this question
Scenario analysis trap
Symmetric encryption protects confidentiality, but it does not provide a strong public proof of origin for software distribution. Both sides would need the same secret key, and sharing that key widely would make distribution and verification harder. The scenario is about authenticity and tamper evidence, which are better addressed by signatures.
Detailed technical explanation
How to think about this question
Digital signatures rely on asymmetric cryptography, typically using RSA or ECDSA, where the vendor signs the hash of the update file with their private key. The customer verifies the signature by decrypting it with the vendor's public key and comparing the result to a freshly computed hash of the received file; if they match, the update is authentic and unaltered. In practice, this is often implemented using PKCS#7 or CMS (Cryptographic Message Syntax) as seen in code signing certificates, and the verification process is specified in RFC 2315 or RFC 5652.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SY0-701 question in full detail.
General Security Concepts — This question tests General Security Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Digital signature, because only the vendor's private key can produce the verified signature. — Option C is correct because a digital signature uses the vendor's private key to sign the update, and the customer verifies it using the vendor's public key. This asymmetric cryptographic mechanism ensures both authenticity (the update came from the vendor) and integrity (the update was not altered), as only the vendor's private key can produce a signature that validates with the corresponding public key.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Before installing a vendor patch package on hundreds of endpoints, the security team wants to confirm the file was published by the vendor and was not altered during download. Which two verification steps should the team perform? Select two.
hard
✓ A.Verify the package signature with the vendor's public key.
✓ B.Compare the downloaded package hash to the hash in the signed manifest.
C.Decrypt the package with the vendor's private key before installation.
D.Rotate the organization's internal encryption key before downloading.
E.Check only the file timestamp and size on disk.
Why A: Option A is correct because verifying the package signature with the vendor's public key confirms the package was cryptographically signed by the vendor, proving its authenticity and integrity. This process uses asymmetric cryptography where the vendor signs the package with their private key, and the security team uses the corresponding public key to validate that signature. It ensures the file was not tampered with after signing and that it originated from the claimed vendor.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.