PL-300 Visualize and analyze the data Practice Question
Which THREE of the following are best practices when designing Power BI reports for mobile devices? (Select three.)
⚠ Common exam trap
It's easy for candidates to confuse general report design best practices (like using custom visuals or multiple slicers) with mobile-specific best practices, failing to recognize that mobile constraints require simplification and dedicated layout optimization.
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
✓
Create a dedicated mobile layout view
Option A is correct because Power BI Desktop provides a dedicated Mobile Layout view (View > Mobile Layout) that lets you rearrange and resize visuals specifically for phone portrait orientation without affecting the desktop canvas. Option B is correct because small phone screens and varied lighting conditions make large font sizes and high-contrast colors essential for legibility and accessibility on mobile devices. Option D is correct because limiting each page to roughly 3-5 visuals keeps the mobile layout scannable and avoids excessive vertical scrolling and slow rendering on phones. Option C is not a mobile best practice per se: custom visuals are chosen for analytical capability, not for mobile optimization, and some custom visuals render poorly or are not optimized for small screens. Option E is not recommended because stacking multiple slicers consumes scarce screen space and complicates touch interaction; mobile designs typically favor a single, well-chosen slicer or filter pane instead.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a dedicated mobile layout view
Why this is correct
A dedicated mobile layout view is a Power BI feature that provides a separate phone-optimized canvas (portrait orientation) where you can reorder, resize, and hide visuals specifically for small screens. Unlike automatic reflow, this layout lets you control exactly what appears, ensuring touch-friendly spacing and prioritized content on each page. It is a best practice because it guarantees a deliberate mobile experience rather than a haphazard shrink of the desktop layout.
- ✓
Use large font sizes and high-contrast colors
Why this is correct
Large font sizes (typically 14pt or larger for body text and data labels) combined with high-contrast colors ensure text, numbers, and visual elements remain legible on a smartphone without zooming. Accessibility standards such as WCAG recommend a contrast ratio of at least 4.5:1 for normal text, which is especially important in outdoor or brightly lit mobile viewing. This practice also improves usability for visually impaired users and reduces eye strain during analysis.
- ✗
Use custom visuals for advanced analytics
Why it's wrong here
Custom visuals from AppSource are not repackaged by Power BI's mobile engine, so they often render poorly on small screens, may ignore touch gestures, or fail to load due to heavier rendering requirements. They also increase page load time and can introduce inconsistent theming or accessibility gaps. For best practice, use certified standard visuals that Power BI has compiled with native mobile support; if a custom visual is unavoidable, verify its mobile behavior before publishing.
- ✓
Limit the number of visuals per page to 3-5
Why this is correct
A mobile screen offers limited viewport space, so showing 3 to 5 visuals per page preserves context while avoiding excessive vertical scrolling. More visuals force the user to continuously pan up and down, making comparisons harder and increasing cognitive load. Instead, create drillthrough or tooltip pages for deeper analytics and keep each mobile page to a single key insight, using visual grouping such as tabs to organize multiple metrics.
- ✗
Include multiple slicers for flexible filtering
Why it's wrong here
Slicers are notoriously space-hungry on a thin mobile canvas; placing several slicers on a page can consume the entire available height before any data visual appears. On a small screen, each tap on a slicer is also more error-prone and tedious. Best practice is to leverage the filter pane, or sync slicers to a dedicated filter page in the mobile layout, or implement slicer navigation via bookmarks and buttons that expand only when needed.
Go deeper
Related to this question
About these practice questions
One of 524 original PL-300 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.