UiPath Exam UiPath-RPAv1 Topic 3 Question 102 Discussion

Actual exam question for UiPath's UiPath-RPAv1 exam

Question #: 102
Topic #: 3

While automating an installation wizard, a pop-up window may or may not appear. What can you use to close the window without stopping the workflow?

Options are :

AUse a click activity inside a Try Catch activity

BUse a click activity and set its TimeoutMS property to 30

CUse a click activity with the ContinueOnError property set to True

Show Suggested Answer

Suggested Answer: A, C

by Annette at Dec 11, 2024, 01:09 AM

Limited Time Offer

25%

Off

Get Premium UiPath-RPAv1 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ben

3 months ago

I'm not sure, but I think C) Use a click activity with the ContinueOnError property set to True could also work.

upvoted 0 times

...

Paz

3 months ago

I'd pick option C and just let the workflow carry on, no matter what. Who needs those pesky windows, anyway? Radical!

upvoted 0 times

Arthur

2 months ago

C) Use a click activity with the ContinueOnError property set to True

upvoted 0 times

...

Carmen

2 months ago

B) Use a click activity and set its TimeoutMS property to 30

upvoted 0 times

...

Margurite

2 months ago

A) Use a click activity inside a Try Catch activity

upvoted 0 times

...

Felix

3 months ago

I agree with Ben, using Try Catch can handle any pop-up window that appears.

upvoted 0 times

...

Ben

3 months ago

I think the answer is A) Use a click activity inside a Try Catch activity.

upvoted 0 times

...

Krissy

3 months ago

Option B is the way to go! 30 milliseconds should be more than enough time for that window to close. Gotta love those snappy automations!

upvoted 0 times

...

Nikita

3 months ago

Hmm, I'm leaning towards option A. Using a Try Catch activity seems like a more robust way to handle the unpredictable window.

upvoted 0 times

Erinn

2 months ago

I think option C with ContinueOnError property set to True could also work in this case.

upvoted 0 times

...

Olene

3 months ago

I agree, option A with Try Catch activity is a safer choice.

upvoted 0 times

...

James

3 months ago

Option C looks interesting, but I'm not sure if 'ContinueOnError' is the right approach here. Might be better to use a Try Catch activity to handle the potential error.

upvoted 0 times

...

Thea

3 months ago

I'd go with option B. Setting the TimeoutMS property ensures the click activity doesn't get stuck waiting for the window to appear.

upvoted 0 times

Tanesha

2 months ago

That's a good point. Option C provides a way to handle errors without stopping the automation process.

upvoted 0 times

...

Dulce

2 months ago

That's a good point. Option C provides a way to handle errors without stopping the automation process.

upvoted 0 times

...

Evette

2 months ago

I would go with option C. Setting ContinueOnError to True allows the workflow to continue even if the click activity fails.

upvoted 0 times

...

Alyce

2 months ago

I would go with option C. Setting ContinueOnError to True allows the workflow to proceed even if the click activity fails.

upvoted 0 times

...

Sue

3 months ago

I agree with you. Option B might cause the workflow to get stuck if the window takes longer to appear.

upvoted 0 times

...

Rodolfo

3 months ago

I agree with you. Option A is a safer choice to handle unexpected pop-up windows.

upvoted 0 times

...

Iola

3 months ago

I think option A is better. Using a Try Catch activity ensures the workflow continues even if the window doesn't appear.

upvoted 0 times

...

Katlyn

3 months ago

I think option A is better. Using a Try Catch activity ensures the workflow continues even if the window doesn't appear.

upvoted 0 times

...