As a Sysops Administrator, you are uploading files from your data center onto AWS Glacier. The total amount of data in your data center is approximately 70 TB. But when you upload files, you can see the files` names are not the same as those that have been uploaded. For example, you upload a file demo.txt, and then in Glacier, you can see the archive ID as 
“TJgHcrOSfAkV6hdPqOATYfp_0ZaxL1pIBOc02iZ0gDPMr2ig-nhwd_PafstsdIf6HSrjHnP-3p6LCJClYytFT_CBhT9CwNxbRaM5MetS3I-GqwxI3Y8QtgbJbhEQPs0mJ3KExample”
What can be done to ensure that you can have the same file in Glacier ensuring minimal impact to cost? Choose 2 answers from the options given below.

Answer options:

A.Create a PostGreSQL database and have an entry for files names in Glacier against the action file names.
B.Upload the files directly to glacier using the AWS Console.
C.Use the AWS Snowball Edge device to upload the files to S3 and then move it to Glacier storage for archival using Lifecycle rules.
D.Upload the files directly to Glacier through Direct Connect.
E.Upload the files in Amazon S3 Infrequent Access and then use lifecycle policies to move them to Glacier.

Correct Answers: C and E
You can upload the files to Amazon S3 either directly or by using a Snowball Edge device. The Lifecycle policies can then be used to transition the storage class of the object to Glacier. So here, the file names will be preserved.
Option A is invalid because this would not be a cost-effective and easy maintenance option.
Option B is invalid because you cannot upload files directly to Glacier.
Option D is invalid because Direct Connect does not resolve the issue mentioned in the question.
For more information on uploading an archive, please refer to the below URL-
https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-an-archive.html