Which solutions for the script will meet these requirements?
(Choose two.)
Check the returned response for the VersionId. Compare the returned VersionId against the MD5 checksum.
Include the MD5 checksum within the Content-MD5 parameter. Check the operation call’s return status to find out if an error was returned.
Include the checksum digest within the tagging parameter as a URL query parameter.
Check the returned response for the ETag. Compare the returned ETag against the MD5 checksum.
Include the checksum digest within the Metadata parameter as a name-value pair. After upload, use the S3 HeadObject operation to retrieve metadata from the object.
Explanations:
The VersionId is not related to MD5 checksums. It is an identifier for a specific version of an object in S3, not a checksum for verifying data integrity.
Including the MD5 checksum within the Content-MD5 parameter allows Amazon S3 to verify that the data being uploaded matches the checksum. If the upload fails, the error will be returned.
The checksum digest cannot be included in the tagging parameter as it is not intended for integrity checks. Tags are used for object metadata and classification.
The ETag for an object is usually the MD5 checksum of the object (unless multipart uploads are used). Comparing the returned ETag with the expected MD5 checksum verifies data integrity.
The Metadata parameter stores user-defined metadata but is not used for checksum verification. The HeadObject operation can be used to retrieve metadata but does not help with MD5 verification.
I plan that the answer is:
Include the MD5 checksum within the Content-MD5 parameter. Check the operation call’s return status to find out if an error was returned.