Pass the UiPath Certified Professional - Developer Track UiPath-SAIv1 Questions and answers with ExamsMirror

According to the UiPath documentation portal1, the Export stage of the Document Understanding Framework is the final stage of the document processing workflow, where the extracted data is converted to a dataset or to a customized format, such as Excel, JSON, or XML. The Export stage enables you to easily export data for training ML models, using the Export files dialog box in Data Manager or Document Manager. The Export stage also allows you to export the schema of the fields and their configurations, which can be imported into a different session. The Export stage supports different export options, such as current search results, all labeled, schema, or all. The Export stage also provides validation rules, such as requiring at least 10 labeled documents or pages for each field, and at least one document for each classification option1. Therefore, option A is the correct answer, as it describes the main function and benefit of the Export stage. Option B is incorrect, as it refers to the Data Validation stage, which is the previous stage of the document processing workflow, where a human can review and correct the extracted data using the Validation Station or the Present Validation Station activities2. Option C is incorrect, as it refers to the Classification stage, which is the second stage of the document processing workflow, where the document is classified as one of the predefined document types using the Classify Document Scope activity and a classifier of choice3. Option D is incorrect, as it refers to the Digitization stage, which is the first stage of the document processing workflow, where the text is extracted out of the image document using OCR (Optical Character Recognition) using the Digitize Document activity and an OCR engine of choice.

References: 1 Document Understanding - Export Documents 2 Document Understanding - Data Validation 3 Document Understanding - Classification Document Understanding - Digitization

The Present Classification Station activity is used for classification validation in attended mode. It allows the user to review and correct the classification results of documents using the Classification Station interface. The other options are not suitable for attended mode, as they are either used for creating Action Center tasks (A and C) or for training classifiers (B).

References: Classification Station - UiPath Documentation Portal, Document Classification Validation Overview - UiPath Documentation Portal.

In UiPath AI Center, the platform supports several types of machine learning (ML) models, including:

Out-of-the-box models from UiPath: Pre-built models designed for common automation tasks.

Models from UiPath technology partners: External models developed by UiPath’s partners.

Open-source models: Community-contributed models that can be used and adapted for various use cases.

Custom models: Models that users build and train specifically for their projects using their datasets.

This flexibility in model support ensures that organizations can leverage a wide range of machine learning capabilities to suit different automation needs.

For more details, refer to:

UiPath AI Center Documentation: AI Center Models

Machine Learning Model Types: Types of Models in UiPath AI Center

UiPath provides three types of classifier trainers to optimize document classification: Keyword Based Classifier Trainer, Intelligent Keyword Classifier Trainer, and Machine Learning Classifier Trainer. These trainers are used to teach the system how to categorize documents based on keywords, intelligent learning patterns, or machine learning techniques for more complex classifications.(Source: UiPath Classifier Trainer documentation​

 A project in UiPath AI Center is an isolated group of resources (datasets, pipelines, packages, skills, and logs) that you use to build a specific ML solution. You can create, edit, or delete projects from the Projects page or the project’s Dashboard page. However, you can only delete a project if it does not have any package currently deployed in a skill. A package is a versioned and deployable unit of an ML model or an OS script that can be used to create an ML skill. A skill is a consumer-ready, live deployment of a package that can be used in RPA workflows in Studio. If a project has a package deployed in a skill, you need to undeploy the skill first before deleting the project. This is to ensure that you do not accidentally delete a project that is being used by a skill12.

References: 1: AI Center - Managing Projects 2: AI Center - Managing ML Skills

According to the UiPath documentation, Page Units are the measure used to license Document Understanding products. Page Units are charged based on the number of pages processed by the Document Understanding models, such as extractors, OCR engines, and classifiers. Therefore, applying OCR on a 10-page document consumes Page Units, while the other options do not. The creation of a Document Validation Action in Action Center does not consume any Page Units, as it is a human-in-the-loop activity. Using ML Classifier on a 21-page document does not consume Page Units, as it is a free model. Using Intelligent Form Extractor on a 5-page document with 0 successful extractions does not consume Page Units, as the extractor only charges for successful extractions.

References:

AI Center - AI Units

Document Understanding - Metering & Charging Logic

In UiPath AI Center, versioning of ML packages is an integral part of managing the lifecycle of machine learning models. Each ML package has a major and minor version to track changes. When an ML package is initially uploaded, it is assigned a major version (e.g., 1.0). If a package is retrained via pipelines, it increments the minor version (e.g., from 1.0 to 1.1). This mechanism helps differentiate between user-uploaded packages and those that have been retrained. Only packages that undergo retraining through pipelines modify their minor version, not the major version. Thus, answer D is correct.

(Source: docs.uipath.com on ML Package Management).

According to the UiPath documentation, the recommended number of samples for the classification fields depends on the number of document types and layouts that you want to classify. The more document types and layouts you have, the more samples you need to cover the diversity of your data. However, a general guideline is to have at least 20-50 document samples from each class, as this would provide enough data for the classifiers to learn from12. A large number of samples per layout is not mandatory, as the classifiers can generalize from other layouts as well3.

References: 1: Document Classification Training Overview 2: Document Classification Training Related Activities 3: Training High Performing Models