Cut ticketing platform cost with a gateway S3 endpoint and scheduled scaling

Answer Correct answers: A, E — Create a gateway VPC endpoint for S3 and replace the predictive scaling policy with scheduled scaling policies for known events.

An events company runs a ticketing platform on AWS. The company’s customers configure and schedule their events on the platform. The events result in large increases of traffic to the platform. The company knows the date and time of each customer’s events. The company runs the platform on an Amazon Elastic Container Service (Amazon ECS) cluster. The ECS cluster consists of Amazon EC2 On-Demand Instances that are in an Auto Scaling group. The Auto Scaling group uses a predictive scaling policy. The ECS cluster makes frequent requests to an Amazon S3 bucket to download ticket assets. The ECS cluster and the S3 bucket are in the same AWS Region and the same AWS account. Traffic between the ECS cluster and the S3 bucket flows across a NAT gateway. The company needs to optimize the cost of the platform without decreasing the platform's availability. Which combination of steps will meet these requirements? (Choose two.)

  1. Create a gateway VPC endpoint for the S3 bucket. Correct Answer
  2. Add another ECS capacity provider that uses an Auto Scaling group of Spot Instances. Configure the new capacity provider strategy to have the same weight as the existing capacity provider strategy.
  3. Create On-Demand Capacity Reservations for the applicable instance type for the time period of the scheduled scaling policies.
  4. Enable S3 Transfer Acceleration on the S3 bucket.
  5. Replace the predictive scaling policy with scheduled scaling policies for the scheduled events. Correct Answer

Community Votes

AE
100%

100% of anonymous learners picked answer AE. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

A gateway VPC endpoint for S3 removes both the NAT gateway data processing charge and the cross-AZ traffic for S3 requests, and because event schedules are already known, scheduled scaling policies size the capacity ahead of time instead of relying on a predictive policy that reacts to patterns.

An events ticketing platform runs on ECS over EC2 On-Demand instances in an Auto Scaling group with predictive scaling, and the cluster downloads ticket assets from an S3 bucket in the same Region through a NAT gateway. The dates and times of customer events are known in advance and availability must not decrease.

Adding a Spot capacity provider at the same weight as the existing On-Demand strategy. Spot instances can be reclaimed, so mixing them in without a base of On-Demand capacity can reduce availability during an event surge, which the requirement explicitly forbids.

Community Discussion (8 comments)

0b43291 👍 7
If you made it this far you will pass.. Good luck everyone! This is a great service.
wbedair 👍 5 Selected: AE
Options A and E will meet the requirements most cost-effectively by leveraging the predictability of the workload of known customer events to optimize scaling operations and reducing data transfer costs
itsjunukim 👍 1 Selected: AE
Tomorrow is the exam. To everyone who has made it this far, good luck and do your best!
AzureDP900 👍 1
A,E By creating a gateway VPC endpoint for the S3 bucket (option A), you can reduce latency and improve performance by routing traffic directly through Amazon's network, rather than relying on the NAT gateway. And by replacing the predictive scaling policy with scheduled scaling policies for the scheduled events (option E), you can avoid scaling instances during low-traffic periods, which would reduce costs and prevent unnecessary charges.
Chakanetsa 👍 1 Selected: AB
A. Create a gateway VPC endpoint for the S3 bucket: This will allow the ECS cluster to access the S3 bucket directly without the need for traffic to flow through the NAT gateway, reducing costs associated with NAT data transfer. B. Add another ECS capacity provider that uses an Auto Scaling group of Spot Instances: By introducing Spot Instances with the same weight as On-Demand Instances, the company can take advantage of the cost savings from Spot Instances while maintaining the ability to scale with On-Demand Instances when needed. These steps will reduce network traffic costs and take advantage of lower-cost compute options without compromising platform availability.
c22ddd8 👍 2 Selected: AE
Since it is scheduled event , E is correct ans
vip2 👍 2 Selected: AE
A: no charge for S3 access E: know details of date and time --- can scheduled for saving cost
kupo777 👍 3
A For S3 communication in the same region, the communication fee is waived by using the gateway VPC endpoint. B Availability is reduced when spot instances are used. C Using on-demand capacity reservation increases costs. D Using S3 Transfer Acceleration increases costs. E Scheduled scaling policies allow resources to be used according to events. The answers are A and E.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

The ECS cluster and the S3 bucket are in the same Region and account, so a gateway VPC endpoint for S3 lets the cluster reach S3 over the AWS network instead of through the NAT gateway. That eliminates the NAT gateway hourly and data processing charges on every asset download as well as any cross-Availability-Zone data transfer, and it reduces request latency, so availability is not reduced. Separately, the company knows the exact date and time of every customer event, so scheduled scaling policies can provision capacity ahead of each known surge, which is more accurate and cheaper than a predictive policy that must learn a pattern. Both changes are purely additive and neither reduces availability.

Why the Other Options Are Wrong

B: Adding a Spot capacity provider with the same weight as the On-Demand strategy means a large share of the capacity can be reclaimed during a peak event, so the platform could lose availability precisely when it is most needed. C: On-Demand Capacity Reservations commit to paying for a specific instance family over a window; for short, predictable, recurring event spikes they are more expensive than scheduled scaling and they do not address the NAT gateway cost. D: S3 Transfer Acceleration optimizes uploads and downloads over long distances to end users, and it adds a per-GB charge, so it is the wrong tool for intra-Region traffic that should simply bypass the NAT gateway.

Community Comment Notes

The community voted 91 to 0 for A and E, and the reasoning was that both steps attack the two named cost drivers directly, the NAT gateway path for the asset downloads and the reactive predictive policy for the known event schedule. One commenter paused on the last option, which is consistent with the same reasoning applied to the NAT gateway, but the vote and the reasoning both land on the gateway endpoint plus scheduled scaling pair.

Official Reference

Related Analysis

Practice All SAP-C02 Questions

Access 85 questions with complete answers and detailed explanations.

View Full SAP-C02 Practice Test →

← Back to SAP-C02 Study Guide