A company needs to design a solution to process videos that users upload to an Amazon S3 bucket. Each video file is approximately 1 GB in size and takes approximately 20 minutes to process. During peak hours, the company expects to process approximately 100 simultaneous uploads. The video file processing is stateless and can run in parallel as soon as the video files arrive in the S3 bucket.
Which solution will meet these requirements in the MOST cost-effective way?
The workload isstateless,parallel, and each job runs for about20 minutes, which makes Lambda a poor fit because Lambda has a maximum execution time of 15 minutes. AWS Fargate is a strong match for event-driven container workloads because it removes server management overhead, andFargate Spotlowers cost for interruption-tolerant processing. AWS also provides patterns for runningevent-driven workloads at scale with Fargate, and EventBridge can be used to trigger container tasks from S3-originated events. Compared with EKS or EC2 On-Demand, ECS on Fargate Spot is the most cost-effective managed container approach here.
============
A company currently stores 5 TB of data in on-premises block storage systems. The company's current storage solution provides limited space for additional data. The company runs applications on premises that must be able to retrieve frequently accessed data with low latency. The company requires a cloud-based storage solution.
Which solution will meet these requirements with the MOST operational efficiency?
The company needs a cloud-based storage solution for frequently accessed data with low latency, while retaining their current on-premises infrastructure for some data storage. AWS Storage Gateway'sVolume Gateway with cached volumesis the most appropriate solution for this scenario.
AWS Storage Gateway - Volume Gateway (Cached Volumes):
Volume Gateway with cached volumesallows you to store frequently accessed data in the AWS Cloud while keeping the most recently accessed data cached locally on-premises. This ensures low-latency access to active data while providing scalability for the rest of the data in the cloud.
The cached volume option stores the primary data in Amazon S3 but caches frequently accessed data locally, ensuring fast access. This configuration is well-suited for applications that require fast access to frequently used data but can tolerate cloud-based storage for the rest.
Since the company is facing limited on-premises storage, cached volumes provide an ideal solution, as they reduce the need for additional on-premises storage infrastructure.
Why Not the Other Options?:
Option A (S3 File Gateway): S3 File Gateway provides a file-based interface (SMB/NFS) for storing data directly in S3. While it is great for file storage, the company's need for block-level storage with iSCSI targets makes Volume Gateway a better fit.
Option C (Volume Gateway - Stored Volumes): Stored volumes keep all the data on-premises and asynchronously back up to AWS. This would not address the company's storage limitations since they would still need substantial on-premises storage.
Option D (Tape Gateway): Tape Gateway is designed for archiving and backup, not for frequently accessed low-latency data.
AWS Reference:
AWS Storage Gateway - Volume Gateway
A company wants to run a hybrid workload for data processing. The data needs to be accessed by on-premises applications for local data processing using an NFS protocol, and must also be accessible from the AWS Cloud for further analytics and batch processing.
Which solution will meet these requirements?
AWS Storage Gateway file gateway presents a file interface backed by Amazon S3 and supports NFS. This allows local applications to access data via NFS while also enabling cloud applications to use the data stored in S3 for analytics and processing, fulfilling both hybrid and cloud-native requirements.
Reference Extract:
'AWS Storage Gateway file gateway offers NFS and SMB access to data stored in Amazon S3, supporting hybrid workloads for local and cloud access.'
Source: AWS Certified Solutions Architect -- Official Study Guide, Hybrid and Storage Gateway section.
A news company that has reporters all over the world is hosting its broadcast system on AWS. The reporters send live broadcasts to the broadcast system. The reporters use software on their phones to send live streams through the Real Time Messaging Protocol (RTMP).
A solutions architect must design a solution that gives the reporters the ability to send the highest quality streams The solution must provide accelerated TCP connections back to the broadcast system.
What should the solutions architect use to meet these requirements?
AWS Global Accelerator: This service provides a global fixed entry point to your applications and optimizes the path to your application through the AWS global network, reducing latency and improving performance.
Accelerated TCP Connections:
Global Accelerator uses the AWS global network to route traffic to the nearest edge location, improving the performance and reliability of your live streams.
It provides static IP addresses that act as a fixed entry point to your application, simplifying DNS management.
High-Quality Streams:
By leveraging Global Accelerator, reporters can send live streams with the highest quality and low latency.
This service automatically reroutes traffic to the nearest available AWS Region, ensuring consistent performance even during traffic spikes or failures.
Operational Efficiency: Using Global Accelerator simplifies the network setup and provides an optimized path for live streams without the need for complex configurations, making it an efficient solution for real-time streaming applications.
AWS Global Accelerator
How Global Accelerator Works
A company's HTTP application is behind a Network Load Balancer (NLB). The NLB's target group is configured to use an Amazon EC2 Auto Scaling group with multiple EC2 instances that run the web service.
The company notices that the NLB is not detecting HTTP errors for the application. These errors require a manual restart of the EC2 instances that run the web service. The company needs to improve the application's availability without writing custom scripts or code.
What should a solutions architect do to meet these requirements?
A Network Load Balancer operates at Layer 4 (TCP/UDP/TLS) and is optimized for high performance and static IP use cases. While NLB target groups can perform health checks, they are typically oriented around basic reachability and do not provide the same application-layer (Layer 7) visibility as an Application Load Balancer (ALB). The problem statement says the NLB is ''not detecting HTTP errors,'' which indicates the health signal needs to be based on an HTTP endpoint that can reflect application correctness (for example, returning specific HTTP status codes).
Replacing the NLB with an ALB enables true HTTP/HTTPS health checks against a URL path, including interpretation of HTTP response codes. This is the cleanest managed approach to detect application-layer failure modes that still allow TCP connections but produce bad HTTP responses. Once the ALB detects targets as unhealthy, the target group health status can be used by an Auto Scaling group to take action. With appropriate health check configuration (and, commonly, using ELB health checks as a signal), Auto Scaling can replace unhealthy instances automatically, improving availability without custom scripts.
Option A is misleading: NLB does not provide the same HTTP-aware request routing and rich L7 features; even if an NLB health check is configured, it does not address the broader need for application-layer detection and remediation as directly as ALB. Option B violates the ''no custom scripts'' requirement. Option D reacts to UnhealthyHostCount, but if the NLB isn't marking hosts unhealthy for HTTP error cases, the metric won't reliably trigger replacement; it also still depends on the NLB's limited visibility into HTTP failures.
Therefore, C best meets the requirement by shifting to ALB for application-layer health checks and using Auto Scaling to replace unhealthy instances automatically.
Brian Parker
5 days agoCarol Davis
27 days agoCynthia Rogers
1 month agoRichard Robinson
2 months agoDorothy Flores
2 months agoEmily Morgan
2 months agoKimberly Young
2 months agoSandra Green
2 months agoSharon Phillips
2 months agoThomas Flores
1 month agoLindsey
3 months agoJannette
3 months agoAron
3 months agoAmmie
3 months agoGwen
4 months agoKeneth
4 months agoJunita
4 months agoFranklyn
4 months agoJanet
5 months agoSylvie
5 months agoTeri
5 months agoCordelia
5 months agoBelen
6 months agoEleonore
6 months agoNoel
6 months agoClement
6 months agoIra
7 months agoTayna
7 months agoCharlene
7 months agoJohna
7 months agoBelen
8 months agoHuey
8 months agoTrinidad
8 months agoJuliann
8 months agoErnest
9 months agoRoyce
9 months agoYoko
9 months agoKris
9 months agoAlishia
10 months agoMiesha
10 months agoBarb
12 months agoGussie
1 year agoEna
1 year agoBlondell
1 year agoGilbert
1 year agoPearlene
1 year agoJosue
1 year agoNakita
1 year agoLaurena
2 years agoVirgie
2 years agoRenea
2 years agoFloyd
2 years agoHan
2 years agoNarcisa
2 years agoJerry
2 years agoParis
2 years agoLamonica
2 years agoBette
2 years agoRoxane
2 years agoJesus
2 years agoJustine
2 years agoWilliam
2 years agoAbraham
2 years agoCyril
2 years agoSharee
2 years agoBrandon
2 years agoYuette
2 years agoPrecious
2 years agoAlease
2 years agoSimona
2 years agoRose
2 years agoCecilia
2 years ago