Question 758 of 966
Model the datahardMultiple ChoiceObjective-mapped

Quick Answer

The answer is partitioning the fact table by date range. This is the most effective optimization because it enables Power BI to perform query folding, scanning only the relevant partitions when a date slicer is applied, rather than loading and processing all 100 million rows. By physically or logically segmenting the fact table into date-based chunks, you drastically reduce the data scanned in memory, directly cutting that 10-second load time. On the PL-300 exam, this scenario tests your understanding of star schema design and large-scale data reduction techniques—a common trap is choosing a simpler fix like removing unused columns, which helps but doesn’t address the core issue of row volume. Remember the memory tip: “Partition by date to eliminate the wait.” This concept applies to both Import and DirectQuery modes, making it a versatile, exam-relevant strategy for any date-slicer-heavy report.

PL-300 Model the data Practice Question

This PL-300 practice question tests your understanding of model the data. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

You have a Power BI model with a large fact table (100 million rows) and several dimension tables. You need to improve query performance for a report that uses a date slicer. The report currently takes 10 seconds to load. What is the most effective optimization?

Question 1hardmultiple choice
Full question →

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

Partition the fact table by date range.

Partitioning the fact table by date range allows Power BI to perform query folding and only scan the relevant partitions when a date slicer is applied. This reduces the amount of data loaded into memory and processed, directly addressing the 100-million-row fact table and the 10-second load time. Partitioning is a native optimization for large tables in DirectQuery or Import mode when using date-based filtering.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Partition the fact table by date range.

    Why this is correct

    Date partitioning allows incremental refresh and reduces query data.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Remove unused columns from the fact table.

    Why it's wrong here

    This reduces model size but may not improve slicer performance significantly.

  • Increase the Power BI service capacity.

    Why it's wrong here

    May not be feasible or cost-effective.

  • Create an aggregated table that summarizes data at the month level.

    Why it's wrong here

    Aggregations can help, but partitioning is more effective for date slicers.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often choose aggregation (Option D) as a quick fix for performance, but they overlook that the report uses a date slicer requiring day-level granularity, making aggregation inappropriate unless the user is willing to lose detail; partitioning directly addresses the root cause of scanning too many rows.

Detailed technical explanation

How to think about this question

In Power BI, partitioning works by splitting a large fact table into smaller, manageable segments based on a range column (e.g., date). When a query includes a filter on that column, the engine uses partition elimination to skip irrelevant partitions, drastically reducing I/O and memory pressure. This is especially effective in DirectQuery mode where the source database (e.g., SQL Server) can also benefit from partition elimination at the query level, and in Import mode where only the needed partitions are loaded into the VertiPaq engine.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related PL-300 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PL-300 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PL-300 question test?

Model the data — This question tests Model the data — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Partition the fact table by date range. — Partitioning the fact table by date range allows Power BI to perform query folding and only scan the relevant partitions when a date slicer is applied. This reduces the amount of data loaded into memory and processed, directly addressing the 100-million-row fact table and the 10-second load time. Partitioning is a native optimization for large tables in DirectQuery or Import mode when using date-based filtering.

What should I do if I get this PL-300 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This PL-300 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 PL-300 exam.