Question-12: You are working with a matrimonial website named HighMariage.com in which users can like or dislike the profiles and if users are having paid subscription then he can see the contact detail of other users. And can establish communications with each other using chat application, as well as can send email as well. Each user can create up to 5 albums which can have images in it and user can make it visible publicly or may not. Each user data is stored in a DynamoDB table named ProfileDataTable there are on daily basis 1000’s of profiles are created however millions of views are happening. You need to implement Auto scaling with the DynamoDB table which all things you can do and also select other correct options.

1. You would be storing the images in the same ProfileDataTable so that it makes your website highly performant while viewing.
2. It would publish consumed capacity metrics to AWS CloudTrail
3. If the consumed capacity exceeds your target utilizations (or below the target) for a specific length of time, AWS send an alert using SQS.
4. Get the Latest AWS Certification Questions & Answer based on recent syllabus from this link
5. If the consumed capacity exceeds your target utilizations (or below the target) for a specific length of time, AWS CloudWatch triggers an Alarm using SQS
6. Get the Latest AWS Certification Questions & Answer based on recent syllabus from this link
7. Publishes Consumed Capacity metrics at AWS CloudWatch

Ans : D, F,G

Exp : If you read the entire question it is Get the latest AWS Training, Certification Preparation Material, Books & Interview questions  more about asking the question regarding the working with specific table in DynamoDB, how being a managed service it can help you in reducing the cost. And you should get notified with various events.

Its about the dynamically accessing the managed resources from the DynamoDB table. Suppose during DayTime your application need more resources and in night time it require less resources and DynamoDB table should help you in getting such resources and cost you less.

AWS DynamoDB provides auto scaling which uses the AWS application Auto Scaling service to dynamically adjust the provisioned throughput capacity on your behalf. Here, on your behalf is important aspect, because DynamoDB is a managed service and you would not be doing administration tasks your own. And based on the traffic received DynamoDB table would do the performance. You can define auto scaling on both Table as well as any Global Secondary indexes which you have created.

What you have to do is create an auto scaling policy for the table or a global secondary index. And also you have to make sure to define whether you need auto scaling for the read or write or for both. As in the given question we need read scaling because that varies a lot.

In the scaling policy we would be defining the target utilization which defines the percentage of consumed provisioned throughput at a point in time and can set up upto between 20 and 90 percent. These are the steps you need to follow for auto scaling of the DynamoDB

1. You create an Application Auto Scaling policy for your DynamoDB table named ProfileDataTable.
2. DynamoDB publishes consumed capacity metrics to Amazon CloudWatch (Remember its CloudWatch). CloudTrail is more for logging perspective and for Alarm you should use Cloudwatch.
3. If the table's consumed capacity exceeds your target utilization (or falls below the target) for a specific length of time, Amazon CloudWatch triggers an alarm. You can view the alarm on the console and receive notifications using Amazon Simple Notification Service (Amazon SNS). Always you want to create a Notification then use the SNS and not the SQS.
4. The CloudWatch alarm invokes Application Auto Scaling to evaluate your scaling policy. Hence, whatever you defined in the scaling policy that would be considered during auto scalaing.
5. Application Auto Scaling issues an UpdateTable request to adjust your table's provisioned throughput.
6. DynamoDB processes the UpdateTable request, dynamically increasing (or decreasing) the table's provisioned throughput capacity so that it approaches your target utilization.