DP-700 Ingest and Transform Data Practice Question
You need to ingest data from an API into a Fabric Lakehouse. The API requires a token-based authentication refreshed every hour. What is the most efficient way to handle this?
⚠ Common exam trap
Candidates often try to hardcode credentials or use overly complex custom scripts. They overlook the standard, modular pattern of using a Web activity for token retrieval within the pipeline itself.
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
✓
Use a Web activity to fetch the token, then pass it to the Copy activity.
Using a Web activity in a Fabric Pipeline to call the authentication endpoint, followed by storing the token in a secure Azure Key Vault or variable, is the standard pattern. This allows the subsequent Copy activity to dynamically retrieve and use the token. This pattern ensures secure credential management while maintaining the automation required for hourly refreshes in a production data environment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hardcode the token in the Copy activity connection string.
Why it's wrong here
Hardcoding tokens is a major security risk and violates standard security practices. Furthermore, since the token expires every hour, a static value will lead to authorization failures after the first hour, causing the entire ingestion process to fail until a new token is manually updated.
- ✓
Use a Web activity to fetch the token, then pass it to the Copy activity.
Why this is correct
This approach automates the credential lifecycle. By dynamically fetching a fresh token via a Web activity, the pipeline ensures that every run is authenticated properly. Storing the output of the Web activity as a variable allows it to be injected into the Copy activity headers securely.
- ✗
Create a new connection every hour manually.
Why it's wrong here
Manual processes are not scalable or reliable for production data engineering. Requiring hourly human intervention creates a high risk of downtime and operational overhead. Data pipelines must be designed to handle authentication renewals automatically to ensure continuous data flow without human dependency in the pipeline.
- ✗
Configure the API to never expire its tokens.
Why it's wrong here
Authentication tokens are designed to expire for security. Requesting an infinite token is rarely permitted by enterprise APIs due to the immense security risks. Even if possible, it would be an insecure configuration that could lead to unauthorized data access if the credentials were ever compromised.
About these practice questions
One of 152 original DP-700 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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 Microsoft exam blueprint
This DP-700 practice question is part of Courseiva's free Microsoft 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 DP-700 exam.