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

$4 OFF AWS Security Specialty Practice Exams

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

Home Forums AWS AWS Certified Developer Associate Incomplete Question in CDA Review Mode Set 1

  • Incomplete Question in CDA Review Mode Set 1

  • ionicsolutions

    Member
    August 6, 2024 at 4:53 am

    Hi TD team,

    the first Review Mode Set of the “AWS Certified Developer Associate DVA-C02 Practice Exams 2024” practice exams contains a question that I believe is incomplete and thus misleading.

    Question 56 simply states “An application performs various workflows and processes long-running tasks …” with no mention of Elastic Beanstalk. I believe that unless an application is already managed through Elastic Beanstalk, Amazon ECS with Fargate is a suitable, if not the preferred option among those offered, as migrating an arbitrary “application that performs workflows and processes long-running tasks” to Elastic Beanstalk is most likely a significant effort and will not be possible in many cases.

    So I suggest to clearly mention that this question is about an Elastic Beanstalk application, or at least provide a hint in the question that the application would be well-suited for deployment with Elastic Beanstalk.

    Thanks!

    • This discussion was modified 1 month, 1 week ago by  ionicsolutions.
  • Nikee-TutorialsDojo

    Administrator
    August 6, 2024 at 8:43 am

    Hello ionicsolutions,

    Thank you for your feedback on Question 56 in the AWS Certified Developer Associate DVA-C02 Practice Exams 2024.

    We appreciate your attention to detail and understand your concern. The question’s intent is to highlight the most suitable AWS service for processing long-running tasks asynchronously, which in this scenario is the Elastic Beanstalk worker environment.

    Key words in the question that associate with the correct answer include “performs various workflows” and “processes long-running tasks”. These keywords suggest the need for an environment that efficiently handles background processing, which the Elastic Beanstalk worker environment is designed to do.

    While Amazon ECS with Fargate is indeed a powerful option for containerized applications, the question aims to identify the best approach for offloading background tasks in a way that integrates seamlessly with minimal configuration and operational overhead. Elastic Beanstalk worker environments provide this capability by managing infrastructure, scaling automatically based on the queue, and maintaining the responsiveness of the main application.

    For further reading, you can visit the official documentation for Elastic Beanstalk worker environments.

    Again, thank you for your valuable feedback.

    Best regards,

    Nikee @ Tutorials Dojo

    • ionicsolutions

      Member
      August 6, 2024 at 5:14 pm

      Hi Nikee,

      I understand that Elastic Beanstalk worker environments can be a good solution here but you are not going to adopt Elastic Beanstalk (with all the overhead and specific configuration) just for this purpose. ECS with Fargate is just as suitable for performing various workflows and processing long-running tasks, see https://containersonaws.com/pattern/background-worker-sqs-queue-container-copilot for a reference architecture published by AWS, which is very similar to https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_ecs.html but with less overhead.

      As far as I can see, there is nothing in the question that would indicate that Elastic Beanstalk is the preferred solution — hence my suggestion to add a hint that makes Elastic Beanstalk a clear preference.

      • Nikee-TutorialsDojo

        Administrator
        August 7, 2024 at 10:23 am

        Hi ionicsolutions,

        Thank you for your feedback and for sharing the reference architecture.

        I understand your concern about adopting Elastic Beanstalk specifically for this purpose and acknowledge that ECS with Fargate is a suitable alternative for processing long-running tasks. The architecture you referenced aligns well with the requirements and can offer a scalable and managed solution with less overhead than Elastic Beanstalk.

        In light of your suggestion, we have updated the scenario to clearly indicate that Elastic Beanstalk is the preferred solution. The change will be reflected in our practice tests soon.

        Thank you once again for your valuable feedback. If you have any further suggestions or questions, please feel free to share.

        Best regards,

        Nikee @ Tutorials Dojo

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now