Microsoft Certified: Fabric Analytics Engineer AssociatePrepare and transform data (20-25%)Hard
A data engineer is developing a Dataflow Gen2 to ingest data from an external REST API. The API requires a specific HTTP header, `X-API-Key`, with a sensitive API key value for authentication. To ensure security and avoid hardcoding the key, the engineer wants to store this key securely and reference it in the Dataflow. Which Microsoft Fabric feature should be used to manage this sensitive credential?
- ADirectly embed the key in the Power Query M formula
- BStore as a parameter in the Dataflow settings
- CStore in a Lakehouse table and query it
- DUse a secure connection in the Fabric portal
Show answer & explanationAnswer & explanation
Correct answer: D. Use a secure connection in the Fabric portal
Microsoft Fabric uses secure connections (managed credentials) in the Fabric portal to store and manage sensitive authentication details like API keys for data sources, allowing them to be referenced securely by Dataflows Gen2.
Why the other options are wrong
- A. Embedding sensitive keys directly in M code is a security risk and not recommended practice.
- B. Parameters can be used, but for highly sensitive credentials like API keys, a secure connection is the best practice for management and encryption.
- C. Storing sensitive information in a Lakehouse table (even if encrypted) is not the primary secure mechanism for managing credentials used by Fabric services themselves.
Fabric Secure Connections
A centralized mechanism in Microsoft Fabric for securely storing and managing credentials for data sources.
- Encrypts sensitive information.
- Reusable across multiple Fabric items.
- Follows security best practices.
Memory trick: Fabric's connections are the vault for your keys.