Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

💝 Valentine's Sale! Get 30% OFF Any Reviewer. Use coupon code: PASSION-4-CLOUD & 10% OFF Store Credits/Gift Cards

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate Lambda execution period

  • Lambda execution period

  • theodosiostziomakas

    Member
    January 20, 2025 at 6:12 pm

    An application is using a Lambda function to process complex financial data that run for 15 minutes on average. Most invocations were successfully processed. However, you noticed that there are a few terminated invocations throughout the day, which caused data discrepancy in the application.

    Which of the following is the most likely cause of this issue?

    A) The failed Lambda functions have been running for over 15 minutes and reached the maximum execution time.

    B) The concurrent execution limit has been reached.

    C) The Lambda function contains a recursive code and has been running for over 15 minutes.
    D) The failed Lambda Invocations contain a ServiceException error which means that the AWS Lambda service encountered an internal error.

    Hello everyone. I answered A but the answer is B. Why is that? What’s the difference?

    Thanks,
    Theodosios

  • Nikee-TutorialsDojo

    Administrator
    January 21, 2025 at 9:02 am

    Hello theodosiostziomakas,

    Thank you for posting here. The issue described in the scenario is most likely caused by the execution timeout limit of AWS Lambda, making Option 1 the correct answer. AWS Lambda has a maximum execution timeout of 15 minutes per invocation. When a function exceeds this limit, it is forcibly terminated. Since the application’s Lambda functions process complex financial data and run for approximately 15 minutes, any slight delay in execution would result in termination due to the timeout limit.

    Option 2, on the other hand, refers to the concurrent execution limit, which governs the total number of Lambda instances that can run simultaneously. When this limit is reached, new invocations are throttled or rejected, but existing invocations are not affected. This means that the terminated invocations observed in the scenario cannot be attributed to reaching the concurrent execution limit.

    The key difference is that the execution timeout terminates invocations exceeding the maximum time limit, while the concurrent execution limit only affects the ability to start new invocations.

    Regards,
    Nikee @ Tutorials Dojo

  • theodosiostziomakas

    Member
    January 21, 2025 at 5:36 pm

    Thank you, I understood it now.

    Kind regards,

    Theodosios

    • Nikee-TutorialsDojo

      Administrator
      January 22, 2025 at 8:23 am

      Hello theodosiostziomakas,

      Happy to help!
      If you have any further questions, please don’t hesitate to contact us.

      Best regards,

      Nikee @ Tutorials Dojo

Viewing 1 - 3 of 3 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now
Skip to content