Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon SAP-C02 Exam - Topic 3 Question 64 Discussion

Actual exam question for Amazon's SAP-C02 exam
Question #: 64
Topic #: 3
[All SAP-C02 Questions]

An EC2-based ticketing service pulls a frequently updated pricing file (stored in S3) on startup. Sometimes EC2s have stale pricing, causing charge issues.

Show Suggested Answer Hide Answer
Suggested Answer: C

Mountpoint for Amazon S3allows EC2 instances to directly access files in S3 as aPOSIX-compliant mount point, ensuring they always get the latest data without copying or syncing.

It's simple and cost-effective for read-heavy patterns.

Mountpoint for Amazon S3


by Slyvia at Jan 22, 2026, 02:28 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Shalon
4 days ago
EC2 instances can cache data, leading to stale pricing.
upvoted 0 times
...
Jin
10 days ago
What if we just let the customers decide the prices? No more stale data!
upvoted 0 times
...
Shanda
15 days ago
I'd paint a happy little cache on the EC2 to solve this problem.
upvoted 0 times
...
Izetta
20 days ago
Implementing a caching mechanism with TTL would help keep the pricing up-to-date.
upvoted 0 times
...
Penney
25 days ago
The pricing file should be cached on the EC2 instance to avoid stale data.
upvoted 0 times
...
Noe
1 month ago
I feel like we might need to implement a versioning system for the pricing file in S3 to avoid stale data, but I'm not entirely sure how that would work.
upvoted 0 times
...
Danica
1 month ago
I think we discussed using Lambda to refresh the pricing file on EC2 startup, but I can't recall the exact implementation details.
upvoted 0 times
...
Francoise
2 months ago
This sounds similar to a practice question about caching strategies. Should we consider using a cache invalidation strategy for the pricing file?
upvoted 0 times
...
Brunilda
2 months ago
I remember something about using S3 event notifications to trigger updates, but I'm not sure if that's the best approach here.
upvoted 0 times
...
Lamonica
2 months ago
This seems like a classic case of keeping cached data fresh. I'd experiment with different caching strategies, like using DynamoDB or ElastiCache to store the pricing data, and see if that helps avoid the staleness issue.
upvoted 0 times
...
Merilyn
2 months ago
I'm a little confused on the best approach here. Should I focus on the EC2 instances or the S3 file? I guess I'd start by understanding the current architecture and workflow in more detail.
upvoted 0 times
...
Mi
3 months ago
Okay, so the key is making sure the EC2 instances always have the latest pricing data. I'd look at setting up some kind of event-driven architecture, where the S3 file update triggers an update to the EC2 instances.
upvoted 0 times
...
Dottie
3 months ago
Hmm, this seems tricky. I'd want to dig into the EC2 startup process and see if there's a way to automatically refresh the pricing data on a regular schedule. Maybe some kind of cron job or scheduled Lambda function?
upvoted 0 times
...
Jess
3 months ago
I'd start by checking the S3 pricing file for any issues with the data or update frequency. Then I'd look at the EC2 instances and see if there's a way to cache the pricing info more effectively.
upvoted 0 times
...

Save Cancel