Question : A user has enabled versioning on an S bucket. The user is using server side encryption for data at Rest. If the user is supplying his own keys for encryption SSE-C., which of the below mentioned statements is true? 1. The user should use the same encryption key for all versions of the same object 2. It is possible to have different encryption keys for different versions of the same object 3. Access Mostly Uused Products by 50000+ Subscribers 4. The SSE-C does not work when versioning is enabled
Explanation: AWS S3 supports client side or server side encryption to encrypt all data at rest. The server side encryption can either have the S3 supplied AES-256 encryption key or the user can send the key along with each API call to supply his own encryption key (SSE-C.. If the bucket is versioning- enabled, each object version uploaded by the user using the SSE-C feature can have its own encryption key. The user is responsible for tracking which encryption key was used for which object's version
Question : A user has created a VPC with CIDR .../. The user has created one subnet with CIDR .../ in this VPC. The user is trying to create another subnet with the same VPC for CIDR 20.0.0.1/24. What will happen in this scenario? 1. The VPC will modify the first subnet CIDR automatically to allow the second subnet IP range 2. It is not possible to create a subnet with the same CIDR as VPC 3. Access Mostly Uused Products by 50000+ Subscribers 4. It will throw a CIDR overlaps error
Explanation: A Virtual Private Cloud VPC. is a virtual network dedicated to the user's AWS account. A user can create a subnet with VPC and launch instances inside that subnet. The user can create a subnet with the same size of VPC. However, he cannot create any other subnet since the CIDR of the second subnet will conflict with the first subnet.
Question : A user has launched an RDS MySQL DB with the Multi AZ feature. The user has scheduled the scaling of instance storage during maintenance window. What is the correct order of events during maintenance window? 1. Perform maintenance on standby 2. Promote standby to primary 3. Access Mostly Uused Products by 50000+ Subscribers 4. Promote original master back as primary
Exp: Running MySQL on the RDS DB instance as a Multi-AZ deployment can help the user reduce the impact of a maintenance event, as the Amazon will conduct maintenance by following the steps in the below mentioned order: Perform maintenance on standby Promote standby to primary Perform maintenance on original primary, which becomes the new standby.
1. AWS does not have sufficient capacity in that availability zone 2. AWS zone mapping is changed for that user account 3. Access Mostly Uused Products by 50000+ Subscribers 4. The user account has reached the maximum EC2 instance limit
1. The AWS VPC will automatically create a NAT instance with the micro size 2. VPC bounds the main route table with a private subnet and a custom route table with a public subnet 3. Access Mostly Uused Products by 50000+ Subscribers 4. VPC bounds the main route table with a public subnet and a custom route table with a private subnet
1. Define the group policy and add a condition which allows the access based on the IAM name 2. Create a DynamoDB table with the same name as the IAM user name and define the policy rule which grants access based on the DynamoDB ARN using a variable 3. Access Mostly Uused Products by 50000+ Subscribers 4. It is not possible to have a group level policy which allows different IAM users to different DynamoDB Tables
1. By default ELB will select the first version of the security policy 2. By default ELB will select the latest version of the policy 3. Access Mostly Uused Products by 50000+ Subscribers 4. It is not required to have a security policy since SSL is already installed