An engineer needs to ensure that a script has not been modified before it is launched. Which of the following best provides this functionality?

Question

Options

• AMasking
• BObfuscation
• CHashing
• DEncryption

• A
  2% (1)
• B
  7% (3)
• C
  89% (39)
• D
  2% (1)

Explanation

Hashing is correct because it generates a fixed-length digest (fingerprint) of a file's contents - if even one byte changes, the hash changes. Before launching a script, you compute its hash and compare it against a known-good value; a mismatch proves tampering occurred. This is exactly how tools like sha256sum or code-signing pipelines verify integrity.

Masking (A) hides sensitive data (e.g., replacing credit card digits with ****) - it has nothing to do with detecting modifications. Obfuscation (B) makes code harder to read, but does not detect whether it was changed. Encryption (D) protects data confidentiality in transit or at rest, but decrypting a file tells you nothing about whether it was altered before encryption.

Memory tip: Think "Hash = fingerprint for integrity." Just as a fingerprint uniquely identifies a person, a hash uniquely identifies a file's exact contents - any change leaves a different fingerprint behind.

No community discussion yet for this question.