Discuss Amazon DVA-C02 Exam Topic 5 Question 30

A developer is using AWS Step Functions to automate a workflow The workflow defines each step as an AWS Lambda function task The developer notices that runs of the Step Functions state machine fail in the GetResource task with either an UlegalArgumentException error or a TooManyRequestsException error

The developer wants the state machine to stop running when the state machine encounters an UlegalArgumentException error. The state machine needs to retry the GetResource task one additional time after 10 seconds if the state machine encounters a TooManyRequestsException error. If the second attempt fails, the developer wants the state machine to stop running.

How can the developer implement the Lambda retry functionality without adding unnecessary complexity to the state machine'?

AAdd a Delay task after the GetResource task. Add a catcher to the GetResource task. Configure the catcher with an error type of TooManyRequestsException. Configure the next step to be the Delay task Configure the Delay task to wait for an interval of 10 seconds Configure the next step to be the GetResource task.

BAdd a catcher to the GetResource task Configure the catcher with an error type of TooManyRequestsException. an interval of 10 seconds, and a maximum attempts value of 1. Configure the next step to be the GetResource task.

CAdd a retrier to the GetResource task Configure the retrier with an error type of TooManyRequestsException, an interval of 10 seconds, and a maximum attempts value of 1.

DDuplicate the GetResource task Rename the new GetResource task to TryAgain Add a catcher to the original GetResource task Configure the catcher with an error type of TooManyRequestsException. Configure the next step to be TryAgain.

Suggested Answer: C

Step Functions Retriers: Retriers provide a built-in way to gracefully handle transient errors within State Machines. Here's how to use them:

Directly attach a retrier to the problematic 'GetResource' task.

Configure the retrier:

ErrorEquals:Set this to ['TooManyRequestsException'] to target the specific error.

IntervalSeconds:Set to 10 for the desired retry delay.

MaxAttempts:Set to 1, as you want only one retry attempt.

Error Handling:

Upon 'TooManyRequestsException', the retrier triggers the task again after 10 seconds.

On a second failure, Step Functions moves to the next state or fails the workflow, as per your design.

'IllegalArgumentException' causes error propagation as intended.

Error Handling in Step Functions:https://docs.aws.amazon.com/step-functions/latest/dg/concepts-error-handling.html

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

34 comments · newest first

Amie 11 months ago

Isn't there a risk of infinite retries with TooManyRequests?

Rosendo 11 months ago

Totally agree with C, less complexity is key!

Lazaro 11 months ago

Wait, why would you duplicate the task? That sounds messy.

Rosendo 11 months ago

I think A is better for clarity.

Pamella 12 months ago

Option C seems like the cleanest solution.

Alonzo 12 months ago

I vaguely remember that duplicating tasks can lead to more complexity. I think we should avoid that option, but I can't recall the exact reasons.

Skye 1 year ago

I feel like adding a Delay task could complicate the workflow unnecessarily. I’m leaning towards using a catcher instead, but I’m not entirely confident.

Louann 1 year ago

I think we practiced a similar question where we had to manage retries. If I recall correctly, using a retrier might simplify things without adding extra steps.

Irma 1 year ago

I remember we discussed how to handle exceptions in Step Functions, but I'm not sure if a retrier or a catcher is the best approach here.

Jettie 1 year ago

This looks like a good opportunity to demonstrate my understanding of AWS Step Functions and error handling. I think option C is the most straightforward and efficient solution, but I'll double-check the other options to be sure.

Sage 1 year ago

I'm not sure I fully understand the difference between the options. I'll need to carefully read through each one and make sure I understand the implications before selecting an answer.

Kerry 1 year ago

Okay, let me think this through step-by-step. I need to handle the UlegalArgumentException error by stopping the state machine, and the TooManyRequestsException error by retrying the task once after 10 seconds. I think option A or B might work for that.

Noble 1 year ago

Hmm, I'm a bit confused about the difference between a catcher and a retrier. I'll need to review that before deciding on the best approach.

Blondell 1 year ago

This seems like a pretty straightforward question. I think I can handle this one.

Stefany 1 year ago

This looks like a tricky BGP configuration question. I'll need to carefully review the options and think through the correct family and neighbor settings.

Leonie 1 year ago

Hmm, I'm a bit unsure about the difference between available stock and released receipts. I'll need to think this through carefully.

Keneth 2 years ago

Option B it is! No need to reinvent the wheel when AWS gives us the tools to handle this gracefully.

Berry 2 years ago

↳ replying to Keneth

That's true, sticking to the recommended approach will also make it easier for future maintenance and troubleshooting.

Junita 2 years ago

↳ replying to Keneth

I agree, it's important to leverage the existing functionality to keep the state machine logic simple and effective.

Kristian 2 years ago

↳ replying to Keneth

Exactly! AWS provides built-in features like catchers and maximum attempts to handle errors efficiently.

Carmen 2 years ago

↳ replying to Keneth

Option B it is! No need to reinvent the wheel when AWS gives us the tools to handle this gracefully.

Sherman 2 years ago

I see your point, but I still think having a separate task for retrying is more clear in this case.

Helga 2 years ago

But wouldn't duplicating tasks add unnecessary complexity to the state machine?

Sherman 2 years ago

I disagree, I believe option D is better. Duplicating the task and retrying with TryAgain seems more straightforward.

Valentin 2 years ago

Option D seems a bit convoluted. Duplicating the task and adding a catcher feels like overkill for this use case.

Gary 2 years ago

I like how Option C uses the built-in retrier functionality of Step Functions. Keeps the state machine clean and easy to maintain.

Maybelle 2 years ago

↳ replying to Gary

Absolutely, keeping things clean and simple is key when working with workflows.

Olene 2 years ago

↳ replying to Gary

It definitely makes the state machine easier to manage in the long run.

Janey 2 years ago

↳ replying to Gary

I agree, using the retrier functionality built into Step Functions is a smart choice.

Mari 2 years ago

↳ replying to Gary

Option C is definitely the way to go. It's simple and efficient.

Helga 2 years ago

I think option A is the best choice. Adding a Delay task after GetResource seems like a simple solution.

Alfred 2 years ago

Option B looks like the simplest and most straightforward way to handle the retries. No need to add extra tasks or complexity.

Pok 2 years ago

↳ replying to Alfred

Yeah, I think adding a catcher to the GetResource task for TooManyRequestsException with a maximum attempts value of 1 is a clean solution.

Tasia 2 years ago

↳ replying to Alfred

I agree, option B seems like the best choice here. It keeps it simple and handles the retries efficiently.

Amazon DVA-C02 Exam - Topic 5 Question 30 Discussion