Home › Forums › AWS › AWS Certified Solutions Architect Associate › Timed Mode Set 2 – AWS Certified Solutions Architect Associate – Question 6
-
Timed Mode Set 2 – AWS Certified Solutions Architect Associate – Question 6
Irene-TutorialsDojo updated 3 months, 2 weeks ago
2 Members
·
2
Posts
-
A company is building an internal application that serves as a repository for images uploaded by a couple of users. Whenever a user uploads an image, it would be sent to Kinesis Data Streams for processing before it is stored in an S3 bucket. If the upload was successful, the application will return a prompt informing the user that the operation was successful. The entire processing typically takes about 5 minutes to finish.
Which of the following options will allow you to asynchronously process the request to the application from upload request to Kinesis, S3, and return a reply in the most cost-effective manner?
A: Use a combination of Lambda and Step Functions to orchestrate service components and asynchronously process the requests.
B: Use a combination of SQS to queue the requests and then asynchronously process them using On-Demand EC2 Instances.
C: Replace the Kinesis Data Streams with an Amazon SQS queue. Create a Lambda function that will asynchronously process the requests.
D: Use a combination of SNS to buffer the requests and then asynchronously process them using On-Demand EC2 Instances.
<div>
</div>According to the test, the correct answer is C.
Even if this is the most cost-effective option, it contradicts the question phrasing, which implies that Kinesis should be involved in the solution:
“Which of the following <…> from upload request to Kinesis <…><i style=”font-family: inherit; font-size: inherit;”>”.
IMO, this is either a poorly written question, or a poorly written set of answers.
-
Hi tugjg,
Thanks for pointing this out. You’re right, the stem requires Kinesis Data Streams. We’ve updated the item and key: the updated correct answer is now Option 3: Use Kinesis Data Streams with AWS Lambda consumers to process records and write them to S3. This keeps Kinesis in the flow and meets the async, cost-effective requirement. Lambda natively polls Kinesis via event source mappings, batches/retries records, and writes to S3 on-demand, no servers or extra orchestration to manage.
If you have further questions or need additional clarification, please don’t hesitate to contact us.
Best,
Irene @ Tutorials Dojo
Log in to reply.