AD01 Blue Prism Accredited Developer Exam Questions and Answers

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

References:

• Blue Prism documentation on spy modes and element identification.

• 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

The 'Multi1' calculation stage in the process flow attempts to perform multiple calculations sequentially. Here are the calculations and the issues they cause:

• Initial Values:
• Calculations:

However, if these calculations were performed strictly in the order they appear in the table, the initial End Value of 0 would cause a division by zero error on the second calculation (5 / [End Value]), resulting in an internal exception before any values could be reassigned. Therefore, the correct answer is that an internal exception for division by zero will be thrown.

References:

• Blue Prism Process Design guidelines
• Error handling documentation in Blue Prism

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

References:

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

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

Reason: IsStopRequested() function is used for the immediate stop provided by the blueprism (mentioned in the foundation course)

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.

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

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.

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.

• 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

• Understanding the Calculation Stage:
• Analyzing the DateAdd Function:
• Interval Values in DateAdd Function:
• Conclusion:

References:

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

Environmental variables are those variables that are available to all processes and business objects. So, these variables are used as dynamic variables, to make sure they can be used whenever required across the Blue Prism platform.

To ensure Blue Prism best practices are followed in respect to naming conventions and layout, the developer should design the object with the following action pages: Launch, Attach, Login, Navigate, and Terminate. Each of these action pages serves a distinct purpose, making the object modular and easier to maintain.

• Launch: This action page is used to start the application.
• Attach: This action page is used to attach to the running instance of the application.
• Login: This action page is used to handle the login process.
• Navigate: This action page is used to navigate through different menus or pages within the application.
• Terminate: This action page is used to close the application properly.

Option C follows these best practices by including Launch, Attach, Login, Navigate, and Terminate action pages, ensuring the object is well-structured and adheres to naming conventions.

The other options do not fully comply with these best practices:

• Option A: Does not include a Terminate action page, which is important for cleanly closing the application.
• Option B: Uses "Orders" instead of a more generic "Navigate" and does not include Terminate.
• Option D: Similar to Option C but uses "Centrix Data Solutions - Basic Actions" instead of the more specific naming convention "Basic Actions – Centrix 01."

ReferencesRefer to Blue Prism's best practices documentation on Object Design, emphasizing modularity, clear naming conventions, and distinct action pages for different functionalities.

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.

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

References:

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

Environment variables value will only be change when the next time process runs and the session variables will change immediately on change in control room.

Session variables values will only be change from the control room and the env variables is only change from the system manager.

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)

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.

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

References:

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

• 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

• Analyzing the Exhibit:
• Identifying the Issue:
• Conclusion:

References:

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

• Understanding the Exception:
• Analyzing Possible Causes:
• Most Likely Cause:

References:

• Blue Prism Developer Documentation: Exception Handling and Troubleshooting
• Blue Prism Training Material on Application Modelling and Object Association

• Attributes in Application Modeller:
• Conclusion:

References:

• Blue Prism Developer Documentation: Application Modeller Attributes
• Blue Prism Training Material on Element Matching and Attributes

In Blue Prism, to construct a valid file path from a root folder and a file name, you need to concatenate these two strings with the appropriate directory separator (backslash in Windows). The correct expression combines the root folder, a backslash, and the file name to form a complete path.

• [Root Folder]&''&[File Name] (Option D): This expression correctly concatenates the root folder and the file name with a backslash in between, forming a valid path. For example, if [Root Folder] is "C:\Users\Exam Taker\Downloads" and [File Name] is "File_to_Save.xlsx", the result would be "C:\Users\Exam Taker\Downloads\File_to_Save.xlsx".

The other options are incorrect:

• ReplacedFile Name]," xlsx" "")&" xh»x" (Option A): This contains syntax errors and incorrect handling of file extensions.
• [Root Folder)&[File Name]&'\xlsx" (Option B): This incorrectly places the file extension as a separate string, and there is a syntax issue with the parenthesis.
• LoadTextFile([Root Folder]&''&" xisx" (Option C): This uses an incorrect function (LoadTextFile) and has a typo in the extension.

ReferencesRefer to Blue Prism's documentation on string manipulation and expression building to understand how to correctly concatenate strings to form file paths.

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

To ensure that only credit transactions are included when calculating the total of customer credits, the 'Credit Transaction?' decision stage needs to check if the transaction code is between 50 and 99. Given that transaction codes are stored as text, we need to convert these values to numbers before performing the comparison.

• Customer Transactions Collection:
• Credit Transaction Identification:
• Decision Stage Expression:

References:

• Blue Prism Process Design guidelines
• Data type conversion functions in Blue Prism

• 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

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)

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.

• Understanding Environment Variables:
• Updating Environment Variables:
• Conclusion:

References:

• Blue Prism Developer Documentation: Environment Variables
• Blue Prism Training Material on Variable Management and Configuration

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.

• 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

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.

• 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