A company is uploading important files as objects to Amazon S3. The company needs to be informed if an object is corrupted during the upload. What should a SysOps administrator do to meet this…

Question

Options

• APass the Content-Disposition value as a request body during the object upload
• BPass the Content-MD5 value as a request header during the object upload
• CPass x-amz-object-lock-mode as a request header during the object upload
• DPass x-amz-server-side-encryption-customer-algorithm as a request body during the object

• A
  4% (1)
• C
  88% (22)
• D
  8% (2)

Explanation

There is an error in this question - the marked correct answer (C) is wrong. The correct answer is B.

x-amz-object-lock-mode (option C) controls S3 Object Lock, a WORM (Write Once, Read Many) feature that prevents objects from being deleted or overwritten. It has nothing to do with detecting upload corruption.

Why B is correct: Including the Content-MD5 header with a pre-computed MD5 checksum of the object during upload tells S3 to verify the data integrity on arrival. If the object was corrupted in transit and the checksum doesn't match, S3 rejects the upload and returns an error - directly informing you of the corruption.

Why the other distractors are wrong:

• A (Content-Disposition): Controls how browsers handle the file on download (e.g., as an attachment) - purely a presentation hint, not integrity checking.
• C (x-amz-object-lock-mode): Governs object immutability/retention policies, not upload integrity.
• D (x-amz-server-side-encryption-customer-algorithm): Used to specify the encryption algorithm when providing your own encryption keys (SSE-C), unrelated to corruption detection.

Memory tip: Think "MD5 = Message Digest = data integrity." The Content-MD5 header acts like a fingerprint you hand to S3 so it can confirm the object arrived intact - if the fingerprints don't match, the upload fails.

You should verify this question against your study materials, as the marked answer appears to be a mistake in the question bank.

No community discussion yet for this question.