QUESTION: 29

Consider the following process flow:

What is the problem with this flow?

There is nothing wrong with this flow.
The exception handling in this flow can be removed because an Attach action in a navigate stage should always work if configured correctly
The Attach Block should be enlarged to also include the Waited Long Enough decision stage.
The flow contains a recover stage and a route from it without a resume stage. This will cause internal errors on future exceptions thrown in the same session.
The 0.5 second wait stage should be removed so that the retries can be performed at full speed.

Answer(s): A

QUESTION: 30

Study the following process flow on the Main Page of a process where the intention is to preserve the current exception.

What is wrong with the design?

The exception handling is not within an Exception Block.
The exception caught by Recover2 will not be preserved by the Re-Throw Exception stage
The Send Alerts process will never be run
Because the flow is on the Main Page of the process there should not be a `Re-Throw' Exception stage as there are no parent/calling pages for the exception to bubble up' to.

Answer(s): B

Explanation:

Reason: After resume stage the exception is dead so the Re thrown will not worked.

Show Answer Next Question

QUESTION: 31

Refer to the exhibit.

What is wrong with the flow shown in the image?

Sub-pages should not have retry logic, exception handling should be in the object level rather than in the process.
The resume stage must also be within the exception block
The retry loop logic does not include any navigation after the resume stage to ensure the application is ready to try the 'Search Screen -Perform Search' action again.
The retry loop logic shown in the image is incorrect because it uses multiple action stages. There should be a retry loop around every action.

Answer(s): C