UiPath-ADAv1 API-Based Automation Practice Question
Which THREE of the following are valid ways to authenticate an API request in UiPath's HTTP Request activity?
⚠ Common exam trap
Candidates often confuse 'OAuth 2.0' with 'Basic' authentication, or forget that custom headers are a valid way to pass API keys for many modern services.
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
✓
Adding 'Authorization' key to the Headers collection.
Authentication is fundamental to secure API consumption. UiPath supports multiple methods including API keys (passed as headers or query strings), OAuth tokens (retrieved via separate requests), and Basic Authentication (encoded in headers). Knowing these options allows developers to align their automation with the specific security standards defined by the target service provider, ensuring compliance and successful communication during the robot's runtime execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Adding 'Authorization' key to the Headers collection.
Why this is correct
Many APIs require an Authorization header for Bearer tokens or Basic authentication strings. Adding this key-value pair to the Headers collection is the standard way to provide credentials. UiPath treats this collection as standard HTTP headers, ensuring the request is properly authenticated when it reaches the server's security layer.
- ✓
Selecting 'OAuth 2.0' in the activity's Authentication tab.
Why this is correct
The HTTP Request activity provides built-in support for OAuth 2.0, which manages the token retrieval and inclusion process automatically. This simplifies development by abstracting the complex handshake process required to obtain and refresh tokens. It is a preferred method when the API documentation explicitly supports standard OAuth 2.0 flows.
- ✗
Hardcoding credentials into the Endpoint field URL.
Why it's wrong here
Embedding credentials in the URL is a severe security risk and is rarely supported by modern API standards. URLs are often logged in plain text, meaning anyone with access to the logs would see the secret. This practice is universally discouraged in favor of header-based or secure storage approaches.
- ✓
Configuring 'Basic' authentication in the Authentication tab.
Why this is correct
Basic authentication is a common, built-in feature in the HTTP Request activity. By providing the username and password in the designated fields, UiPath automatically handles the Base64 encoding required for the Authorization header. This makes connecting to legacy or simple API endpoints straightforward and secure within the automation project.
- ✗
Writing the password into a plain text file for the API to read.
Why it's wrong here
APIs do not read local files from the machine executing the robot. The API request must contain the authentication information within the HTTP transmission itself. Using an external text file is not a supported authentication mechanism for REST web services and will result in a connection failure.
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.