Blue Prism AD01 Exam Questions

Tagging Exception Items:

By calling the Exception Stage details and tagging them to the item before marking it as an exception, it ensures that detailed information about the exception is captured and can be viewed later. This helps in identifying the cause of the exception and provides valuable context.

Stage Logging:

Enabling stage logging within each exception properties ensures that all exception details are logged. This allows the Process Controller to view detailed exception information from the session logs, providing a comprehensive view of what went wrong.

Benefits:

These two approaches ensure that exception details are both tagged to the work queue items and logged in the session logs, making it easier for the Process Controller to review and analyze exceptions from different interfaces within Blue Prism.

Blue Prism documentation on exception handling, tagging, and logging.

Loop Structure:

The loop iterates through each row in the Data collection.

For each row, it checks the 'Full Time?' condition.

Condition:

If 'Full Time?' is true, the process continues to 'Generate Report of Full Time Employees'.

If 'Full Time?' is false, the row is removed from the collection.

Loop Execution:

Initially, there are 4 rows in the Data collection.

If any row is not full-time, it is removed.

Outcome:

The decision to generate the report happens only if all rows satisfy the 'Full Time?' condition.

Since the diagram does not specify that any rows are full-time and the decision to remove rows occurs based on a negative condition, all rows could potentially be removed.

Final Report:

Given the process flow and assuming all rows do not meet the 'Full Time?' condition, no rows are left for generating the report.

Blue Prism documentation on loop stages and decision stages.

Best Practices for Production Release:

A . Disable unnecessary stage logging: This is a best practice to reduce data storage and improve performance.

C . Alerting Mechanism: Including an alerting mechanism helps notify Process Controllers of critical issues, which is crucial for maintaining process health and quick issue resolution.

D . Zero Validation Errors: Ensuring there are no validation errors before deployment helps avoid runtime failures.

Handling Business Exceptions:

Using retry loops to handle business exceptions for work queue items is not recommended as it can lead to unnecessary retries and may not address the underlying issue causing the exception. Instead, business exceptions should be handled by sending them to an exception queue for further analysis and resolution.

Blue Prism documentation on best practices for process development and deployment.

Data Items and Types:

Sign Up Date: 04-05-2023 (Date data type)

Current Date: 13-06-2023 (Date data type)

Expiry Date: 04-07-2023 (Date data type)

Status: Text data type

Output: Text data type

Decision Stage:

The decision checks if Current Date > Expiry Date.

13-06-2023 is not greater than 04-07-2023, so the decision evaluates to No.

Calc1 and Calc3 Execution:

Since the decision is No, Calc1 and Calc3 are executed.

Calc1 is not shown, but it must set Status to something other than 'Expired' (possibly 'Active').

Calc3 concatenates Status and Expiry Date to form the final output.

Expected Output:

If Calc1 sets Status to 'Active', Calc3 will produce the output:

Subscription Status = Active; Expiration Date = 04-07-2023

Final Output:

Given the logic and data provided, if Calc1 does not change Status from 'Expired' (it wasn't executed due to decision No path):

Subscription Status = Expired. Expiration Date = 04-07-2023

If the decision path was intended to show Expired status, then:

Subscription Status = Expired; Expiration Date = 04-07-2023.

Blue Prism documentation on decision stages and data type handling in expressions.

Exception Handling Logic:

When using ExceptionType() and ExceptionDetail() functions, they must be used within the context of an active recovery stage. These functions retrieve details about the current exception.

Issue in Logic:

In the provided diagram, the Capture Exception Detail stage is executed as a multiple calculation stage but is not within a recovery block. Using these exception functions outside recovery mode can cause another exception.

Resulting Infinite Loop:

This causes a new exception each time the Capture Exception Detail stage is executed, leading to an infinite loop of exceptions as the process continuously tries to recover from the newly generated exceptions.

Blue Prism documentation on proper use of exception functions and recovery stages.