Blue Prism AD01 Blue Prism Accredited Developer Exam Exam Practice Test

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.

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

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

• 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

• 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

• Delivery Lifecycle Phases:
• Missing Phase:

References:

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

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: (page 2)

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.

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: When passing the values in the Parameter the parameter should be configured with respect to the window text and pass as the value “close” as other attributes are identical we only have window text to make our fingerprint unique.

Reason: Is is common as the duplicate elements we are found by default as the attributes are provided by the application not by the blue prism. how do make our elements unique is not done by practicing and experience. ( This is also mentioned in the Foundation course and as well as in other Pdf too)

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

References:

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

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

• 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

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

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.

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.

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.

Loop Orders is configuring to the Orders collection and as per the diagram in the order collection there are 15 rows so the loop is run till 15 times and the process order page will executed 15 times.

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

References:

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

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.

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.

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

References:

• Blue Prism documentation on using the Credential Manager and best practices for secure credential handling.

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.

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.

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.

• Startup Parameters:
• Setting Startup Parameters:

References:

• Blue Prism documentation on setting and using startup parameters.

• Importing Release Files:
• Handling Conflicts:

References:

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

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.

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

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.

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

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

References:

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

• 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

• 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

Reason: This is happening when the application is not attached or launched and user tries to read the action. Exercise also mentioned in the foundation course. Below snapshot is from the Exception pdf.