DP-600 · Workspace Development Lifecycle
23 cards
Power BI Desktop Projects
-
Quick check
How does a Power BI Desktop project store a report and its semantic model?
AAs a single binary file that tools read as one opaque blob
That describes the `.pbix` format, which is the binary alternative this format replaces.
BAs plain text files in a folder
Right. Readable text in a folder structure is what lets standard diff tools compare versions.
CAs cached data held inside a repository branch until it is published
A project is a local save format, and nothing is cached inside a branch on the author's behalf.
3 / 23
-
Quick check
What do the two main subfolders of a project hold?
ABoth hold JSON page definitions, one copy for authors and one for reviewers
Only the report definition is JSON, and a project keeps no duplicate copies for different readers.
BBoth hold the branches and commits belonging to the repository
Branches and commits live in the repository, not inside the saved project folders.
CThe semantic model folder holds TMDL; the report folder holds `.pbir`
Right. One folder defines tables, measures, and relationships; the other defines pages, visuals, and layout.
6 / 23
-
Quick check
Which Power BI Desktop sequence saves a project?
AFile, then Save as, choosing Power BI Project as the file type
Right. Power BI Desktop then creates the project folder structure along with a `.gitignore` file.
BFile, then Export, then template
Exporting a template produces a reusable report structure without data, not a text-based folder.
CWorkspaces, then Deployment pipelines
That path builds a promotion route between workspaces and saves nothing locally.
9 / 23
-
Keep your progress in the app
That’s 3 of 9 quick checks. In the app they stay answered, and every lesson remembers where you left off.
-
Quick check
The project file type does not appear in Save as. Where is it enabled?
AWorkspace settings, then Git integration
Git integration connects a workspace to a repository in the service and changes no local save option.
BDeployment pipelines, then deployment rules, then the data source option
Deployment rules replace configuration values between stages and have no effect on local file types.
COptions and settings, then Options, then Preview features
Right. The save option is a preview feature, so it is switched on there before a project can be saved.
11 / 23
-
Quick check
What does the `.gitignore` created with a project do?
AIt keeps the model definition files out of every commit
The model definition is the part most worth versioning, so it is not excluded.
BIt excludes cache and local settings files
Right. Those files are machine-specific, so they stay out of version control.
CIt stops the workspace from synchronizing with the repository
Workspace synchronization is configured in the service and is unaffected by a local ignore file.
13 / 23
-
Quick check
Why can a reviewer tell that a change renamed a column rather than altering a visual?
ABecause each table, measure, and relationship is a separate readable text file
Right. Text definitions let ordinary diff tools show exactly which measures, columns, relationships, pages, visuals, or layouts changed.
BBecause the binary report file records the change
A binary file shows that something changed without showing what, which is the problem this format solves.
CBecause comparison icons mark the item orange
Stage comparison icons say an item differs between environments; they do not describe the change.
16 / 23
-
Quick check
A team must add a description to every measure and then review the result as text changes. What fits?
AOpen the binary report file and edit each measure by hand before deploying it
A binary file cannot be batch-edited or read line by line, and deploying produces no reviewable change.
BUpdate the TMDL files with a script, then commit
Right. The model definition supports programmatic editing, and the text changes are then committed.
CChange a deployment rule for the stage, then resave the report from the service
Deployment rules override configuration values between stages; they write nothing into a model.
19 / 23
-
Quick check
Authors work locally and the Fabric workspace must reflect approved commits. Which sequence matches?
AEdit the binary file, deploy to Test, then create a repository
That leaves version history until last, so the readable review the team wanted never happens.
BEdit a deployment rule, save the layout, then clear the local cache
None of those steps produces a reviewed change or brings committed content into the workspace.
CEdit the project locally, commit it to Git, then let the workspace synchronize with the repository
Right. Readable local artifacts, then history and collaboration, then published content that matches the commits.
21 / 23
-
Quick check
Which statement about the project format is correct?
AIt stores definitions as text, so ordinary diff tools can review them
Right. Readable text is the whole reason the format supports code review and scripted edits.
BIt stores one binary file
A single binary file is the `.pbix` alternative, and it is what this format replaces.
CIt stores report pages in the semantic model folder and measures in the report folder
The folders are the other way around: model definitions in one, report definitions in the other.
23 / 23
-
9 quick checks · then the test
In the app, finishing the quick checks opens this lesson’s 10-question test, and the ones you miss come back exactly when you’re about to forget them.
The whole course, on your phone
Lessons you can read, audio you can listen to on the way to work, and practice that remembers what you got wrong.