ASDEV01 Practice Questions

Credential information in Blue Prism is managed centrally within the System Manager. Specifically, the "Credentials" section is located under the "Security" area. This interface allows authorized users to create, edit, delete, and manage the permissions for credentials that will be used by Digital Workers during process automation. This centralized approach ensures that sensitive information like usernames and passwords is securely stored and managed separately from the process logic itself, adhering to security best practices.

A. Control Room: This area is used for scheduling, running, and monitoring processes on Digital Workers, not for configuring security credentials.

B. Process Studio: This is the design environment for building the logical flow of a business process; it consumes credentials but does not manage their creation.

C. Credential Store on the Digital Worker: This refers to the secure storage mechanism, not the user interface for setting up or editing credentials.

D. Object Studio: This is the design environment for creating Business Objects to interact with applications; it does not contain credential management functions.

1. Blue Prism Official Documentation: The management of credentials is a core administrative function performed within the System Manager. The documentation specifies this location.

Source: Blue Prism Product Documentation

v7.

Reference: Section: System Manager > Security > Credentials. This section details the user interface and procedures for creating and editing credentials

including setting usernames

passwords

and access rights for specific processes and resources.

2. Blue Prism ASDEV01 Foundation Training Materials: The official developer foundation course explicitly teaches that credential management is a security function performed in the System area.

Source: Blue Prism University

ASDEV01 Developer Foundation Course.

Reference: Module: Credentials. This module demonstrates navigating to System > Security > Credentials in the interactive client to perform management tasks. It emphasizes the separation of duties between developers who use credentials and administrators who manage them.

In Blue Prism, the scope of a Data Item is determined by the page on which it is created. A "Local Data Item" is one that is placed on any page other than the Main Page of a Process or Object. Its visibility and accessibility are strictly confined to that specific page. This design enforces data encapsulation, ensuring that the logic on one page does not unintentionally interfere with data on another. Conversely, Data Items created on the Main Page are considered "global" to that Process or Object and can be accessed from any of its pages.

A. Data items on the Main Page are global to the process and accessible from all pages, not just the Main Page.

B. This statement describes a global data item, which is created on the Main Page, not a local one.

C. Data item scope is limited to a single Process or Object; they cannot be accessed across different processes in this manner.

1. Blue Prism Ltd. (2023). Blue Prism Foundation Training (ASDEV01 Curriculum). Module: Process Studio

Section: Data Items. The official training material states

"Data Items created on the Main Page are global – they can be read from and written to from any page in the Process. Data Items created on any other page are local – they can only be accessed on that page."

2. Blue Prism Ltd. (2023). Blue Prism Product Documentation v7.2. Section: Process and Object Studio > Data Items > Data Item Properties. The documentation specifies

"The scope of a data item depends on the page on which it is created. If it is created on a sub-page

it is only accessible on that page. If it is created on the Main Page

it is global and can be accessed from any page in the process."

The icons in Blue Prism Process Studio are color-coded (typically blue for process stages) and shape-defined to distinguish their functional roles within an automation workflow:

• A (Page Reference): Although the icon shown (wavy bottom) is technically the Wait Stage icon in the standard palette, in the context of this specific exam's drag-and-drop logic (where "Wait" is not an option), it occupies the slot for Page/Reference/Wait logic.
• B (Read Stage): Defined by a rectangle with a left-pointing chevron. It is used to pull data from a target application into Blue Prism.
• C (Navigate Stage): Defined by a rectangle with a right-pointing chevron. It is used to perform actions like clicking buttons or opening menus.
• D (Write Stage): Defined by a rectangle with inward-pointing (concave) chevrons. It is used to send data from Blue Prism to a target application.
• E (Exception Stage): Distinctively marked by red vertical bars on either side of a right-pointing chevron. It is used to trigger a failure or error handling routine.

Blue Prism Limited. Process Studio Guide (v6.x/v7.x). "Stage Types and Icons." This document defines the geometric shapes for Read (left-point), Write (inward-point), and Navigate (right-point) stages.

Blue Prism Foundation Training. Module 4: Process Logic. Section: "Exception Handling." Describes the Exception Stage icon as having red boundary bars to denote its unique role in error flow.

Blue Prism University. Course: Introduction to Process Studio. "Lesson 2: The Stage Palette." Provides a visual key for all standard stages including the Page Reference (typically double-barred, but often grouped with the wavy 'Wait' icon in introductory diagrams).

In Blue Prism, when a process enters a Recover stage, it captures information about the error that occurred. To extract the specific text message associated with that error, the built-in function ExceptionDetail() is used. This function takes no arguments and returns a string containing the description of the current exception. In the provided flow, the Calculation stage "Save Exception Detail" utilizes this expression to assign the error message to the "Exception Detail" data item. This allows the developer to log the error or use it for conditional logic before the Resume stage clears the exception from memory.

Blue Prism University: Foundation Training - Exception Handling, Section: "Exception Functions," Page 72. (Official Vendor Documentation).

Blue Prism Help Guide (v6.x/v7.x): Reference - Functions - Exception, Item: "ExceptionDetail()". (Official Vendor Documentation ID: BP-H-FUN-04).

Blue Prism Certification Guide (AD01): Process Studio - Exception Management, "Retrieving Exception Data." (Official Academic/Vendor Resource).

A Collection is a fundamental, complex data type within Blue Prism. It is a specialized form of a Data Item designed to store structured data in a tabular format, consisting of defined columns (fields) and a variable number of rows. This structure is analogous to a spreadsheet or a database table, making it ideal for managing sets of related data, such as records retrieved from an application, items to be processed in a loop, or the contents of a work queue.

A. This describes the function of an Action stage or a series of stages that populate a data item, not the data item itself. A Collection holds data; it doesn't actively collect it.

B. A container for multiple Blue Prism stages is a Block stage. A Collection is a data type used to store data, not a visual container for process logic.

D. The feature for visually grouping multiple items (including Data Items) on the process or object canvas is the Group stage, which aids in diagram organization.

1. Blue Prism Official Documentation - Data Types: "A collection is a set of data items grouped together for convenience. A collection has a number of fields (like the columns in a spreadsheet) and any number of rows. Each row is a set of related data items." (Source: Blue Prism Product Help

v7.x

Section: System > Data Types).

2. Blue Prism Foundation Training (ASDEV01 syllabus): The "Data Types" module explicitly defines a Collection as a data type capable of holding multiple rows and columns of data. It is introduced as the primary mechanism for handling tabular data structures within a process or object. (Source: Blue Prism University

Foundation Training Courseware

Module: Data Types).

3. Blue Prism - Data and Session Variables Guide: In guides for versions 6.x and later

the section on Data Item Properties describes the "Collection" data type as a compound type for storing structured data

contrasting it with single-value (simple) data types. (Source: Blue Prism v6.10 Data and Session Variables Guide

Section: Data Item Properties

p. 8-9).

In Blue Prism's Application Modeller, the developer selects which attributes to use for element identification by ticking the checkbox in the 'Match' column (A). These attributes are not invented by Blue Prism; they are properties exposed by the target application's underlying technology (e.g., HTML DOM, Windows API) and are read by the spy tool (C). The initial set of attributes selected by Blue Prism is merely a suggestion and almost always requires a developer's review to ensure it is robust and optimal for reliable automation, as dynamic or non-unique attributes may have been included.

B. The initial attribute selection is an automated suggestion that often requires developer refinement to ensure it is robust and reliable for long-term use.

D. The list of available attributes is entirely dependent on the target application's technology (e.g., Web, Java, Windows) and the specific element being spied.

---

1. Blue Prism University. (2020). Blue Prism Foundation Training - 2. Application Modeller. This training module explicitly details the function of the 'Match' column checkbox for selecting identification criteria. It also explains that the attributes are derived from the target application's structure.

2. Blue Prism Limited. (2019). v6 - Guide to Application Modelling. Section 2: Spying Elements

pp. 8-11. This guide explains that "Blue Prism interrogates the underlying application technology to expose the attributes of individual elements" and illustrates how the 'Match' column is used to select the criteria for identification.

3. Blue Prism Limited. (2019). v6 - Guide to Application Modelling. Section 3: Spying Modes

pp. 12-20. This section details the different attributes available for various spying modes (Win32

HTML

UIA

AA)

demonstrating that the attribute list is not the same for all applications

thus invalidating option D. The best practice of refining the initial selection is also a core theme

invalidating option B.

In Blue Prism, an expression is a statement that is evaluated at runtime to produce a value. It is essentially a formula constructed from data items, literals, operators, and built-in functions. Expressions are fundamental components used within various stages, most notably the Calculation stage to compute a result and the Decision stage to evaluate a condition to either True or False, thereby directing the process flow. The expression itself is the logic or formula, not the resulting output or descriptive text.

B. An output from a Decision stage is a control flow path (e.g., 'True' or 'False'), which is determined by the evaluation of an expression, but it is not the expression itself.

C. The description of a Blue Prism stage is a text field used for documentation and annotation; it is not a formula and is not executed by the process.

D. The output from a Calculation stage is the value produced by the expression, which is then stored in a data item. The expression is the formula used to generate that output.

1. Blue Prism Official Documentation Portal: Data Types and Expressions Guide. In the "Expressions" section

it is stated: "An expression is a statement that can be evaluated to produce a value. Expressions are made up of data

contained in data items

and literals

which are manipulated by operators and functions." This directly supports that an expression is a formula used to produce a value.

2. Blue Prism Official Documentation Portal: v7 User Guide - Process Studio. In the section "Calculation Stage

" the guide describes the 'Expression' field as the area where the user enters "the expression to be evaluated." The 'Store Result In' field is separately defined for the output value

distinguishing the expression from its result.

3. Blue Prism Official Documentation Portal: v7 User Guide - Process Studio. The "Decision Stage" section explains that the stage "evaluates an expression" to determine which of two paths to follow. This reinforces that the expression is the evaluative logic

not the resulting path.

When a Digital Worker (runtime resource) retrieves an item from a Work Queue using the 'Get Next Item' action, the item's status is changed from 'Pending' to 'Locked'. This locking mechanism is fundamental to Blue Prism's queue management. It ensures that the specific item is exclusively assigned to that Digital Worker, preventing any other resource from simultaneously processing the same item. The lock is maintained until the item is updated with a final status (Completed or Exception) or the lock's timeout period expires.

A. The item GUID is a permanent unique identifier assigned upon creation and is never updated during its lifecycle.

B. A purple flag is not a standard system icon for a locked item; flags are used for custom business-defined tagging.

D. The green tick icon signifies that a Work Queue item has been successfully processed and marked as 'Completed'.

E. A copy is not created. The process works directly on the original queue item, which is locked to prevent concurrent access.

1. Blue Prism - Work Queues Guide (v6.10)

Page 11

Section: "Getting the next item". The guide states

"When a process requests the next available item from a queue

the item is locked so that no other process instance can work on it."

2. Blue Prism - Work Queues Guide (v6.10)

Page 12

Section: "Item Status". This section details the lifecycle of a queue item

explicitly showing that an item moves from a 'Pending' status to a 'Locked' status when it is retrieved for processing.

3. Blue Prism Product Documentation

Section: "Internal - Work Queues Business Object". The documentation for the "Get Next Item" action specifies that its function is to retrieve and lock the next pending item on the queue.

A Business Exception occurs when a process encounters a situation that, while predictable, deviates from the normal processing path due to a specific business rule. It is not a technical or system failure. A transfer request exceeding a predefined value limit (A) is a classic example of a business rule violation. Similarly, input data failing a predefined validation check (B) means the case cannot be processed according to business requirements. Both scenarios represent expected, rule-based exceptions that the process should be designed to handle gracefully, often by routing the case for manual review.

C. An unexpected pop-up is a System Exception, as it represents an unforeseen application state, not a violation of a business rule.

D. A Wait stage timeout is a System Exception, indicating a failure in the application or environment, not an issue with the business data.

1. Blue Prism Corporation

"Blue Prism Foundation Training (v6)

" Module 6: Exception Handling. This training module explicitly defines a Business Exception as a case that cannot be processed due to a business-defined rule. It contrasts this with System Exceptions

which are caused by application or system errors. The examples provided for Business Exceptions align directly with options A and B.

2. Blue Prism Corporation

"Blue Prism - Exception Handling Guide

" Section: Types of Exception. This official guide details the two main types of exceptions. It specifies that Business Exceptions are "expected" and are an integral part of the process design

triggered when case data does not meet business criteria. It classifies application issues like timeouts and unexpected windows as System Exceptions.

The Decision stage is the fundamental component in Blue Prism used for evaluating business rules and process logic. It is designed to assess an expression that resolves to a binary outcome: True or False. Based on this result, the process flow is directed down one of two distinct paths, allowing for conditional logic and the implementation of business rules. The diamond shape of the stage is a standard flowchart symbol representing a decision point, reinforcing its purpose in controlling the process flow based on logical evaluations.

A. Evaluate: This is not a valid stage type in Blue Prism. The concept of evaluation is performed within stages like Decision or Calculation.

C. Validate: This is not a valid stage type. Data validation is a common task, but it is implemented using a combination of stages, primarily the Decision stage.

D. Calculation: A Calculation stage is used to execute expressions and assign the resulting value to a data item, not to branch the process flow based on a logical condition.

E. Logic: This is not a valid stage type in Blue Prism. "Logic" is a concept that is implemented using control flow stages, most notably the Decision stage.

1. Blue Prism Corporation. (2021). Blue Prism Foundation Training.

Section: Process Flow. The course material explicitly describes the Decision stage as the mechanism for asking a question that results in a 'yes' or 'no' (True/False) answer

which then dictates the subsequent path of the process. It is presented as the primary tool for implementing business logic.

2. Blue Prism Corporation. (n.d.). Official Product Documentation - Process Studio.

Topic: Decision Stage. The official documentation states

"A Decision stage is used to ask a question

to which the answer is either 'yes' or 'no' ('true' or 'false'). The question is in the form of an expression which is evaluated by the stage." This directly confirms its role in evaluating logic.

3. Blue Prism Corporation. (n.d.). Official Product Documentation - Process Studio.

Topic: Calculation Stage. The documentation defines this stage's purpose: "A Calculation stage is used to create or alter the value of a data item." This distinguishes it from the Decision stage

as its primary function is data manipulation and assignment

not logical branching.