Free UIPATH SAIAV1 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

his is confirmed in the UiPath documentation, where the "Train" feature guides users from the

dataset creation stage through the necessary steps to optimize the training process. The system

recommends next best actions based on progress to ensure efficient and focused training🔍

The OOB labeling template is a predefined template that you can use to label your text data for

entity recognition models. The template comes with some preset labels and text components, but

you can also add your own labels using the General UI or the Advanced Editor. When you add an

entity label, you need to fill in the following information:

Name: the name of the new label. This is how the label will appear in the labeling tool and in the

exported data.

Input to be labeled: the text component that you want to label. You can choose from the existing text

components in the template, such as Date, From, To, CC, and Text, or you can add your own text

components using the Advanced Editor. The text component determines the scope of the text that

can be labeled with the entity label.

Attribute name: the name of the attribute that you want to extract from the text. You can use this to

create attributes such as customer name, city name, telephone number, and so on. You can add

more than one attribute for the same label by clicking on + Add new.

Shortcut: the hotkey that you want to assign to the label. You can use this to label the text faster by

using the keyboard. Only single letters or digits are supported.

Color: the color that you want to assign to the label. You can use this to distinguish the label from the

others visually.

Reference:🔍AI Center - Managing Data Labels,🔍Data Labeling for Text - Public Preview

To build custom models supported by AI Center, you can use a Python IDE or an AutoML platform of

your choice. A Python IDE is a software application that provides tools and features for writing,

editing, debugging, and running Python code. An AutoML platform is a service that automates the

process of building and deploying machine learning models, such as data preprocessing, feature

engineering, model selection, hyperparameter tuning, and model evaluation. Some examples of

Python IDEs are PyCharm, Visual Studio Code, and Jupyter Notebook. Some examples of AutoML

platforms are Google Cloud AutoML, Microsoft Azure Machine Learning, and DataRobot.

To use a Python IDE, you need to install the required Python packages and dependencies, write the

code for your model, and test it locally. Then, you need to package your model as a zip file that

follows the AI Center ML Package structure and requirements. You can then upload the zip file to AI

Center and create an ML Skill to deploy and consume your model.

To use an AutoML platform, you need to sign up for the service, upload your data, configure your

model settings, and train your model. Then, you need to export your model as a zip file that follows

the AI Center ML Package structure and requirements. You can then upload the zip file to AI Center

and create an ML Skill to deploy and consume your model.

Reference:🔍AI Center - Building ML Packages,🔍AI Center - ML Package Structure,🔍AI Center - Creating

ML Skills

Recall is a metric that measures the proportion of all possible true positives that the model was able

to identify for a given concept1. A true positive is a case where the model correctly predicts the

presence of a concept in the data. Recall is calculated as the ratio of true positives to the sum of true

positives and false negatives, where a false negative is a case where the model fails to predict the

presence of a concept in the data.🔍Recall can be interpreted as the sensitivity or completeness of the

model for a given concept2. For example, if there are 100 verbatims that should have been labelled

as ‘Request for information’, and the model detects 80 of them, then the recall for this concept is

80% (80 / (80 + 20)). A high recall means that the model is good at finding all the relevant cases for a

concept, while a low recall means that the model misses many of them.

Reference:🔍1:🔍Recall🔍2:🔍Precision and Recall

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/UIPATH_UIPATH-SAIAV1/page_69_img_2.jpg

to load a taxonomy from a given non-default location text file into a variable, the order of steps

should be as follows:

Create a new variable of type 'DocumentTaxonomy' called 'documentTaxonomy', then create a new

string variable called 'taxonomyPath'.

This step involves setting up the necessary variables that will be used in the process. The

'documentTaxonomy' variable will hold the deserialized taxonomy object, and 'taxonomyPath' will

store the path to the taxonomy file.

Using an Assign activity, assign the given non-default taxonomy text file path to the most recent

variable created.

Here you will assign the path of the taxonomy file to the 'taxonomyPath' variable.

Use the Read Text File activity on the 'taxonomyPath' variable created. Next, create a new variable

'taxonomyText', then save the output of the Read Text File activity to 'taxonomyText'.

This step is where you read the contents of the taxonomy file using the 'Read Text File' activity. The

contents are stored in the 'taxonomyText' variable.

Inside the last Assign activity 'Value to Save' property add the following expression:

"Newtonsoft.Json.JsonConvert.DeserializeObject(Of DocumentTaxonomy)(taxonomyText)" where

'taxonomyText' is the text read from the file and 'documentTaxonomy' (the most recent variable

created) is the variable you created.

In this final step, you will deserialize the JSON content from the 'taxonomyText' into a

'DocumentTaxonomy' object using the 'JsonConvert.DeserializeObject' method and assign it to the

'documentTaxonomy' variable.

Following these steps in this order will load the taxonomy from a text file into the

'documentTaxonomy' variable in UiPath.

Comprehensive and Detailed Explanation From Exact Extract:

To evaluate this:

Let’s assume:

doubleX = 10.5

intX = 10

stringX = "18"

Then:

CDbl(intX) → 10.0

CDbl(stringX) → 18.0

Sum = 10.5 + 10 + 18 = 38.5

CInt(38.5) > 38.30 → 38 > 38.30 → True

Result of If → 1

CDbl converts string/numeric values to Double

CInt converts Double to Integer (rounding behavior is floor if .5 and below)

UiPath Reference:

Data Type Conversion - Microsoft VB.NET

Model-based data extraction, often involving machine learning models, is particularly effective for

handling complex data structures such as variable-length data or data that spans multiple pages. This

approach adapts better to varying formats and can extract information more accurately in such

scenarios compared to rule-based or manual methods.

Comprehensive and Detailed Explanation From Exact Extract:

The "Step Out" option in UiPath Studio’s Debugging toolbar, as shown in the image, is used when

debugging a process and you have stepped inside a function, invoked workflow, or nested container.

If you want to exit from the current container (e.g., a workflow or sequence) and return to the caller

or parent scope, you use Step Out.

It executes all remaining activities within the current container, and once complete, pauses the

execution back at the point where that container was invoked.

It does not stop execution, nor does it re-execute exceptions or pause after every activity (like Step

Into or Step Over).

🔍Visual Confirmation from the Image:

The "Step Out" button is highlighted in red, indicating it’s active and available during debugging.

It is grouped alongside "Step Into" and "Step Over," all part of debug control options.

🔍Use Case:

Suppose you're debugging a workflow and step into an invoked file or a "Then" branch. If everything

looks fine, you can use Step Out to quickly exit and return control to the parent workflow without

stepping through every line.

UiPath Documentation Reference:

Debugging in Studio – UiPath Docs

In UiPath's Document Understanding Framework, UiPath Document OCR is recommended as the

initial OCR engine for processing documents. This OCR option is optimized for extracting text from a

wide variety of document types and provides good accuracy with structured, semi-structured, and

unstructured documents. It is designed to work seamlessly within the UiPath Document

Understanding process and is highly compatible with other UiPath activities and models, making it a

preferred choice for starting document processing in most projects.

For more details, refer to:

UiPath Document Understanding Framework: UiPath OCR Engines

UiPath Document OCR: UiPath OCR Guide

Reference: UiPath Integration Service Triggers

Comprehensive and Detailed Explanation From Exact Extract:

ML models are best suited for complex, semi-structured or unstructured documents where rules or

templates can't handle layout variability. For example, invoices from many vendors with different

formats are ideal for ML.

In contrast, fixed-format documents are better handled with regex, form, or template-based

extractors.

UiPath Documentation Reference:

Choosing the Right Extractor – Document Understanding

In UiPath Document Manager, for string fields, the available options for scoring include:

Exact match: This checks whether the extracted string exactly matches the expected value.

Levenshtein: This method computes the "distance" between two strings, which is the number of

single-character edits (insertions, deletions, or substitutions) required to change one string into the

other. It is used to assess the similarity between the extracted string and the expected value.

These scoring methods help evaluate the accuracy of string extraction in the document

understanding process.

For more details, refer to:

UiPath Document Understanding Framework: String Field Scoring

Levenshtein Distance in UiPath: Scoring String Fields

The End Process is the final stage of the Document Understanding Process, which is a fully functional

UiPath Studio project template based on a document processing flowchart. The End Process is

responsible for setting the queue transaction status, logging the results, and performing any post

processing or cleaning actions if needed. The End Process sets the queue transaction status as

Successful if the document was processed without any exception, and as Failed if an exception

occurred, either a Business Exception (such as invalid data) or a System Exception (such as network

failure). The End Process also adds the extracted data and the validation status as output arguments

to the queue transaction. The End Process also logs the processing statistics, such as the number of

documents processed, the number of exceptions, the average processing time, and the accuracy

rate.🔍The End Process also performs any post processing or cleaning actions, such as deleting

temporary files, closing applications, or sending notifications1.

Reference:🔍1:🔍Document Understanding Process: Studio Template

To iterate through all Microsoft Word documents in a local folder using the For Each File in Folder

activity, you should use the filter option "*.doc*". This filter utilizes the asterisk (*) wildcard to match

any number of characters, effectively capturing both .doc and .docx file extensions.

UiPath Documentation

In the Filter by field of the activity, entering "*.doc*" ensures that the iteration includes all files with

names ending in .doc or .docx, which are standard extensions for Microsoft Word documents.

Other options are incorrect because:

B . Microsoft Word: This is not a valid filter pattern.

*C . " doc"**: This pattern looks for files with names ending in " doc" and does not account for file

extensions.

*D . " doc, *docx"**: This is not a valid filter pattern; multiple patterns should be separated by

semicolons (e.g., "*.doc;*.docx").

Therefore, the correct filter to use is "*.doc*".

Comprehensive and Detailed Explanation From Exact Extract:

The recommended practice in Communications Mining is to train both labels and general fields

simultaneously. This ensures the system learns the relationships and intent expressions effectively.

This approach helps improve the overall model accuracy by leveraging training signals from both

classification and field extraction.

UiPath Documentation Reference: UiPath Communications Mining Documentation – Labeling

Strategy

Comprehensive and Detailed Explanation From Exact Extract:

Processes that undergo frequent business logic changes require frequent updates to automation

scripts, resulting in high maintenance effort and potential breakdowns in unattended execution.

Stable, rules-based processes are preferred for long-term, low-maintenance automation.

UiPath Academy Reference:

RPA Developer Foundation – “Process Assessment and Selection” Module

The correct execution order of the Document Understanding template stages is:

Taxonomy

Digitize

Classify

Extract

Extraction Validation

Export

Comprehensive and Detailed The Document Understanding template stages are based on a

document processing flowchart that follows these steps:

First, you need to define the🔍Taxonomy🔍of the document types and fields that you want to process

and extract information from.🔍This is done using the Taxonomy Manager in UiPath Studio1.

Next, you need to🔍Digitize🔍the input documents, which can be in various formats such as PDF, image,

or text.🔍This is done using the Digitize Document activity, which converts the documents into a

machine-readable format and performs OCR if needed2.

Then, you need to🔍Classify🔍the digitized documents into the predefined document types in your

taxonomy.🔍This is done using the Classify Document Scope activity, which can use various classifiers

such as Keyword Based Classifier, Machine Learning Classifier, or Intelligent Form Extractor3.

After that, you need to🔍Extract🔍the relevant information from the classified documents based on the

fields in your taxonomy. This is done using the Data Extraction Scope activity, which can use various

extractors such as Regex Based Extractor, Machine Learning Extractor, or Form Extractor.

Next, you need to perform🔍Extraction Validation🔍to review and correct the extracted information,

either manually or automatically. This is done using the Present Validation Station activity, which can

use either the Validation Station or the Action Center for human-in-the-loop validation.

Finally, you need to🔍Export🔍the validated information to the desired output location, such as a file, a

database, or a queue. This is done using the Export Extraction Results activity, which can use various

exporters such as Excel Exporter, CSV Exporter, or Queue Item Exporter.

Reference:

UiPath Studio - Taxonomy Manager

UiPath Activities - Digitize Document

UiPath Activities - Classify Document Scope

Reference: UiPath Dictionaries

According to the UiPath documentation, a dataset is a folder of storage containing arbitrary sub-

folders and files that allows machine learning models in your project to access new data points. You

can edit a dataset’s name, description, or content from the Datasets > [Dataset Name] page, by

clicking Edit dataset. However, you can only edit a dataset if it is not currently being used in an active

pipeline. A pipeline is a sequence of steps that defines how to train, test, and deploy a machine

learning model. If a dataset is being used in an active pipeline, you will see a lock icon next to it,

indicating that it cannot be edited. You can either wait for the pipeline to finish or stop it before

editing the dataset.

Reference:

AI Center - Managing Datasets

AI Center - About Datasets

AI Center - About Pipelines

The Document Understanding Process uses two types of synchronization mechanisms to prevent

multiple robots from writing in a file at the same time: file locks and queues. File locks are used to

ensure that only one robot can access a file at a time, while queues are used to store the information

extracted from the documents and to avoid data loss or duplication. The process uses the following

activities to implement these mechanisms:

File Lock Scope: This activity creates a lock on a file or folder and executes a set of activities within it.

The lock is released when the scope ends or when an exception occurs. This activity ensures that only

one robot can read or write a file or folder at a time, and prevents other robots from accessing it until

the lock is released.

Add Queue Item: This activity adds an item to a queue in Orchestrator, along with some relevant

information, such as a reference, a priority, or a deadline. The item can be a JSON object, a string, or

any serializable .NET type. This activity ensures that the information extracted from the documents is

stored in a queue and can be retrieved by another robot or process later.

Get Queue Items: This activity retrieves a collection of items from a queue in Orchestrator, based on

some filters, such as status, reference, or creation time. The items can be processed by the robot or

passed to another activity, such as Update Queue Item or Delete Queue Item. This activity ensures

that the information stored in the queue can be accessed and manipulated by the robot or process.

Reference:🔍Document Understanding Process: Studio Template,🔍File Lock Scope,🔍Add Queue Item,

[Get Queue Items]