DP-700 Implement and Manage an Analytics Solution Practice Question
A company is using Git integration in Microsoft Fabric to manage their Lakehouse and Report items. They notice that after a developer committed changes to a branch and synced them to the workspace, certain sensitive metadata files are being tracked in the repository. Which file should be modified in the local Git repository to prevent specific Fabric item metadata from being tracked in the future?
⚠ Common exam trap
Candidates look for Fabric-specific configuration switches inside the workspace portal instead of using standard version control mechanisms like gitignore files.
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
✓
.gitignore
Git integration in Fabric synchronizes item definitions between the workspace and a Git provider. To manage which files are ignored or tracked, standard Git practices apply. This is essential for preventing the leakage of sensitive internal metadata or temporary files that should not be part of the version control history of the analytics project.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
fabric.config
Why it's wrong here
There is no standard file named fabric.config used for Git exclusion in Microsoft Fabric. While Fabric has specific configuration files for items, it relies on standard Git mechanisms to handle file exclusion and ignore patterns within the repository structure during the synchronization process with Azure DevOps or GitHub.
- ✓
.gitignore
Why this is correct
The .gitignore file is the standard mechanism in Git to exclude specific files or directories from being tracked. In Fabric Git integration, adding patterns to this file will prevent the specified metadata or item files from being committed to the repository, thereby maintaining a clean and secure version history.
- ✗
.fabricignore
Why it's wrong here
While some tools use specialized ignore files, Microsoft Fabric's Git integration currently leverages the standard .gitignore file for excluding content. Using a non-standard filename like .fabricignore would result in Git ignoring the instructions, and the sensitive files would continue to be tracked and synced to the remote repository.
- ✗
item.config.json
Why it's wrong here
The item.config.json file contains metadata about a specific Fabric item, such as its display name and type. Modifying this file to attempt to ignore other files is incorrect, as its purpose is to define the item's properties for the Fabric service, not to control Git tracking behavior.
Visual reference
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.