An analyst needs to inspect the contents of an object currently stored in the S3 Glacier Deep Archive storage class. They issue a RestoreObject request specifying a 10-day restoration period. Once the restore completes, what is true about the object during and after that 10-day window?
- The object's storage class permanently changes to S3 Standard once the restore completes
- A temporary, readable copy becomes available for 10 days while the object itself remains in the Deep Archive storage class; after 10 days, the temporary copy is removed
- The restore permanently deletes the archived original, replacing it with only the temporary copy
- No temporary copy is created; the RestoreObject request instead grants direct real-time reads against the archived data for 10 days
Why B? And why not the others?
Correct answer: B. A temporary, readable copy becomes available for 10 days while the object itself remains in the Deep Archive storage class; after 10 days, the temporary copy is removed
AWS documentation on restoring archived objects explains that objects in the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage classes are not accessible in real time, so to read one you must restore a temporary copy of the object into the bucket for a specified number of days; unless the analyst separately copies that restored data into a new object with a different storage class, the original object itself remains stored in Deep Archive throughout and after the process, and the temporary copy is automatically removed once the specified restoration period, 10 days here, expires. The option claiming the object's storage class permanently changes to Standard is wrong because a restore operation never changes the storage class of the original archived object; the restored data is only a temporary, separate accessible copy, and a permanent class change would require an explicit copy operation. The option describing the original as permanently deleted and replaced is wrong because restoring never removes the archived original; documentation notes the requester is billed for both the ongoing archived storage and the temporary restored copy simultaneously, which would make no sense if the archived original had been deleted. The option claiming there is no temporary copy and instead direct real-time reads occur against the archived data misdescribes the entire mechanism: Glacier Deep Archive data is never read in place, which is exactly why a restore operation exists to stage a temporary, ordinarily accessible copy elsewhere in the bucket for the requested duration.
Source: AWS S3 documentation: Restoring an archived object — a temporary copy is created for a specified number of days while the original remains archived, and expires automatically