Which solutions for the script will meet these requirements?
(Choose two.)
Check the returned response for the Versionld. 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 in the S3 response refers to the version of the object in S3, but it is not related to verifying the data integrity or checksum comparison.
The Content-MD5 parameter is used to send an MD5 checksum with the upload request. The response can then be checked to see if there was an error, ensuring data integrity.
The checksum included in the tagging parameter is not a valid or standard method to verify data integrity during the upload process.
The ETag is often the MD5 checksum of the object in S3, and it can be compared to the MD5 checksum calculated before the upload to verify data integrity.
Including the checksum in the Metadata parameter does not help in verifying the integrity during the upload. The HeadObject operation retrieves metadata but does not validate checksums in the way required.