Blue Prism AD01 Blue Prism Accredited Developer Exam Exam Practice Test

• Understanding Control Room Functions:
• Capabilities of Control Room:
• Conclusion:

References:

• Blue Prism Developer Documentation: Control Room Functions
• Blue Prism Training Material on Work Queue Management

The Saved Quantity data item will contain the sum of all the Quantity values in the Orders collection after the loop. The loop will iterate through each row of the collection and add the value of Quantity to the Saved Quantity data item using a calculation stage. The initial value of Saved Quantity is 0, and after adding each row’s Quantity, it will become 19 (0 + 4 + 5 + 1 + 9). References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)

• Analysis of the Requirement:
• Available Configurations:
• Evaluation of Each Option:
• Conclusion:

References:

• Blue Prism Developer Documentation: Interacting with Application Windows
• Blue Prism Training Material on Window and Element Interaction

• Stage Logging in Production:
• Decision Stage:
• Best Practice:

References:

• Blue Prism best practices for logging and monitoring in production environments.

A sub-page in a process can have only one start stage, which is where the execution begins when the sub-page is called from another page. A sub-page cannot have zero or more than one start stages, as that would cause ambiguity or confusion in the execution flow. References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)

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

• Loop Structure:
• Condition:
• Loop Execution:
• Outcome:
• Final Report:

References:

• Blue Prism documentation on loop stages and decision stages.

Upon restarting the Blue Prism Server Service, the scheduler will check for any schedules that should have been executed during the downtime. Based on the system configuration, only the schedules within a defined timeframe will be executed. This is typically set in the ‘Execute missed schedules from the past n minutes’ setting within the scheduler configuration. If a schedule is discovered that should have executed multiple times within the configured period, it will only be executed once. Schedules that fall outside of this defined timeframe will not be executed and may be marked as exceptions depending on the system settings

In Blue Prism, certain stages can be found in both Object Studio and Process Studio. These stages are:

• Read Stage (Option C): This stage is used to read data from elements and variables. It is available in both Object Studio and Process Studio.
• Write Stage (Option D): This stage is used to write data to elements and variables. It is also available in both Object Studio and Process Studio.

The other stages listed in the options are specific to either Object Studio or Process Studio, but not both.

ReferencesRefer to the Blue Prism documentation and training materials which outline the stages available in Object Studio and Process Studio.

Spy modes in Blue Prism are used to interact with different types of applications. The correct statements about spy modes are:

• Browser Mode is the default mode used for web-based applications (Option D): This is the most accurate statement. Browser Mode is specifically designed for interacting with web-based applications and is the default mode for such cases.

The other options are incorrect:

• Accessibility Mode is the most commonly used for open source web applications (Option A): Accessibility Mode is used for interacting with applications designed with accessibility in mind, not necessarily open source web applications.
• Win32 Mode is the default mode used for web-based applications (Option B): Win32 Mode is used for desktop applications that use the Win32 API, not web-based applications.
• HTML Mode is the most commonly used when a Code Stage is required (Option C): HTML Mode is used for web applications, but the use of a Code Stage does not determine the spy mode.

ReferencesRefer to Blue Prism's documentation on spy modes, which explains the appropriate use cases for each mode.

• Understanding the Diagram and Process Flow:
• Exception Handling in Blue Prism:
• Recover Stage Focus:
• Conclusion:

References:

• Blue Prism Developer Documentation: Exception Handling and Recovery Stages
• Blue Prism Training Material on Debugging and Exception Management

• Data Items:
• Calculation Expression:

"Recent Activity for "& [Data3]& " -" &

" Orders: " & [Data1] &

" Refunds: " & [Data2]

• Breaking Down the Expression:
• Combining the Results:
• Final Output:

References:

• Blue Prism documentation on data item manipulation and string concatenation.

• Data Item Exposure:
• Environment Variables:
• Implementation:

References:

• Blue Prism documentation on Data Item exposure and Environment Variables.

• Spy Mode:
• Testing in Process Studio vs. Control Room:
• First Check:

References:

• Blue Prism documentation on spy modes and element identification.

Reason: This is because when we are running the process in testing and development phase at time the speed of running the process is slow, that’s why it ran properly and when we haven’t give the proper wait stage and when the process ran in control room the exception occurs as the process ran in full speed so the process is not having the time to wait.

This is mentioned in the Process creation exercise or Lifecycle exercise.

• Analysis of the Launch Action:
• Blue Prism Best Practices:
• Reasoning for the Wait Stage:
• Implementation:

References:

• Blue Prism Developer Documentation: Best Practices for Wait Stages
• Blue Prism Training Material on Login Automation Procedures

• Session Variables:
• Updating Session Variables:
• Conclusion:

References:

• Blue Prism Developer Documentation: Session Variables and Data Items
• Blue Prism Training Material on Control Room Operations

Reason: As we need to pass the values in the username so the values of username to be passed only in the username element. As Rest other options are having only the outer area of the spied application.

The provided diagram represents an Action page in a Business Object that is used to place orders. According to best practices for Object Design in Blue Prism, actions should primarily focus on interacting with the application rather than containing business rules or decision-making logic. The following points explain why Option D is the correct answer:

• Avoid applying business rules and decision-making logic in an Action (Option D): Business rules and decision-making should be handled in Process Studio, not in Object Studio. The decision regarding "Quantity Under Limit?" in the diagram is a business rule and should be part of the process logic, not the object logic.

Other options are essential best practices but are not violated here:

• Use a conditional Wait stage to confirm the screen change (Option A): This is followed as the diagram shows a Wait stage confirming the screen change.
• The timeout of the Wait stage should lead to a System Exception (Option B): This is followed as the diagram shows a system exception being thrown upon a timeout.
• An action page should first confirm if the application is connected (Option C): This is followed as the action begins by checking the connection to the "New Order Window."

ReferencesRefer to Blue Prism's best practices for Object Design, which emphasize separating process logic and object interaction logic.

In Blue Prism, Environment Locks are used to prevent concurrent access to resources. When an exception occurs, it is crucial to ensure that the lock is released to avoid deadlocks and ensure other processes can acquire the lock.

• A Release Lock action should be added to the recovery logic to unlock the resource in case of an exception (Option A): This ensures that even if an exception occurs, the lock is released, preventing any potential deadlocks and allowing other processes to acquire the lock.

Other options are not directly addressing the core issue:

• Query Lock action (Option B): This checks the lock status but does not help in releasing the lock during an exception.
• Unique Lock Token (Option C): While important for acquiring the lock initially, it does not address the release of the lock during exceptions.
• Sleep action after Acquire Lock (Option D): This helps in timing but does not handle lock release in case of an exception.

ReferencesRefer to Blue Prism's best practices on using Environment Locks and handling exceptions to ensure that resources are properly managed and locks are released appropriately.

• Best Practices for Production Release:
• Handling Business Exceptions:

References:

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

• Data Items and Types:
• Decision Stage:
• Calc1 and Calc3 Execution:
• Expected Output:

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):
• If the decision path was intended to show Expired status, then:

References:

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

• Exception Handling:
• Preserve Exception Details:
• Configuration:

References:

• Blue Prism documentation on exception handling and recovery stages.

• Exception Handling Logic:
• Issue in Logic:
• Resulting Infinite Loop:

References:

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

• Understanding the Breakpoint:
• Analyzing the Breakpoint Condition:
• Possible Outcomes:
• Conclusion:

References:

• Blue Prism Developer Documentation: Debugging and Breakpoints
• Blue Prism Training Material on Conditional Breakpoints

Reason: Global send key events and global keys are not passed through the navigate stage.

Blue Prism Visual Business Objects (VBOs) are pre-built automation components that need to be imported into the environment. These VBOs are stored in the Blue Prism installation directory.

• **[Root Directory]\Program Files\Blue Prism Limited\Blue Prism Automate\VBO**: This is the correct directory where the VBOs can be found. It contains the necessary VBO files that can be imported into Blue Prism.

Other options do not accurately represent the location of the VBOs:

• Option A: Incorrect path format.
• Option B: Refers to a training directory, which is not the standard location for VBOs.
• Option D: Too general and does not specify the correct sub-directory for VBOs.

ReferencesRefer to Blue Prism installation documentation for the location of Visual Business Objects.

In Blue Prism, a sub-page in a process can have any number of End stages. This is because sub-pages can be designed to handle various branches and paths, requiring multiple endpoints to conclude different process flows. This flexibility allows for more complex and branched process designs, enabling developers to manage various outcomes and logic paths efficiently.

References:

• Blue Prism Process Design guidelines
• Sub-page design documentation in Blue Prism

Following best practices for Blue Prism development, it is essential to keep validation logic separate from the core business process to enhance maintainability and clarity. This approach ensures that validation is modular and can be easily updated or reused.

• Process Studio, a separate page within the process containing validation logic (Option B): This is the best practice for implementing validation logic. By creating a separate page within the Process Studio, the validation logic remains organized and distinct from other parts of the process. This approach allows for easy updates and debugging.

The other options are less ideal for the following reasons:

• Object Studio a business object dedicated to validating the form (Option A): While this is a valid approach, it is generally better to keep validation within the process logic rather than creating a separate object solely for validation.
• Process Studio: an action on the main page calling a Business Object's Validation page (Option C): This complicates the process unnecessarily by involving an additional business object.
• Object Studio a separate page within the create request object containing validation logic (Option D): Keeping validation within the Object Studio ties it too closely to the specific object, making it less flexible and reusable.

ReferencesRefer to Blue Prism's best practices documentation on process design, which emphasizes modularity and separation of concerns.

Blue Prism Process Templates are designed to handle common challenges and ensure robust, reliable automation. The following points directly address the issues the team is facing:

• Contains logic loops which will recover from an Exception, navigate back to a known point in the application, and try to perform the function again (Option A): This ensures that the process can handle transient errors by retrying the operation, thereby improving resilience and reducing unnecessary termination.
• Any error that occurs within a page that is not handled by retrying, will be caught and bubbled up to the Main Page and will go to the Mark Item as Exception' page if not resolved (Option C): This ensures that unhandled errors are appropriately managed, preventing the process from terminating unexpectedly and allowing for proper exception handling.

Other options, while useful, do not directly address the described challenges:

• Environment Variables (Option B): These are useful for configuration but do not address error handling directly.
• Session Variables (Option D): These allow for stopping processes but are not related to error recovery.
• Centralized management of the Work Queue (Option E): This helps with load balancing but does not directly relate to error handling or process recovery.

ReferencesRefer to Blue Prism's documentation on Process Templates, highlighting their built-in error handling and retry mechanisms.

• Understanding the Diagram:
• Analyzing the Logic:
• Identifying the Issue:

References:

• Blue Prism Developer Documentation: Exception Handling and Retry Logic
• Blue Prism Training Material on Process Flow and Exception Handling

In a Citrix environment, where traditional spying modes might not work effectively due to the nature of remote desktop applications, Surface Automation techniques are used. The Region mode allows you to define specific areas of the screen to interact with, making it suitable for environments where duplicate elements are present.

• Region (Option D): This spy mode allows you to define a specific area on the screen and interact with elements within that region. This is particularly useful in Citrix environments where other spy modes might fail to differentiate between duplicate elements.

The other options are less effective in this scenario:

• Win32 (Option A): This mode is used for traditional Windows applications but might not work well in a Citrix environment.
• Browser (Option B): This mode is designed for web-based applications and is not suitable for Windows applications in Citrix.
• Application Navigator (Option C): This mode is not typically used for surface automation in Citrix environments.

ReferencesConsult Blue Prism's documentation on surface automation techniques and best practices for automating applications in Citrix environments.

• Process Definition Document (POD):
• Role in Automation:

References:

• Blue Prism documentation on process documentation and the role of the Process Definition Document (POD).

• Single Object Design:
• Actions:
• Decision-Making Logic:

References:

• Blue Prism best practices on object design and separation of concerns between objects and processes.

• Understanding the Process Diagram:
• Analysis of the Calculation Stage:
• Data Type Considerations:
• Conclusion:

References:

• Blue Prism Developer Documentation: Date Functions
• Blue Prism Training Material on Calculation Stages and Date Manipulation

In Blue Prism's Application Modeller, the "Identify" button offers different options for identifying and working with elements in an application. Understanding the difference between the "Spy Element" and "Navigator" options is crucial for effective element identification and automation design.

• Spy Element (Option D): This option allows you to manually identify an element to use in the Application Modeller. When you select "Spy Element," you manually click on the element within the application to capture its attributes and use them for automation.
• Navigator Options (Option D): The Navigator options, including "Open Application Navigator" and "Open UI Automation Navigator," display a tree of elements available to choose from. These navigators allow you to browse through a hierarchical view of elements in the application, making it easier to select and identify elements that might be difficult to manually spy.

The other options are incorrect because:

• Option A: This does not accurately describe the functionality of the Spy Element and Navigator options.
• Option B: This option misrepresents the primary use of the Navigator options, which is for browsing and selecting elements rather than debugging.
• Option C: This is the reverse of the actual functionality. The Spy Element is used for manual identification, while the Navigator options display a tree of elements.

ReferencesConsult Blue Prism's documentation and user guides on Application Modeller and element identification methods to understand the distinct functionalities of Spy Element and Navigator options.

• Testing Best Practices:
• Verification of Exception Handling:
• Comprehensive Testing:

References:

• Blue Prism documentation on testing best practices for process development.