Practice Test GeeksDP-600 Fabric Practice Test
← All DP-600 Flashcard Decks

Deployment Pipelines and CI/CD Flashcards

7 cards from real DP-600 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Deployment Pipelines and CI/CD flashcards as text

  1. Which Git providers are natively supported for Microsoft Fabric workspace Git integration?

    Answer: Azure DevOps and GitHub

    Fabric workspace Git integration natively supports Azure DevOps Repos and GitHub as source control providers.

  2. What is the purpose of the .platform file found in each item folder of a Fabric Git repository?

    Answer: It stores item metadata such as item type, display name, and logical ID

    The .platform file stores essential item metadata — including item type and logical ID — that Fabric uses to track and identify items during Git sync operations.

  3. When a Fabric workspace is connected to a Git branch for the first time, what happens to existing workspace items?

    Answer: Fabric exports existing workspace items to the Git repository branch

    On initial connection, Fabric exports the current workspace items to the connected Git branch, establishing the initial baseline in source control.

  4. What does the 'Update from Git' operation do in Fabric workspace Git integration?

    Answer: Pulls the latest changes from the connected Git branch and applies them to the workspace

    Update from Git pulls the latest committed changes from the connected branch and synchronizes them into the workspace, updating workspace items accordingly.

  5. What file format does Fabric use to store semantic model definitions in a Git repository?

    Answer: TMDL (Tabular Model Definition Language)

    Fabric stores semantic model definitions using TMDL (Tabular Model Definition Language), a human-readable text format well-suited for version control diffing.

  6. When both the workspace and the connected Git branch have conflicting changes to the same item, how does Fabric resolve the conflict?

    Answer: The user must manually choose to keep either workspace changes or Git changes

    Fabric presents conflicts to the user and requires a manual decision to keep either the workspace version or the Git version; there is no automatic merge for item definitions.

  7. Which of the following is NOT a capability of Fabric workspace Git integration?

    Answer: Scheduling automatic workspace-to-Git syncs on a time-based interval

    Fabric Git sync must be triggered manually or via the REST API; there is no built-in scheduler for automatic periodic synchronization.