Amazon Exam DVA-C02 Topic 6 Question 22 Discussion

Actual exam question for Amazon's DVA-C02 exam

Question #: 22
Topic #: 6

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 Clay at Mar 16, 2024, 09:30 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Shenika

4 months ago

I think option C could also be worth considering. Performing a parallel scan operation might be a good solution for improving query performance.

upvoted 0 times

...

Samira

4 months ago

But wouldn't configuring the application to retry requests also be beneficial in ensuring faster performance?

upvoted 0 times

...

Jeffrey

4 months ago

I'm leaning towards option A. Increasing the page size for each request might help improve query performance.

upvoted 0 times

...

Madalyn

4 months ago

I disagree, I believe option D is the best choice. Turning on read capacity auto scaling can help with increased performance.

upvoted 0 times

...

Samira

5 months ago

I think option B could work because creating a global secondary index might help speed up the queries.

upvoted 0 times

...

Sol

5 months ago

Hmm, I see your point. But what about option D? Turning on read capacity auto scaling seems like a scalable solution as well.

upvoted 0 times

...

Gussie

5 months ago

I agree with Stacey, setting the query attribute as the partition key in a GSI could definitely help in improving query performance.

upvoted 0 times

...

Stacey

6 months ago

I disagree, I believe creating a global secondary index like option B would be more efficient in speeding up the queries.

upvoted 0 times

...

Sol

6 months ago

I think option A could work, by increasing the page size and configuring retries for requests that exceed throughput.

upvoted 0 times

...

Merrilee

7 months ago

Haha, I love how these DynamoDB questions always involve some kind of performance issue. It's like the AWS exam writers are just trying to keep us on our toes, you know? But yeah, I think the GSI is the way to go here. It's a classic DynamoDB solution for this kind of problem.

upvoted 0 times

...

Kattie

7 months ago

I'm not so sure about the GSI option. Isn't that going to cost more in terms of provisioned throughput? And what if the queries change in the future, then we'd have to update the index. I'm kind of leaning towards the auto-scaling option - that seems like a more hands-off and potentially cheaper solution.

upvoted 0 times

...

Rosann

7 months ago

I agree, the GSI option does seem like the best choice here. The partition key will allow for fast lookups, and it won't require any changes to the application code. Plus, it's a more scalable solution than just increasing the page size or doing a parallel scan.

upvoted 0 times

...

Adela

7 months ago

Hmm, this is an interesting question. The slow queries due to the non-key attributes are definitely a concern, especially with the expected increase in data. I'm leaning towards option B - creating a global secondary index (GSI) with the query attribute as the partition key. That seems like the most straightforward way to improve query performance.

upvoted 0 times

Elly

7 months ago

I'm convinced. Option B it is for optimizing the queries that involve non-key attributes in the DynamoDB table.

upvoted 0 times

...

Filiberto

7 months ago

Yeah, that's a good point. Option B seems like the most targeted approach to improving query performance, especially considering the expected increase in data volume.

upvoted 0 times

...

Shantell

7 months ago

It might work, but creating a global secondary index specifically targeting the query attribute seems more direct and effective. That's why B stands out to me as the better choice.

upvoted 0 times

...

Dalene

7 months ago

But wouldn't increasing the page size for each request and configuring the application to retry requests also be a valid approach? That's option A, right?

upvoted 0 times

...

Aracelis

7 months ago

I agree, B seems like the appropriate solution here. It will definitely help with the slow queries involving non-key attributes.

upvoted 0 times

...

Karma

7 months ago

I think B makes the most sense. Creating a global secondary index with the query attribute as the partition key should help improve query performance.

upvoted 0 times

...