Had something like this in a mock. Model view (C) is the only spot in Power BI Desktop where you can visually map out tables and relationships, perfect for diagramming a star schema with just the fact and related tables. Not totally ruling out edge cases, but C matches the requirement best.

Noticed a lot of us are split on whether "number of months" means a rolling period or a fixed one. Did the question actually show any filter context hint, like a time slicer? Without that, I'd assume they want the rolling window, so that'd be DAX with DATESINPERIOD. Am I missing something obvious?
Pretty sure B is right. EXPLAIN TABLE just gives you the plan for how the query will run, but it doesn't tell you if OPTIMIZE or VACUUM were used on the Delta table. Official docs and practice tests mention you need to check table history or logs for maintenance status. Anyone tried confirming this in a lab yet?
Nice straightforward question, matches what I've seen in other official practice sets.
Pretty sure it's B, D, and E. Developers need Admin on the pipeline for deployments (B), Contributor for Dev/Test workspaces (E), but only Viewer on Production so they can't accidentally deploy there (D). Option F is a trap since granting Contributor to Production breaks least privilege. Anyone see a reason to include A?
Recommendation from most guides and official docs points to B and C. Vertipaq Analyzer and the specific DMV help analyze memory footprint per column. Anyone prepping, definitely practice with both tools for these scenarios.

You need to reduce the memory used by Model! and the time it takes to refresh the model. Which
two actions should you perform? Each correct answer presents part of the solution. NOTE: Each
correct answer is worth one point.