A company runs a highly available data collection application on Amazon EC2 in the eu-north-1 Region. The application collects data from end-user devices and writes records to an Amazon Kinesis data…

Question

Options

• AIn each of the two new Regions, set up the Lambda functions to run in a VPC. Set up an S3
• BTurn on S3 Transfer Acceleration on the S3 bucket in eu-north-1. Change the application to use
• CCreate an S3 bucket in each of the two new Regions. Set the application in each new Region to
• DIncrease the memory requirements of the Lambda functions to ensure that they have multiple

• A
  4% (1)
• B
  64% (18)
• C
  11% (3)
• D
  21% (6)

Explanation

S3 Transfer Acceleration uses Amazon CloudFront's globally distributed edge locations to route data over AWS's optimized backbone network rather than the public internet, which dramatically reduces latency for cross-region uploads - exactly the problem here where sa-east-1 and ap-northeast-1 must write to a bucket in eu-north-1.

Why the distractors fail:

• A is wrong because placing Lambda in a VPC with an S3 gateway endpoint only optimizes traffic within a region - it does nothing to accelerate cross-region transfers to eu-north-1.
• C would reduce lag by writing locally first, but it introduces complexity (replication, consistency delays) and doesn't directly address the transfer bottleneck; it also contradicts the centralization requirement if not paired with replication.
• D is wrong because increasing Lambda memory affects compute speed and concurrency, not network transfer latency between regions.

Memory tip: Think of S3 Transfer Acceleration as "express lanes via CloudFront edge nodes" - whenever a question involves slow uploads from distant/global clients to a single S3 bucket, Transfer Acceleration is almost always the answer. The key signal phrase is cross-region or global users writing to one bucket.

No community discussion yet for this question.