Correct answer should be D

Target.Timeout (milliseconds) - Specifies the amount of time (in milliseconds) to wait for the activity to run before the SelectorNotFoundException error is thrown. The default value is 30000 milliseconds (30 seconds).

Confusing - in that case, il will test both parameters. Choose D but not sure

Since the question confirms the Ui Element loads successfully before the timeout, D is the answer.

it's interactive so it will be clicked once it's loaded successfully.

We know that if the WaitForReady was "None" then once the button is loaded, the robot would click on it and it would keep going. We also know if it was set to "Complete" the robot should wait till the whole page loads (which does not happen says the exercise), so the robot cannot click in this case, but it will continue. But it is set to Interactive, which is a bit more confusing. The documentation only says: "- Waits for the target app to indicate readiness, although some assets may still be loading." I believe a browser will be ready just because an animation is not yet loaded (just like having facebook in your chrome, you can start scrolling down, while posts are still loading, to navigate to newer posts). So in this case I chose, that the robot will be able to click once its fully loaded. D

C is the correct

Yes I am doing these dump questions again. I will choose answer D, because even though webpage never loads fully, element itself gets loaded within timeout (30 seconds) and bot clicks it and goes to next activity

Again, question is veeeery poor. "the element specified in the Click activity does load within the specified timeout duration" - what is that specified timeout duration? If it within 30 seconds, then answer D is correct, if it is higher than 30 seconds, then answer C is correct.

The answer is C because ContinueOnError is True and then the process will continue after the click activity.

i belive the correct answer should be D

An animation on the web page never completely loads but the element specified in the Click activity does load within the specified timeout duration. The element loads before timeout so there would be no error and no reason to continueonerror. Due to WaitForReady being interactive, I believe the element is clicked once the element itself is loaded.