Question : You have uploaded your blogs images to Amazon Glacier and after few days you want to view Glacier images from the AWS console. Which information will not be available from the console? 1. Last date of the inventory update 2. Size of the vault as per the last inventory 3. Access Mostly Uused Products by 50000+ Subscribers 4. Number of archives as of the last inventory
Correct Answer : Get Lastest Questions and Answer : Explanation: An archive is any object, such as a photo, video, or document, that you store in a vault. It is a base unit of storage in Amazon Glacier. Each archive has a unique ID and an optional description. When you upload an archive, Amazon Glacier returns a response that includes an archive ID. This archive ID is unique in the region in which the archive is stored. The following is an example archive ID. TJgHcrOSfAkV6hdPqOATYfp_0ZaxL1pIBOc02iZ0gDPMr2ig-nhwd_PafstsdIf6HSrjHnP-3p6LCJClYytFT_CBhT9CwNxbRaM5MetS3I-GqwxI3Y8QtgbJbhEQPs0mJ3KExample
Archive IDs are 138 bytes long. When you upload an archive, you can provide an optional description. You can retrieve an archive using its ID but not its description. Important : Amazon Glacier provides a management console. You can use the console to create and delete vaults. However, all other interactions with Amazon Glacier require that you use the AWS Command Line Interface (CLI) or write code. For example, to upload data, such as photos, videos, and other documents, you must either use the AWS CLI or write code to make requests, using either the REST API directly or by using the AWS SDKs.If a user is trying to access Glacier from the AWS console, the user can view the number of archives, last date of inventory update, list of vaults as well as the number of archives per vault. The console does not show the list of archives. Uploading an Archive in Amazon Glacier
You can upload an archive in a single operation or upload it in parts. The API call you use to upload an archive in parts is referred as Multipart Upload. For more information, see Uploading an Archive in Amazon Glacier. Important : Amazon Glacier provides a management console. You can use the console to create and delete vaults. However, all other interactions with Amazon Glacier require that you use the AWS Command Line Interface (CLI) or write code. For example, to upload data, such as photos, videos, and other documents, you must either use the AWS CLI or write code to make requests, using either the REST API directly or by using the AWS SDKs. For more information about using Amazon Glacier with the AWS CLI, go to AWS CLI Reference for Amazon Glacier. To install the AWS CLI, go to AWS Command Line Interface.
Downloading an Archive in Amazon Glacier : Downloading an archive is an asynchronous operation. You must first initiate a job to download a specific archive. After receiving the job request, Amazon Glacier prepares your archive for download. After the job completes, you can download your archive data. Because of the asynchronous nature of the job, you can request Amazon Glacier to send a notification to an Amazon Simple Notification Service (Amazon SNS) topic when the job completes. You can specify an SNS topic for each individual job request or configure your vault to send a notification when specific events occur. For more information about downloading an archive, see Downloading an Archive in Amazon Glacier. Deleting an Archive in Amazon Glacier Amazon Glacier provides API call you can use to delete one archive at a time. For more information, see Deleting an Archive in Amazon Glacier. Updating an Archive in Amazon Glacier
After you upload an archive, you cannot update its content or its description. The only way you can update the archive content or its description is by deleting the archive and uploading another archive. Note that each time you upload an archive, Amazon Glacier returns to you a unique archive ID. Maintaining Client-Side Archive Metadata, Except for the optional archive description, Amazon Glacier does not support any additional metadata for the archives. When you upload an archive Amazon Glacier assigns an ID, an opaque sequence of characters, from which you cannot infer any meaning about the archive. You might maintain metadata about the archives on the client-side. The metadata can include archive name and some other meaningful information about the archive. Note : If you are an Amazon Simple Storage Service (Amazon S3) customer, you know that when you upload an object to a bucket, you can assign the object an object key such as MyDocument.txt or SomePhoto.jpg. In Amazon Glacier, you cannot assign a key name to the archives you upload. If you maintain client-side archive metadata, note that Amazon Glacier maintains a vault inventory that includes archive IDs and any descriptions you provided during the archive upload. You might occasionally download the vault inventory to reconcile any issues in your client-side database you maintain for the archive metadata. However, Amazon Glacier takes vault inventory approximately daily. When you request a vault inventory, Amazon Glacier returns the last inventory it prepared, a point in time snapshot.
Question : Being a HadoopExam blog developer you have lot of Images to analyze and once the analysis completed you decided to upload these images as archives to Glacier. Befor uploading you want to find key Glacier resources. Which of the below is not a Glacier resource? 1. Notification configuration 2. Archive 3. Access Mostly Uused Products by 50000+ Subscribers 4. Job
Correct Answer : Get Lastest Questions and Answer : Explanation: AWS Glacier has four resources. Vault and Archives are core data model concepts. Job is required to initiate download of archive. The notification configuration is required to send user notification when archive is available for download. The Amazon Glacier data model core concepts include vaults and archives. Amazon Glacier is a REST-based web service. In terms of REST, vaults and archives are the resources. In addition, the Amazon Glacier data model includes job and notification-configuration resources. These resources complement the core resources. Vault
In Amazon Glacier, a vault is a container for storing archives. When you create a vault, you specify a name and select an AWS region where you want to create the vault. Each vault resource has a unique address. Archive An archive can be any data such as a photo, video, or document and is a base unit of storage in Amazon Glacier. Each archive has a unique ID and an optional description. Archive IDs are unique within a vault. Note that you can only specify the optional description during the upload of an archive. Amazon Glacier assigns the archive an ID, which is unique in the AWS region in which it is stored. Each archive has a unique address. Job : Retrieving an archive and vault inventory (list of archives) are asynchronous operations in Amazon Glacier in which you first initiate a job, and then download the job output after Amazon Glacier completes the job. With Amazon Glacier, your data retrieval requests are queued and most jobs take about four hours to complete.
Note : Amazon Glacier offers a cold storage data archival solution. If your application needs a storage solution that requires real-time data retrieval, you might consider using Amazon S3. For more information, see Amazon Simple Storage Service (Amazon S3).
To initiate a vault inventory job, you provide a vault name. The archive retrieval job requires both the vault name where the archive resides and the archive ID you wish to download. You can also provide an optional job description when you initiate these jobs. These descriptions can help you in identifying jobs.
Both the archive retrieval and vault inventory jobs are associated with a vault. A vault can have multiple jobs in progress at any point in time. When you send a job request (initiate a job), Amazon Glacier returns to you a job ID to track the job. Notification Configuration : Because jobs take time to complete, Amazon Glacier supports a notification mechanism to notify you when a job is complete. You can configure a vault to send notification to an Amazon Simple Notification Service (Amazon SNS) topic when jobs complete. You can specify one SNS topic per vault in the notification configuration. Amazon Glacier stores the notification configuration as a JSON document.
Question : You are planning to host MS SQL on an EBS volume. And you decided to use the AWS RDS. What advantages will you have if he uses RDS in comparison to an EBS based DB? 1. Better throughput with PIOPS 2. High availability with multi AZs 3. Access Mostly Uused Products by 50000+ Subscribers 4. MS SQL is not supported with RDS
Explanation: By default and at no additional charge, Amazon RDS enables automated backups of your DB Instance with a 1 day retention period. Free backup storage is limited to the size of your provisioned database and only applies to active DB Instances. For example, if you have 10GB-months of provisioned database storage, we will provide at most 10GB-months of backup storage at no additional charge. If you would like to extend your backup retention period beyond one day, you can do so using the CreateDBInstance API (when creating a new DB Instance) or ModifyDBInstance API (for an existing DB Instance). You can use these APIs to change the RetentionPeriod parameter from 1 to the desired number of days. Comparing with on-premises or EC2 based MS SQL, RDS provides an automated backup feature. PIOPS is available with both RDS and EBS. However, HA is not available with MS SQL.