Question : Being a HadoopExam.com AWS Developer you are launching an EC instance under the free usage tier from the AMI with a snapshot size of GB. How can you launch the instance under the free usage tier? 1. Launch a micro instance, but do not store the data of more than 30 GB on the EBS storage. 2. Launch a micro instance. 3. Access Mostly Uused Products by 50000+ Subscribers 4. It is not possible to have this instance under the free usage tier.
Explanation: When a user is launching an EC2 instance under a free usage tier, the user has to use a micro instance and within 30 GB of the EBS volume. Since the size of the AMI snapshot is 50 GB, it is not possible to have an instance with a size lesser than 50 GB. In this case the user cannot use the free usage tier since the user will incur EBS charges.
Question : Being a HadoopExam.com AWS Developer you are assigning a tag to an instance, which of the below mentioned options is not a valid tag key/value pair? 1. Key: "Name :aws" Value: "instance@aws" 2. Key : "name@aws" Value:"aws:instance" 3. Access Mostly Uused Products by 50000+ Subscribers 4. Key : "aws" Value:"aws"
Explanation: In Amazon Web Services, to help manage EC2 instances as well their usage in a better way, the user can tag the instances. The tags are metadata assigned by the user which consists of a key and value. The tag key cannot have a prefix as "aws:", although it can have only "aws".
Question : Being a HadoopExam.com AWS Developer you have configured a security group with EC-CLASSIC. Which of the below mentioned statements is true? 1. By default all inbound traffic is enabled and all outbound traffic is disabled 2. By default all inbound traffic is disabled and all outbound traffic is enabled 3. Access Mostly Uused Products by 50000+ Subscribers 4. By default all inbound and outbound traffic is disabled
1. Amazon RDS makes it easy to use replication 2. scale beyond the capacity constraints of a single database instance for read-heavy database workloads 3. Access Mostly Uused Products by 50000+ Subscribers 4. 1 and 3 5. 1,2 and 3
The following table explains how to calculate the provisioned throughput capacity that you need.
Capacity Units Required For How to Calculate Reads Number of item reads per second * 4 KB item size (If you use eventually consistent reads, you'll get twice as many reads per second.) Writes Number of item writes per second * 1 KB item size If your application's read or write requests exceed the provisioned throughput for a table, then those requests might be throttled. You can use the AWS Management Console to monitor your provisioned and actual throughput and to change your provisioned capacity in anticipation of traffic changes. Read Capacity Units If your items are smaller than 4 KB in size, each read capacity unit will give you one strongly consistent read per second, or two eventually consistent reads per second. You cannot group multiple items in a single read operation, even if the items together are 4 KB or smaller. For example, if your items are 3 KB and you want to read 80 items per second from your table, then you need to provision 80 (reads per second) * 1 (3 KB / 4 KB = 0.75, rounded up to the next whole number) = 80 read capacity units for strong consistency. For eventual consistency, you need to provision only 40 read capacity units.
If your items are larger than 4 KB, you will need to round up the item size to the next 4 KB boundary. For example, if your items are 6 KB and you want to do 100 strongly consistent reads per second, you need to provision 100 (reads per second) * 2 (6 KB / 4 KB = 1.5, rounded up to the next whole number) = 200 read capacity units. You can use the Query and Scan operations in DynamoDB to retrieve multiple consecutive items from a table or an index in a single request. With these operations, DynamoDB uses the cumulative size of the processed items to calculate provisioned throughput. For example, if a Query operation retrieves 100 items that are 1 KB each, the read capacity calculation is not (100 * 4 KB) = 100 read capacity units, as if those items were retrieved individually using GetItem or BatchGetItem. Instead, the total would be only 25 read capacity units ((100 * 1024 bytes) = 100 KB, which is then divided by 4 KB). For more information see Item Size Calculations.
Write Capacity Units : If your items are smaller than 1 KB in size, then each write capacity unit will give you 1 write per second. You cannot group multiple items in a single write operation, even if the items together are 1 KB or smaller. For example, if your items are 512 bytes and you want to write 100 items per second to your table, then you would need to provision 100 write capacity units.
If your items are larger than 1 KB in size, you will need to round the item size up to the next 1 KB boundary. For example, if your items are 1.5 KB and you want to do 10 writes per second, then you would need to provision 10 (writes per second) * 2 (1.5 KB rounded up to the next whole number) = 20 write capacity units.
Question :
Which of the functionality and tasks Amazon RDS manage on your behalf
1. provisioning the infrastructure capacity you request to installing the database software 2. performing backups and patching the database software that powers your DB Instance 3. Access Mostly Uused Products by 50000+ Subscribers 4. 1 and 3 5. 1,2 and 3
1. Messages will be delivered exactly once and messages will be delivered in First in, First out order 2. Messages will be delivered exactly once and message delivery order is indeterminate 3. Access Mostly Uused Products by 50000+ Subscribers 4. Messages will be delivered one or more times and message delivery order is indeterminate