hardmultiple choiceObjective-mapped

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?

Question 1hardmultiple choice
Full question →

Based on the exhibit, which cryptographic mechanism provides proof that the update came from the vendor and was not altered?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Hashing, because matching SHA-256 values alone prove the file came from the vendor.

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

Distractor review

Symmetric encryption, because only the vendor and the customer share the secret key.

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

Best answer

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

Distractor review

Salting, because adding random data makes the update file easier to trust.

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 trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Static NAT maps one inside address to one outside address.

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. — A digital signature is the correct mechanism because it lets the customer verify that the update was signed by the vendor's private key and that the contents were not altered after signing. A matching hash alone only proves the file is unchanged relative to the expected hash value. The signature adds authenticity, which is what the audit note specifically requires. Why others are wrong: A hash can detect changes only when the trusted value is already known and trustworthy. Symmetric encryption protects secrecy, not public proof of origin. Salting is for password hashes, not file verification. The exhibit's verified signature is the key clue because it ties the file to the vendor's private key and protects against tampering.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.