AD01 Practice Exam Questions with Answers Blue Prism Accredited Developer Exam Certification

To search for Work Queue items based on tags in Blue Prism, you can use specific search strings in the Control Room:

• “+Height;Tall” - This search string will return all items that have been tagged with the ‘HeightTall’ value. The plus sign (+) indicates that you want to include items with this tag.
• “-Material;Brick” - This search string will return all items that do NOT have the ‘Material Brick’ tag. The minus sign (-) is used to exclude items with this tag.

When using these search strings, Blue Prism will filter the Work Queue items accordingly, showing only those that meet the specified criteria.

ReferencesFor more detailed information on how to use tags for searching Work Queue items in Blue Prism, you can refer to the official Blue Prism documentation or instructional videos provided by Blue Prism University1

• 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

• 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

Reason: As the business object is only configure in the Object studio.

Rest all other reasons are failed.

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.

• Pausing a Schedule:
• Maintaining Configuration:
• Reactivation:

References:

• Blue Prism documentation on scheduling and best practices for managing schedules.

• 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

Reason: As the window text is not unique when the value is changed and bp is able to spied at time a error would come. So there is no use of window text.

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

• Input Data Item:
• Decision Criteria:
• Flow Execution:
• Calculation Stage:
• Final Output:

However, based on the diagram provided and the path conditions, it's clear that "Right([Input], 6) = "Prism!"" is true for the given input "Blue Prism!". This means the flow will follow Path B, and the final result in the Output data item will be "B".

References:

• Blue Prism documentation on decision stages and calculation stages.
• The provided process logic and decision criteria.

In Blue Prism, a Clean Up page is used to perform finalization tasks as the business object is closed down. This can include tasks such as closing all instances of applications, saving any final state, and releasing resources. The Clean Up page is called automatically by Blue Prism when the business object is disposed of at the end of a business process.

• Option A (Close All Instances): This is the correct use of the Clean Up page. It involves closing all instances of the application or resources that were used during the process. This ensures that no instances are left open, which could otherwise lead to resource leaks or conflicts.

The other options are not ideal for the Clean Up page:

• Option B (Save Workbook): While saving a workbook might be necessary, it is more appropriate to do this as part of the main process or just before the clean-up if it is part of the final steps in the business process.
• Option C (Save Workbook): Similar to Option B, this does not fit the primary use case for a Clean Up page.
• Option D (Exit): While exiting might seem appropriate, it is too generic and does not convey the specific actions needed for cleaning up resources.

ReferencesRefer to Blue Prism's best practices and documentation on using Clean Up pages to ensure that resources are properly finalized and released at the end of a business process.

• Understanding the Scenario:
• Possible Reasons for Inability to Edit:
• Conclusion:

References:

• Blue Prism Developer Documentation: Application Modeller Permissions
• Blue Prism Training Material on Shared Application Models and User Permissions

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

References:

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

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.

• Understanding Blue Prism Components:
• Capability to Interact with Business Applications:
• Conclusion:

References:

• Blue Prism Developer Documentation: Object Studio and Business Objects
• Blue Prism Training Material on Application Interaction

In Blue Prism, wait stages are crucial to ensure that the application is in the correct state before proceeding with further actions. In this scenario:

• Conditional Wait stage after the Attach page: This ensures that after attaching to the application, the process waits until the necessary elements are present before continuing. This is important because the application may take some time to load or change states.
• Conditional Wait stage after the Navigate stage: This ensures that after navigating, the process waits until the target elements are available. This helps to handle any delays in the application response or page loading times.

By configuring wait stages in this manner, you ensure that the process only proceeds when the application is ready, thereby minimizing the risk of errors due to timing issues.

Other options are less optimal:

• Unconditional Wait stage (Options C and D): These do not provide the necessary checks to confirm the application's state and can lead to unreliable automation.
• Wait stage after the Write stage (Option A): This is less relevant if the critical steps are attaching and navigating, which are the primary steps where timing issues are likely to occur.

ReferencesRefer to Blue Prism's best practices on using wait stages to synchronize process execution with the application state.

• Understanding Work Queue Icons in Blue Prism:
• Icons and Their Meanings:
• Conclusion:

References:

• Blue Prism Developer Documentation: Work Queue Icons and Status Indicators
• Blue Prism Training Material on Work Queue Management

Using environment variables is a best practice in Blue Prism for managing configuration settings that may vary across different environments (e.g., Testing, Development, Training, and Production). This approach allows for easy updates and changes without modifying the underlying code.

• Environment Variable: Storing the URLs in an environment variable allows you to change the URL for different environments without altering the business object or process code. This makes the automation more flexible and easier to maintain.

Other options are less optimal:

• Build per URL (Option A): Creating separate objects for each URL is inefficient and increases maintenance effort.
• Dynamic Match (Option B): This does not specifically address URL management.
• Global Data Items (Option C): While global data items can store URLs, environment variables are more suited for managing environment-specific configurations.

ReferencesRefer to Blue Prism's best practices on managing environment-specific configurations using environment variables.

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)

• Importing Release Files:
• Handling Conflicts:

References:

• Blue Prism documentation on importing release files and handling conflicts.

Reason: This is happening when identifying the elements in application modeler some of the details which are changing on the different environment and while identifying the elements in application modeler the developer takes the element whose values are changing and when the application run on the different path at that point of the time the process is able to expecting values eg same url, date or title but it is not at there so the process terminates. Follow the best practice for this.

Reason: A) when spying the application, blueprism fetch all the elements of the target application only, blue prism doesn’t provide any elements of its own.

C) Attributes are vary from application type to type. Attributes are different for windows, browsers, mainframe, java.

D) Reason is below.

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

• Revisiting the Issue:
• Analyzing the Possible Reasons:
• Conclusion:

References:

• Blue Prism Developer Documentation: Collections and Global Data Items
• Blue Prism Training Material on Data Item Scope and Visibility

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

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.

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

References:

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

• Initial Analysis of the Action Flow:
• Importance of Wait Stages:
• Identification of Critical Points for Wait Stages:
• Implementation:

References:

• Blue Prism Developer Documentation: Best Practices for Wait Stages
• Blue Prism Training Material on Intelligent Wait Stages

• 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, the Wait stage is used to pause the process until specific conditions are met or a timeout occurs. The following points explain why Option B is the correct answer:

• If all conditions are met before the TimeOut period expires, the process will continue (Option B): This is the correct behavior of the Wait stage. If the specified conditions are met before the timeout period, the process will continue without waiting for the entire timeout duration.

The other options are incorrect:

• The Wait Stage will sequentially check each condition, it does not require all conditions to be met (Option A): This is incorrect because the Wait stage does not check conditions sequentially but rather waits for any specified condition to be met.
• If no conditions are met, an internal error will appear and terminate the process (Option C): This is incorrect; if no conditions are met within the timeout period, the process will follow the timeout path, which may or may not terminate the process depending on how it is handled.
• The Wait Stage will simultaneously check all conditions and follow the logic of whichever condition is met first (Option D): This is incorrect because the Wait stage waits for any one of the conditions to be met before the timeout, rather than following the logic of the first met condition.

ReferencesRefer to Blue Prism's documentation on the Wait stage and its behavior in processes, highlighting how conditions and timeouts are managed.

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.