Question : Being a HadoopExam.com AWS Developer you have enabled versioning of a bucket. Is it possible to store all the versions of the objects in RRS and the current version of the object in S3? 1. Yes, only if the life cycle rule is set 2. Yes 3. Access Mostly Uused Products by 50000+ Subscribers 4. No
Explanation: It is not possible to change the storage class of a specific version of an object in Amazon S3. When the user copies it, Amazon S3 gives it a new version ID.
Question : Being a HadoopExam.com AWS Developer you are exploring options to work with AWS S. Which of the below mentioned statements does not help user with respect to AWS S3? 1. The user can store a php file in AWS S3 2. The user can create a bucket with the same name as the user domain on S3 3. Access Mostly Uused Products by 50000+ Subscribers 4. The user can host a dynamic website with Cloudfront
Explanation: A user can create an S3 bucket which maps to his domain name as well as store a static website on S3. The user can upload a php file to S3, but it will not be processed as S3 cannot host a dynamic website.
Question : Being a HadoopExam.com AWS Developer you have enabled a static website with AWS S. The user already has index.html as a part of this bucket. What difference will be there for the user while using this hosting feature? 1. Nothing. the user can always access index.html without the hosting feature 2. It helps the user to save some costs as it will not consider the I/O charges if website hosting is enabled 3. Access Mostly Uused Products by 50000+ Subscribers 4. The user can directly access the website using the region specific endpoint
Explanation: To host a static website, the user needs to configure an Amazon S3 bucket for website hosting and then upload the website contents to the bucket. The website is then available at the region-specific website endpoint of the bucket. If the user has an index.html object as part of the bucket, the user can always host it without the website hosting feature. However, it will require an absolute URL of the object. In this case the user can access the whole bucket as a website and need not refer individual objects separately.
1. US - STANDARD uses eventual consistency and it can take time for an object to be readable in a bucket. 2. Objects in Amazon S3 do not become visible until they are replicated to a second region. 3. Access Mostly Uused Products by 50000+ Subscribers 4. You exceeded the bucket object limit and once this limit is raised the object will be visible.
Ans : 4 Exp : Protecting Data Using Server-Side Encryption with Amazon S3-Managed Encryption Keys (SSE-S3)
Server-side encryption is about protecting data at rest. Server-side encryption with Amazon S3-managed encryption keys (SSE-S3) employs strong multi-factor encryption. Amazon S3 encrypts each object with a unique key. As an additional safeguard, it encrypts the key itself with a master key that it regularly rotates. Amazon S3 server-side encryption uses one of the strongest block ciphers available, 256-bit Advanced Encryption Standard (AES-256), to encrypt your data.
Amazon S3 supports bucket policies that you can use if you require server-side encryption for all objects that are stored in your bucket. For example, the following bucket policy denies upload object (s3:PutObject) permission to everyone if the request does not include the x-amz-server-side-encryption header requesting server-side encryption.
{ "Version":"2012-10-17", "Id":"PutObjPolicy", "Statement":[{ "Sid":"DenyUnEncryptedObjectUploads", "Effect":"Deny", "Principal":"*", "Action":"s3:PutObject", "Resource":"arn:aws:s3:::YourBucket/*", "Condition":{ "StringNotEquals":{ "s3:x-amz-server-side-encryption":"AES256" } } } ] } Server-side encryption encrypts only the object data. Any object metadata is not encrypted.
Question : Select correct statement about DynamoDB ?
1. store backed instances can be stopped and restarted 2. Auto scaling requires using Amazon EBS - backed instances 3. Access Mostly Uused Products by 50000+ Subscribers 4. Virtual Private Cloud requires EBS backed instances
1. Use CloudFront distributions for static content. 2. Remove public read access and use signed URLs with expiry dates. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Store photos on an EBS volume of the web server.
1. API for this object Contact support to increase your object size limit 2. API for this object Use the large object upload 3. Access Mostly Uused Products by 50000+ Subscribers 4. None, Simple Storage Service objects are limited to 5 GB