Discuss UiPath UiPath-ADAv1 Exam Topic 13 Question 33

A developer implemented a process using the Robotic Enterprise Framework and an Orchestrator queue. The MaxRetryNumber from the "Config.xlsx" file is set to "1" and the Max # of retries from the Queue settings from Orchestrator is set to

"2". At runtime, the first transaction item throws a Business Exception.

How many times will the transaction be retried?

AThe transaction will be retried only one time.

BThe transaction will not be retried.

CThe transaction will be retried 2 times.

DThe transaction will be retried multiple times, until it will be processed successfully.

Suggested Answer: B

The types of authentication supported by Connector Builder for Integration Service include various OAuth 2.0 flows, Basic authentication, API Key, and Personal Access Token (PAT). The correct option that lists these authentication types is B, which includes OAuth 2.0 Authorization Code, OAuth 2.0 Authorization code with PKCE (Proof Key for Code Exchange), OAuth 2.0 Client Credentials, Basic, API Key, and Personal Access Token (PAT), along with No Authentication.

UiPath Integration Service Documentation: Authentication Types in Integration Service

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

32 comments · newest first

Mickie 10 months ago

So confusing! I thought it would retry twice with the queue settings.

Bok 11 months ago

Nope, it won't be retried at all. Business Exception stops it.

Odette 11 months ago

Wait, are you sure? The queue says 2 retries.

Mabelle 11 months ago

I agree, it will only retry once.

Miriam 11 months ago

The MaxRetryNumber is set to 1, so only one retry.

Brandon 12 months ago

I’m a bit confused. If the Orchestrator allows 2 retries, does that mean it will retry twice regardless of the Config file? I need to think this through.

Selma 12 months ago

This seems similar to a practice question we did about exception handling. I feel like the transaction will only retry once because of the Config file.

Fausto 12 months ago

I think the Orchestrator queue setting allows for more retries, but since the Config file is set to 1, it might override that.

Delsie 1 year ago

I remember that the MaxRetryNumber in the Config file limits the retries, but I'm not sure how it interacts with the Orchestrator settings.

Zack 1 year ago

I'm pretty confident the answer is C. The MaxRetryNumber from the config file sets the maximum number of retries, but the Queue settings override that and allow for 2 retries. So the transaction will be retried 2 times.

Nana 1 year ago

Okay, let me break this down step-by-step. The MaxRetryNumber from the config file is set to 1, which means the process will only retry the transaction once. However, the Max # of retries from the Queue settings is set to 2. So the transaction will be retried 2 times, as per the Queue settings.

Terina 1 year ago

Hmm, I'm a bit confused. The question mentions both the MaxRetryNumber from the config file and the Max # of retries from the Queue settings. I'll need to think through how these two settings interact to determine the number of retries.

Raul 1 year ago

I think the answer is C. The MaxRetryNumber is set to 1 in the config file, but the Max # of retries from the Queue settings is set to 2, so the transaction will be retried 2 times.

Nu 1 year ago

Wait, so are we talking about a developer, a robot, and an Orchestrator all working together? Sounds like the start of a bad joke!

Francesco 1 year ago

Option B is the way to go! If the MaxRetryNumber is set to 1 and the Max # of retries is set to 2, then the transaction will not be retried at all. Simple as that.

Georgene 1 year ago

Hmm, this is a tricky one. I'm going to go with option D just to be safe. After all, who doesn't love a good, old-fashioned 'retry until successful' strategy?

Elke 1 year ago

↳ replying to Georgene

Option D it is then, let's hope for a successful processing in the end.

Marshall 1 year ago

↳ replying to Georgene

I would go with option D as well, better to be safe than sorry.

Tanesha 1 year ago

↳ replying to Georgene

I agree, retrying until successful seems like a safe bet.

Erasmo 1 year ago

↳ replying to Georgene

I think option D sounds like a good choice.

Tonette 1 year ago

I'm not sure about this one. The question seems a bit tricky. Maybe I should just flip a coin and guess.

Leonida 1 year ago

↳ replying to Tonette

User 3: I'm not sure, maybe it will be retried multiple times until it's successful.

Lawana 1 year ago

↳ replying to Tonette

User 2: I believe the transaction will be retried only one time.

Adolph 1 year ago

↳ replying to Tonette

User 1: I think the transaction will be retried 2 times.

Maryann 1 year ago

Option C is the correct answer. The Max # of retries from the Queue settings from Orchestrator is set to 2, so the transaction will be retried 2 times.

Joanne 1 year ago

↳ replying to Maryann

D) The transaction will be retried multiple times, until it will be processed successfully.

Lili 1 year ago

↳ replying to Maryann

C) The transaction will be retried 2 times.

Jacob 1 year ago

↳ replying to Maryann

B) The transaction will not be retried.

Ilene 1 year ago

↳ replying to Maryann

A) The transaction will be retried only one time.

Hildred 1 year ago

I agree with Romana, the transaction will be retried 2 times because of the Orchestrator queue settings.

Percy 2 years ago

I believe the transaction will not be retried.

Romana 2 years ago

I think the transaction will be retried 2 times.

UiPath-ADAv1 Exam - Topic 13 Question 33 Discussion