AD01 Blue Prism Accredited Developer Exam Questions and Answers

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)

• Delivery Lifecycle Phases:
• Missing Phase:

References:

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

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

References:

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

• Understanding Blue Prism Flow Representations:
• Analysis of Options:
• Conclusion:

References:

• Blue Prism Developer Documentation: Exception Handling
• Blue Prism Training Material on Process Flow and Error Management

• Operational Handbook:
• Benefits:
• Not a Benefit:

References:

• Blue Prism documentation on operational handbooks and their benefits.

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

• 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

As per the process template the resume there should be another action or page after the resume stage.

To resolve the error at the Navigate stage when using a dynamic input value to navigate the left menu links in a web-based application, it is crucial to ensure the Web Target Address attribute is set correctly.

• 'Web Target Address' attribute should be checked for the element (Option A): This attribute helps Blue Prism identify the correct target address for navigation. Ensuring it is checked and properly configured will allow Blue Prism to navigate accurately.

Other options may not address the root cause effectively:

• 'Web Path/X Path' attribute should have '= (Equal)' as the Match Type (Option B): This is not necessary if the dynamic value is already used effectively.
• 'Value' field of the Web Text attribute should be cleared (Option C): Clearing the value may result in the element not being found at all.
• 'Web Page Address' attribute should be unchecked for the element (Option D): This could cause navigation issues if the page address is not correctly identified.

ReferencesRefer to Blue Prism's documentation and best practices for configuring web elements and attributes for navigation stages.

• Exception Handling Best Practices:
• Issue in the Main Page:
• Required Logic:

References:

• Blue Prism documentation on best practices for exception handling and process design.

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

Rest all other reasons are failed.

• 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

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.

• Credential Retrieval:
• Cause of Exception:
• Steps to Fix:

References:

• Blue Prism documentation on using the Credential Manager and best practices for secure credential 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.

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

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.

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

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

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)

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

References:

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

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

References:

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

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

• Importing Release Files:
• Handling Conflicts:

References:

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

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.

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

• 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

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.

• Attributes in Application Modeller:
• Conclusion:

References:

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

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.

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