MENU
A financial services company loaded millions of historical stock trades into an Amazon DynamoDB table. The table uses on-demand capacity mode. Once each day at midnight, a few million new records are loaded into the table. Application read activity against the table happens in bursts throughout the day. and a limited set of keys are repeatedly looked up. The company needs to reduce costs associated with DynamoDB.
Which strategy should a solutions architect recommend to meet this requirement?
Suggested Answer: A
Get Premium SAP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
it will use the ALB to handle the unpredictable bursts of traffic and route it to the SQS queue. The SQS queue will act as a buffer to store incoming data temporarily and the container running in Amazon ECS with the Fargate launch type will process messages in the queue. This approach will ensure that all data is processed and prevent data loss.
33 comments · newest first
SH
Shawnta
11 months ago
Not sure about DAX, it adds complexity.
IN
India
12 months ago
Provisioned capacity is a solid choice here.
HE
Herminia
12 months ago
Surprised they didn’t mention caching first!
RE
Refugia
1 year ago
I think option C makes more sense for cost savings.
AR
Art
1 year ago
DAX can really speed up reads!
LI
Lisbeth
1 year ago
I feel like combining DAX with provisioned capacity might be the right approach, but I’m not clear on how Savings Plans fit into the overall strategy.
NI
Nicolette
1 year ago
I practiced a similar question where switching to provisioned capacity saved costs, but I’m not entirely sure if we need auto scaling with that.
JU
Julianna
1 year ago
I think DAX could be a good choice for caching those repeated lookups, but I’m a bit confused about whether we should stick with on-demand or switch to provisioned capacity.
LO
Lon
1 year ago
I remember that using ElastiCache can help reduce read costs, but I'm not sure if it's the best option here since we have a lot of writes too.
ED
Eden
1 year ago
Hmm, this looks straightforward. I think the output will be 2 since the increment function increments the value by 1.
RO
Rodrigo
1 year ago
Honestly, I'm not totally sure. I thought merging was different from adding a new endpoint, so maybe A and C?
MA
Magda
1 year ago
Okay, let's see. The workstation is sluggish for one user but not others, and the admin has validated it's working normally. I'm leaning towards B or D.
VA
Valentin
1 year ago
Communicating IT risks to the business is also really important. They need to be aware of the risks to make informed decisions.
AN
Annmarie
1 year ago
I'm really unsure here; isn't a Cartesian product basically what you get from combining two sets? I keep mixing up the concepts of joins.
PA
Paris
1 year ago
Word cloud sounds familiar, but I remember it's more about visualizing keywords rather than focusing on specific short phrases.
RE
Remedios
1 year ago
D looks like the full package - DAX, provisioned capacity, and auto-scaling. It's like a Swiss Army knife for this DynamoDB problem.
MA
Malcolm
1 year ago
C is tempting, but I don't think provisioned capacity is the answer. Gotta take advantage of those DynamoDB features to optimize performance and cost.
AL
Alva
1 year ago
I'm going with B. DAX and auto-scaling sounds like the way to go here. Beats having to manually provision capacity and worry about those pesky Savings Plans.
WE
Wendell
1 year ago
I'm leaning towards B as well. DAX and auto-scaling seem like a good combination to reduce costs.
PO
Pok
1 year ago
Yeah, I think B is the most cost-effective choice here. No need to worry about manual capacity provisioning with auto-scaling.
MI
Michel
1 year ago
I agree, B does seem like the best option. DAX can definitely help with reducing costs and auto-scaling is convenient.
CA
Candida
1 year ago
Wait, so we need to reduce costs, but they're loading in millions of records daily? That's like trying to save money on your electricity bill while running a Bitcoin mining operation out of your basement!
MA
Marti
1 year ago
D) Deploy DynamoDB Accelerator (DAX). Use provisioned capacity mode. Configure DynamoDB auto scaling.
OC
Ocie
1 year ago
But wouldn't using provisioned capacity mode increase costs?
KI
Kimbery
1 year ago
C) Use provisioned capacity mode. Purchase Savings Plans in Cost Explorer.
CA
Carey
1 year ago
B) Deploy DynamoDB Accelerator (DAX). Configure DynamoDB auto scaling. Purchase Savings Plans in Cost Explorer
VI
Vicki
1 year ago
D: Yeah, combining DAX with provisioned capacity and auto scaling should help manage costs efficiently.
AL
Alishia
1 year ago
C: D) Deploy DynamoDB Accelerator (DAX). Use provisioned capacity mode. Configure DynamoDB auto scaling.
AR
Arlette
1 year ago
B: That sounds like a good plan to optimize costs and performance.
RO
Rory
1 year ago
A: B) Deploy DynamoDB Accelerator (DAX). Configure DynamoDB auto scaling. Purchase Savings Plans in Cost Explorer
LA
Lashawn
2 years ago
I'm not sure about option C. Provisioned capacity may not be cost-effective for this scenario with fluctuating read activity.
EV
Eva
2 years ago
I agree with Tom. Using DAX and auto scaling can optimize costs while ensuring performance.
TO
Tom
2 years ago
I think option B is the best choice. DAX can help with read activity bursts and auto scaling can adjust capacity based on demand.