AD01 Blue Prism Accredited Developer Exam Questions and Answers

• Excel VBO Workflow:
• Correct Order:

References:

• Blue Prism documentation on Excel VBO and its actions.

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.

• Understanding the Diagram:
• Analyzing the Flow:
• Conclusion:

References:

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

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.

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.

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

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

References:

• Blue Prism documentation on exception handling and recovery stages.

• 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

Reason: Session variable values to be update only in the Control room.

Below is the reference.

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

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.

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

References:

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

• Defined within the Object Layer:
• Actions Built to No Specific Hierarchy:
• Incorrect Options:

References:

• Blue Prism documentation on the Object layer and Business Objects.

• 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

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

References:

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

• Attributes in Application Modeller:
• Conclusion:

References:

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

• 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

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.

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: As the business object is only configure in the Object studio.

Rest all other reasons are failed.

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)

Feel free to ask if you have any more questions or need further assistance!

• Active Directory Integration:
• Encrypt and Decrypt Work Queue Item Data:
• Functionality Added:

References:

• Blue Prism documentation on Credentials Manager and its integration with Active Directory and work queue item encryption.

• Tagging Exception Items:
• Stage Logging:
• Benefits:

References:

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

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.

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.

• Environment Lock:
• Implementation:
• Correct Approach:

References:

• Blue Prism documentation on Environment Locks and their usage.

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.

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)

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.

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.

• 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

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

References:

• Blue Prism documentation on spy modes and element identification.

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

• Understanding the Process Flow:
• Calculation Stage Expression:
• Analysis of Options:
• Conclusion:

References:

• Blue Prism Developer Documentation: Calculation Stages
• Blue Prism Training Material on Data Item References