DVA-C02 · Question #646
A company hosts a multitenancy application that is becoming more popular. The company is setting up an Amazon CloudFront distribution for the application. When the company begins to test the CloudFron
The correct answer is A. Configure the application to send a custom header named TenantID that includes a unique tenant. Sending a custom TenantID header and configuring CloudFront to cache based on that header allows the application to serve tenant-specific content correctly with minimal code changes. It leverages built-in CloudFront capabilities and avoids complex development, achieving the goal
Question
A company hosts a multitenancy application that is becoming more popular. The company is setting up an Amazon CloudFront distribution for the application. When the company begins to test the CloudFront distribution, some tenants see incorrect images for the tenant. The company needs to configure the application to cache the correct image for each tenant. Which solution will meet this requirement with the LEAST development effort?
Options
- AConfigure the application to send a custom header named TenantID that includes a unique tenant
- BCreate a new database table that maps images to tenant IDs. Configure the application to serve
- CConfigure the application to send a cookie header that includes a unique tenant identifier with
- DWrite a Lambda@Edge function to look up and rewrite image paths based on each tenant.
How the community answered
(32 responses)- A78% (25)
- B6% (2)
- C3% (1)
- D13% (4)
Explanation
Sending a custom TenantID header and configuring CloudFront to cache based on that header allows the application to serve tenant-specific content correctly with minimal code changes. It leverages built-in CloudFront capabilities and avoids complex development, achieving the goal with the least effort.
Community Discussion
No community discussion yet for this question.