UiPath-ADAv1 Orchestrator and Integration Service Practice Question
A developer needs to store a credential that will be used by multiple processes across different folders in Orchestrator. The credential should be accessible to all processes without duplicating it in each folder. Which asset type and scope should the developer use?
⚠ Common exam trap
It's easy for candidates to confuse asset scopes: folder-level assets are isolated, while tenant-level assets are shared across all folders.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A Credential asset defined at the tenant level in Orchestrator.
Tenant-level Credential assets are designed for secrets that must be shared across folders. They are stored securely and can be accessed by any process in the tenant, eliminating duplication. Folder-level assets and local Windows credentials do not provide the required cross-folder accessibility and centralized management.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A Windows Credential Manager entry on each robot machine.
Why it's wrong here
Windows Credential Manager is local to each machine and not centrally managed by Orchestrator. It requires manual setup on every robot and does not provide a single source of truth. While it can store credentials, it lacks the centralized governance, auditing, and cross-folder accessibility that Orchestrator assets provide. This approach does not meet the requirement for shared access across folders.
- ✓
A Credential asset defined at the tenant level in Orchestrator.
Why this is correct
Tenant-level assets are available to all folders within the tenant, making them ideal for shared credentials used by multiple processes across different folders. Defining the credential once at the tenant level avoids duplication and ensures consistent access. Processes in any folder can retrieve the credential using the Get Credential activity, provided they have the necessary permissions.
- ✗
A Credential asset defined at the folder level in each required folder.
Why it's wrong here
Folder-level assets are scoped to a single folder and cannot be shared across folders. Defining the credential separately in each folder duplicates the secret, increasing maintenance overhead and the risk of inconsistent values. This approach does not meet the requirement of a single credential accessible to all processes without duplication.
- ✗
A Text asset defined at the tenant level, storing the password as plain text.
Why it's wrong here
A Text asset stores values in plain text, which is insecure for credentials. Even at the tenant level, using a Text asset for passwords exposes sensitive information. Orchestrator provides the Credential asset type specifically for secure storage and retrieval of passwords. Using a Text asset would violate security best practices and likely fail compliance requirements.
About these practice questions
This UiPath-ADAv1 question is part of Courseiva's 285-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official UiPath exam blueprint
This UiPath-ADAv1 practice question is part of Courseiva's free UiPath certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the UiPath-ADAv1 exam.