Amazon Exam DVA-C02 Topic 7 Question 32 Discussion

Actual exam question for Amazon's DVA-C02 exam

Question #: 32
Topic #: 7

A company runs an application on AWS The application stores data in an Amazon DynamoDB table Some queries are taking a long time to run These slow queries involve an attribute that is not the table's partition key or sort key

The amount of data that the application stores in the DynamoDB table is expected to increase significantly. A developer must increase the performance of the queries.

Which solution will meet these requirements'?

AIncrease the page size for each request by setting the Limit parameter to be higher than the default value Configure the application to retry any request that exceeds the provisioned throughput.

BCreate a global secondary index (GSI). Set query attribute to be the partition key of the index

CPerform a parallel scan operation by issuing individual scan requests in the parameters specify the segment for the scan requests and the total number of segments for the parallel scan.

DTurn on read capacity auto scaling for the DynamoDB table. Increase the maximum read capacity units (RCUs).

Show Suggested Answer

Suggested Answer: B

Global Secondary Index (GSI):GSIs enable alternative query patterns on a DynamoDB table by using different partition and sort keys.

Addressing Query Bottleneck:By making the slow-query attribute the GSI's partition key, you optimize queries on that attribute.

Scalability:GSIs automatically scale to handle increasing data volumes.

Amazon DynamoDB Global Secondary Indexes:https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html

by Devon at Jul 15, 2024, 05:52 AM

Limited Time Offer

25%

Off

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Precious

4 months ago

Honestly, I'm just hoping the right answer doesn't involve any magic spells or unicorn dust. Let's stick to the practical solutions here.

upvoted 0 times

...

Renea

4 months ago

Haha, Viola! That's a good one. But you know, Option D might work if the team doesn't mind dealing with the potential cost implications of auto scaling.

upvoted 0 times

...

4 months ago

I disagree, Aleta. The application's data is expected to grow significantly, so Option A might not be scalable in the long run. Option B seems like the best choice here.

upvoted 0 times

Tracie

3 months ago

I agree with you. Creating a global secondary index (GSI) with the query attribute as the partition key seems like the most suitable solution for improving query performance.

upvoted 0 times

...

Maryann

3 months ago

I think Option B is the way to go. It will help with the slow queries involving the attribute that is not the table's partition key or sort key.

upvoted 0 times

...

Aleta

4 months ago

I'm not sure about that, Aron. Increasing the page size and retrying requests that exceed the provisioned throughput (Option A) could also be a good solution.

upvoted 0 times

...

5 months ago

I think option B is the best solution.

upvoted 0 times

...