Blue Prism AD01 Blue Prism Accredited Developer Exam Exam Practice Test

In Blue Prism, specific stages are unique to either Process Studio or Object Studio. The Option A stage is known as the "Anchor Stage," which is only found in Process Studio. It is used to create flowchart diagrams by connecting various stages, helping to visualize the process flow.

The other options represent stages that can be found in Object Studio or both studios but not exclusive to Process Studio:

• Option B: This is the "Wait Stage," which can be found in both Process and Object Studio.
• Option C: This is the "Navigate Stage," commonly used in Object Studio.
• Option D: This is the "Decision Stage," which can be found in both Process and Object Studio.

ReferencesConsult Blue Prism documentation that outlines the stages available in Process Studio and their specific use cases.

The Loop Again stage will be executed 11 times when the page is executed. The loop counter data item starts with a value of 0, and each time the loop again stage is executed, it increments by 1 using a calculation stage. The loop will continue until the loop counter value is equal to or greater than the max loops value, which is 10. Therefore, the loop again stage will be executed once for each value of loop counter from 0 to 10, which is 11 times in total. References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)

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

Reason: collection name or data type should always pass in square braces. And if you want to pass any column from the collection than use it as a dot notation after the collection name in the same braces. (You can check this in foundation course or by doing practically)

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 golden rules for Object Design in Blue Prism focus on creating modular, reusable, and maintainable objects. These rules are:

• Keep actions small and limited to a specific task (Option A): This ensures that actions are simple, easy to understand, and reusable.
• Do not include business logic in the Object (Option B): Business logic should be handled in the Process layer, keeping objects focused on interacting with applications.
• Use Input/Output parameters to promote usability (Option C): This enhances the flexibility and reusability of objects by allowing different data to be passed in and out of actions.

However, using a single Object for an entire application (Option D) is not recommended. This approach would result in a monolithic and difficult-to-maintain object. Instead, it is better to create multiple objects, each handling a specific part of the application or a specific type of interaction.

ReferencesRefer to Blue Prism's best practices and guidelines on Object Design, which emphasize modularity, separation of concerns, and reusability.

• 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.

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.

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

• Step Function in Sub-Page:
• Current Stage (Add to Queue):
• Error Handling:

References:

• Blue Prism documentation on exception handling and the use of the Step function.

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.

When setting the Window Text attribute for an application in Blue Prism, it's often helpful to use wildcards to ensure the element is consistently matched, even if the window title varies slightly. In this case, using a * at the beginning and end of the value will match any window title that contains the text "Centrix Data Solutions - Please Log In".

• Use a * at the beginning and end of the Value (Option B): This will ensure that any leading or trailing characters in the window title will not prevent a match. For example, *Centrix Data Solutions - Please Log In*.

Other options might not be as effective:

• Change the Match Type to Dynamic (Option A): This is unnecessary if the wildcard approach works.
• Position the ''after Solutions' (Option C): This does not make sense in the context provided.
• Change the Match Type to Wildcard (Option D): This would require more specific adjustments to the value itself.

ReferencesRefer to Blue Prism's documentation on attribute matching and the use of wildcards for ensuring reliable element identification.

In Blue Prism, there are specific stages that are available in Object Studio but not in Process Studio. These stages are designed to interact with applications and perform specific actions at a more granular level.

• Option A (Action Stage): Found in Object Studio. It allows the object to call actions within other objects or business objects.
• Option B (Read Stage): Found in Object Studio. It is used to read data from an application or interface.
• Option E (Write Stage): Found in Object Studio. It is used to write data to an application or interface.

These stages are part of the functionality provided by Object Studio for interacting directly with applications, and they are not available in Process Studio, which is used for high-level process orchestration.

References:

• Blue Prism Object Studio documentation
• Blue Prism Process Studio documentation

• Understanding Priorities:
• Setting Priorities:
• Implementation:

References:

• Blue Prism documentation on work queue priorities.

Reason: Only the choice stage is found in both process and object studio rest all other stages are found only in the object studio.

The process will move to the 'Close Down' page directly from the 'Stop?' Decision stage under two conditions:

• The specified Stop time has passed: This condition checks if the current local time exceeds the configured stop time. In the provided Decision Properties, the condition LocalTime() > [Stop After Time] evaluates if the current time is beyond the stop time.
• 'Request Stop' received from Control Room: This condition is checked by the IsStopRequested() function. If the Control Room sends a stop request, this function returns true, causing the process to move to the 'Close Down' page.

Other conditions like Stop After Items and an immediate stop request from the Control Room are not mentioned in the process depicted in the exhibits. Therefore, only the two conditions mentioned above apply.

References:

• The Decision stage properties and conditions as shown in the provided exhibit.
• Blue Prism documentation on Decision stages and Control Room interactions for stopping processes.

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

References:

• Blue Prism documentation on spy modes and element identification.

• Delivery Lifecycle Phases:
• Missing Phase:

References:

• Blue Prism delivery lifecycle documentation and project management best practices.

• Understanding Session Variables:
• Behavior of Session Variables:
• Conclusion:

References:

• Blue Prism Developer Documentation: Session Variables
• Blue Prism Training Material on Process Execution and Variable Management

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

References:

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

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.

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

References:

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

When encountering an error due to multiple similar elements on a web page with the same name, it's crucial to use an attribute that ensures a unique match.

• Match Index (Option D): This attribute is specifically designed to handle situations where multiple elements have similar properties. By setting the Match Index, you can specify which instance of the element should be used, ensuring a unique match.

The other options are less effective in this scenario:

• Web Text (Option A): This may not be unique if multiple elements have the same text.
• Ordinal (Option B): While it indicates the order, it’s less precise compared to Match Index.
• Web Element Type (Option C): This doesn't help in distinguishing between multiple similar elements.

ReferencesConsult Blue Prism's best practices for dealing with web automation and handling multiple similar elements on a page. The Match Index attribute is commonly recommended for these cases.

• 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

To retrieve items from a work queue tagged with 'Gas' or 'Electric' and exclude items tagged with 'Dual', you need to use a tag filter that excludes the 'Dual' tag. In Blue Prism, the correct way to exclude items tagged with 'Dual' is to use the '-' operator before the tag name, like -Dual. This ensures that only items tagged with either 'Gas' or 'Electric' but not 'Dual' are retrieved.

References:

• The Blue Prism documentation on work queues and tagging explains how to use the '-' operator to exclude specific tags.

When working with the Blue Prism Application Modeller, the visibility of an element is critical for ensuring that it can be consistently interacted with by Blue Prism. The "Screen Visible" attribute determines whether the element is currently visible on the screen. However, this attribute can sometimes cause issues if the element is off-screen or hidden but still needs to be interacted with by Blue Prism.

• Screen Visible (Option B): Unticking this attribute ensures that Blue Prism can interact with the element even when it is not visible on the screen. This helps in maintaining consistent visibility and interaction with the element regardless of its on-screen status.

The other attributes are important for identifying and interacting with the element:

• Window Text (Option A): This attribute is necessary to identify the text within the window.
• Visible (Option C): This indicates whether the element is visible; unticking this might cause inconsistency.
• Class Name (Option D): This attribute helps identify the type of UI element, crucial for correct interaction.

ReferencesBlue Prism's best practices for application modelling and attribute selection emphasize maintaining consistency and reliability in element interaction by carefully managing visibility attributes.

For window application to ensure the new screen is in focus We need to activate the New screen as not the application

• Reset Action in Business Object:
• Launch Action:
• Application Window:

References:

• Blue Prism documentation on debugging and Business Object behavior during resets.

Reason: There is no wait stage required after Read and write stage as it makes the process lengthy here, because here no activity is performed which are taking time to read and write so wait is not useful.

Here wait is required for search fields as there the activity is happening in which it is required for wait.

• 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

This expression will evaluate to true as long as the number of attempts is less than the maximum number of attempts, which means the process will try again. If the expression is false, it means the number of attempts has reached or exceeded the maximum number of attempts, which means the process will throw an exception. References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)