Question 146 of 504
CryptographyeasyMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is to sign the update with the developer's private key. This cryptographic technique ensures software update integrity because the digital signature, created with the private key, is mathematically bound to the update file; any tampering during download breaks the signature, and verification with the corresponding public key confirms both that the file is unchanged and that it originated from the claimed developer. On the Systems Security Certified Practitioner SSCP exam, this concept tests your understanding of asymmetric cryptography in code signing scenarios, often appearing in questions about secure software distribution or Authenticode. A common trap is confusing hashing alone with signing—hashing only detects changes, but without a private key signature, it cannot prove authenticity. Remember the memory tip: “Sign with private, verify with public—integrity and origin, not just a hash.”

SSCP Cryptography Practice Question

This SSCP practice question tests your understanding of cryptography. 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.

An organization wants to ensure that a software update has not been tampered with during download. Which cryptographic technique should be used?

Question 1easymultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Sign the update with the developer's private key

Signing the update with the developer's private key provides both integrity and authenticity. When the user verifies the signature using the developer's public key, they can confirm that the update has not been tampered with and that it originated from the claimed developer. This is the standard approach for ensuring trust in software distribution, as used in code signing certificates (e.g., Authenticode, GPG).

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.

  • Compute a SHA-256 hash of the update

    Why it's wrong here

    Hashing provides integrity but no authentication of the source.

  • Sign the update with the developer's private key

    Why this is correct

    A digital signature ensures integrity and authenticates the developer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Encrypt the update with AES

    Why it's wrong here

    Encryption provides confidentiality, not integrity.

  • Append a MAC (Message Authentication Code)

    Why it's wrong here

    A MAC requires a shared secret, which may not be feasible for public downloads.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse integrity-only mechanisms (hash, MAC) with the combined integrity and authenticity provided by digital signatures, or they mistakenly think encryption (AES) prevents tampering when it only provides confidentiality.

Detailed technical explanation

How to think about this question

Digital signatures use asymmetric cryptography: the developer signs the hash of the update with their private key, and the user verifies the signature with the corresponding public key. This process is defined in standards like PKCS#7 (CMS) or RFC 4880 (OpenPGP). A subtle behavior is that the signature itself does not encrypt the update, so the update remains readable, but any modification invalidates the signature, providing strong tamper evidence.

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.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SSCP practice-question pages

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

Practice this exam

Start a free SSCP practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SSCP question test?

Cryptography — This question tests Cryptography — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Sign the update with the developer's private key — Signing the update with the developer's private key provides both integrity and authenticity. When the user verifies the signature using the developer's public key, they can confirm that the update has not been tampered with and that it originated from the claimed developer. This is the standard approach for ensuring trust in software distribution, as used in code signing certificates (e.g., Authenticode, GPG).

What should I do if I get this SSCP 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SSCP practice questions

Last reviewed: Jun 25, 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.

Loading comments…

Sign in to join the discussion.

This SSCP practice question is part of Courseiva's free ISC2 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 SSCP exam.