UiPath-ADAv1 API-Based Automation Practice Question
You are automating an API process that involves several sequential calls where the second request requires an ID generated by the first. What is the most efficient way to manage this data flow?
⚠ Common exam trap
Candidates often overcomplicate the process by writing intermediate data to local text or CSV files instead of simply passing variables directly through the workflow memory.
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
✓
Store the ID in a variable and pass it to the next HTTP Request.
Storing the response from the first API call in a variable is the most efficient way to maintain data flow. By parsing this variable and extracting the required ID, it can be passed as an argument or variable into subsequent HTTP Request activities. This approach minimizes memory footprint and keeps the workflow clean, maintainable, and easy to debug compared to writing data to temporary files or global state objects.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Write the first response to a CSV file and read it in the next step.
Why it's wrong here
File I/O operations are significantly slower and introduce unnecessary disk latency into the automation. They also create potential issues with file locks or access permissions. Using memory-based variables for data passing is the standard, high-performance approach for API orchestration within a single workflow execution context.
- ✓
Store the ID in a variable and pass it to the next HTTP Request.
Why this is correct
Variables are the standard mechanism for passing data between activities in a workflow. This approach is efficient, secure, and preserves the execution context. By extracting the ID into a variable, the automation can dynamically update the subsequent request's body or URL parameter without incurring any performance penalties or I/O overhead.
- ✗
Hardcode the ID into the second activity during development.
Why it's wrong here
Hardcoding values prevents the automation from being dynamic. If the API returns a different ID each time, a hardcoded value will cause the second call to fail consistently. Automation must be data-driven, using variables to handle dynamic output from previous steps to ensure the process works for different scenarios.
- ✗
Re-run the first request inside the second activity's scope.
Why it's wrong here
Re-running requests is redundant and wasteful, increasing the processing time and potentially hitting API rate limits. It is poor practice to make the same call multiple times if the data is already available. The architecture should be optimized to fetch data once and reuse it throughout the remaining workflow steps.
About these practice questions
Courseiva writes every UiPath-ADAv1 question from scratch — 285 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.