Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Developer - Associate · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
A.Eliminada: O problema ocorre no backend (Lambda), e não no frontend. Como a invocação é assíncrona, o frontend não tem controle sobre falhas no processamento. C. Eliminada: Já foi mencionado que os logs do Lambda não mostram erros ou falhas, então apenas inspecionar os logs do CloudWatch não ajudaria a encontrar a causa do problema. D. Eliminada: O cache no API Gateway não afeta requisições POST, pois o cache só é aplicado para métodos GET. Então essa alternativa não faz sentido.
since there are no logs of errors or failures, the issue is likely due to dropped asynchronous events. Configuring a DLQ will capture these dropped events for further analysis and reprocessing. A) Eliminated - While inspecting frontend logs can help diagnose client-side issues, the problem here involves unprocessed events in Lambda. C) Eliminated - The question states that there are no errors or failures in the Lambda logs D) Eliminated - API Gateway caching is not related to this issue. Even with caching enabled, events would still invoke the Lambda function.
Answer : B Lambda has a concurrency limit and in some cases, if the limit is reached, Lambda could throttle incoming requests without throwing an error, which means some invocations may be lost or delayed. Those will be moved to DLQ