Microsoft Power BI Quiz: Custom Visuals
10 questions · exam conditions
0:00
Custom VisualsQuestion 1 of 10

A company develops an approved custom KPI visual. Hundreds of report authors must be able to discover the visual from Power BI Desktop, and administrators want to manage the approved version centrally rather than distribute a package by email.

What should the Power BI administrator do?

Add the visual to an organizational theme and require authors to import the theme before creating each report.
Publish the visual as an organizational visual and direct authors to the Organizational visuals section when adding visuals.
Store the visual package in a shared workspace and grant all report authors the workspace Contributor role.
Embed the visual in a Power BI template and require every report to be created from that template.
← Back to quizzes

Microsoft Power BI Quiz

Microsoft Power BI Quiz: Custom Visuals

Practice Custom Visuals in Microsoft Power BI with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Custom Visuals, giving you a quick way to practice the rules, question types, and explanations that matter most for Microsoft Power BI.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

A company develops an approved custom KPI visual. Hundreds of report authors must be able to discover the visual from Power BI Desktop, and administrators want to manage the approved version centrally rather than distribute a package by email.

What should the Power BI administrator do?

  1. Add the visual to an organizational theme and require authors to import the theme before creating each report.
  2. Publish the visual as an organizational visual and direct authors to the Organizational visuals section when adding visuals. (correct answer)
  3. Store the visual package in a shared workspace and grant all report authors the workspace Contributor role.
  4. Embed the visual in a Power BI template and require every report to be created from that template.
Explanation: When a question asks how to distribute and centrally manage a custom visual for a large number of report authors, you should immediately think about Power BI's Organizational visuals feature — a purpose-built admin tool for exactly this scenario. The Power BI admin portal allows administrators to upload a custom visual (.pbiviz file) to the organization's private store. Once published, the visual appears under the Organizational visuals tab in Power BI Desktop's "Get more visuals" dialog, making it instantly discoverable to all report authors without any file sharing. Crucially, when the admin updates the visual in the portal, all reports using it reflect the new version — that's the centralized management the question demands. Answer B describes this workflow precisely, making it the correct choice. A is wrong because organizational themes control colors, fonts, and formatting — they cannot package or distribute custom visuals. Attaching a visual to a theme file is not a supported mechanism. C is wrong because storing the .pbiviz file in a shared workspace requires every author to manually download and import it each time. There's no central update mechanism; if the visual is revised, you're back to redistribution by other means. D is wrong because Power BI template files (.pbit) capture data model structure and report layout, not reusable organizational visual definitions. Requiring a template doesn't solve the discovery or central management problem — authors still wouldn't find the visual in Desktop natively. Study tip: On Power BI admin questions, watch for the phrase "manage centrally." It almost always points to the admin portal's Organizational visuals feature, not workspaces or templates.

Question 2

A proposed custom map visual sends location values to a third-party routing service to calculate travel paths. The organization's policy requires a Microsoft-certified visual and prohibits report data from being sent to external services.

How should you evaluate the proposal?

  1. Approve it because Microsoft certification guarantees that any third-party service receiving data is located in the Power BI tenant.
  2. Approve it after configuring an on-premises data gateway, because the gateway prevents a visual from contacting external endpoints.
  3. Reject the design as stated and select an approach that does not require the visual to send data to an external routing service. (correct answer)
  4. Approve it after applying sensitivity labels, because labels encrypt data before a custom visual sends it to an external service.
Explanation: When evaluating a custom visual proposal in Power BI, you need to check it against two independent requirements simultaneously: certification status and data handling behavior. A visual can satisfy one condition while completely violating the other. The organization's policy has two clear rules — the visual must be Microsoft-certified, and report data cannot leave to external services. The proposed visual violates the second rule outright by sending location data to a third-party routing service. No configuration workaround changes that fundamental design. The correct path is C: reject the proposal and find an approach that keeps data internal, such as using a certified visual that performs routing calculations locally or through Power BI's own infrastructure. Choice A is dangerously wrong because Microsoft certification does not guarantee anything about where a visual sends data. Certification verifies code quality and security standards during review, not that all downstream data flows stay within your tenant. These are separate concepts. Choice B misrepresents what an on-premises data gateway does. A gateway bridges your internal data sources to the Power BI service — it controls how data flows into Power BI, not how a custom visual inside a report communicates with external endpoints. It cannot block a visual from making outbound API calls. Choice D confuses sensitivity labels with encryption that would prevent external data transmission. Sensitivity labels can apply protections like encryption to files and content, but they don't intercept or block a visual's runtime network requests to outside services. Study tip: On exam questions about custom visuals, always evaluate both certification and data residency as separate checkboxes. A visual passing one requirement never automatically satisfies the other.

Question 3

A report uses an uncertified custom visual that displays correctly in Power BI Desktop and the Power BI service. Executives must also receive the page through an email subscription and export it to PowerPoint with the visual rendered.

What is the best design decision?

  1. Keep the visual and enable persistent filters, because persistent filters control whether custom visuals appear in exported content.
  2. Replace it with a suitable certified visual or a native visual, and test both required distribution methods before release. (correct answer)
  3. Keep the visual and publish through an app, because app distribution makes every custom visual eligible for static rendering.
  4. Replace the semantic model's storage mode with Import, because custom-visual export support depends primarily on storage mode.
Explanation: When a question involves distributing Power BI content through email subscriptions or PowerPoint exports, you need to think about rendering support — specifically, whether a visual can produce a static image during those export processes. Uncertified custom visuals are not guaranteed to render in exported or subscribed content; they may appear as blank placeholders because Power BI's export pipeline relies on certified or native visuals for static rendering. That's why B is the best decision. Replacing the visual with a certified or native alternative ensures the visual will actually render in both email subscriptions and PowerPoint exports. Equally important is the instruction to test both distribution methods before release — this reflects real-world validation practice and ensures executives receive complete, accurate reports. A is wrong because persistent filters control which filter state is saved and restored for users — they have absolutely no effect on whether custom visuals render in exported content. This is a classic distractor that conflates two unrelated features. C is wrong because publishing through an app is simply a distribution mechanism, not a rendering privilege. App distribution does not grant uncertified custom visuals any special eligibility for static rendering in exports or subscriptions. D is wrong because storage mode (Import, DirectQuery, etc.) governs how data is retrieved and refreshed — it has no bearing on whether a custom visual's rendering engine is supported during export. Conflating data architecture with visual certification is a common trap. Your study tip: whenever you see questions about exports, subscriptions, or email delivery, immediately ask yourself whether all visuals on the page are certified or native — that's the gating requirement for reliable static rendering.

Question 4

A report author plans to use the same custom visual in reports for several brands. Each report applies a different JSON theme. During a pilot, native visuals adopt the brand colors, but some elements of the custom visual retain their original formatting.

What should the report author conclude?

  1. The theme file is invalid, because every visual on a report page must apply all theme settings identically.
  2. The custom visual may expose or interpret formatting properties differently, so theme behavior and required overrides must be validated. (correct answer)
  3. The semantic model is caching the old colors, so refreshing the model will force the custom visual to apply the theme.
  4. The visual is uncertified, because certified custom visuals always implement every native visual theme property automatically.
Explanation: When working with themes and custom visuals in Power BI, you need to understand a fundamental distinction: native visuals are built by Microsoft and are fully integrated with the theming engine, while custom visuals are developed independently and may implement formatting properties in their own way — or not at all. This is exactly what the scenario describes. Native visuals respond correctly to the JSON theme, but the custom visual partially ignores it. This tells you the custom visual's developer controls how (and whether) theme properties are mapped to its internal formatting. Some properties may be exposed, others hardcoded, and others simply not wired to theme support. Answer B is correct because it accurately identifies that custom visual behavior with themes must be tested and may require manual overrides on a per-brand basis — this is standard practice when deploying custom visuals across branded reports. Answer A is wrong because themes do not require every visual to apply all settings identically. There is no such rule, and a theme file is not invalidated by partial adoption from a custom visual. Answer C is a red herring — semantic model caching has nothing to do with how a visual renders formatting properties; the issue is in the visual layer, not the data layer. Answer D is a common trap: certification status confirms a visual meets security and quality standards, but it does not guarantee full implementation of every native theme property. Certified visuals are safer, not necessarily more theme-compatible. Your takeaway: always pilot-test custom visuals against every target theme before deployment. Treat custom visual theme behavior as "assumed incomplete until verified," and budget time for manual formatting overrides.

Question 5

A consultant provides a custom visual as a .pbiviz file rather than through AppSource. The visual will receive customer-level values assigned to its data fields. The consultant states that installing the package is safe because report viewers have only read permission.

What is the appropriate response?

  1. Import the package because read-only report permission prevents custom visual code from processing values supplied by the report.
  2. Import the package after disabling export data, because that setting blocks every possible external request made by custom visual code.
  3. Require a trusted-source and security review before import, because the package contains code that can process data supplied to the visual. (correct answer)
  4. Require viewers to use personal bookmarks, because bookmarks isolate the visual package from the underlying semantic model.
Explanation: When you see a question about custom visuals in Power BI, shift your thinking to security and data trust, not just user permissions. Custom visuals packaged as .pbiviz files contain executable JavaScript code that runs inside the report — meaning they can actively process any data values bound to their fields, regardless of how the report viewer's permissions are configured. This is precisely why C is correct. The consultant's claim that "read permission" makes the package safe is a red flag. Read permission controls what a viewer can do with the report, not what the visual's code can do with the data fed to it. A malicious or poorly written visual could capture, transmit, or expose customer-level data externally. Any .pbiviz from an unverified source requires a trusted-source verification and security code review before import. A is wrong because it conflates report viewer permissions with code execution privileges. The visual's JavaScript runs independently of whether the viewer has read or write access — permission levels do not sandbox the visual's logic. B is wrong on two counts: disabling "export data" only restricts users from manually exporting data through the UI; it does not intercept or block network requests that custom visual code might make programmatically. D is wrong because personal bookmarks are a personalization feature that saves view state (filters, slicers, etc.). They have no relationship to isolating a visual's code from the semantic model data it receives. Study tip: On Power BI security questions, remember that custom visuals are essentially third-party code — treat them like any untrusted executable, and never let claimed user permission levels substitute for source verification.

Question 6

A custom visual meets a report's design requirements, but report pages containing it feel slower than pages using native visuals. The semantic model and measures are identical, and the report will be used with substantially more data after deployment.

What should you do before approving the custom visual?

  1. Use Performance Analyzer with representative filters and data volumes, and compare the visual's query and rendering behavior with alternatives. (correct answer)
  2. Convert all measures used by the visual to calculated columns, because custom visuals render calculated columns without issuing queries.
  3. Increase the report canvas size and reduce page zoom, because these settings lower the number of data points processed by the visual.
  4. Publish the report to Premium capacity immediately, because additional capacity guarantees that custom-visual rendering will match native visuals.
Explanation: When evaluating custom visuals for production use, your primary concern should be performance under realistic conditions — not just whether the visual looks right. Custom visuals are third-party JavaScript components that can vary widely in rendering efficiency, query patterns, and behavior as data volumes scale. This question tests whether you know how to validate a custom visual before approving it for broader deployment. The right approach is A: using Performance Analyzer in Power BI Desktop with representative filters and data volumes. Performance Analyzer captures exactly how long each visual spends on DAX queries versus rendering, letting you compare the custom visual directly against native alternatives. Since the scenario warns of substantially more data post-deployment, testing at scale now is essential — a visual that feels "slightly slow" with sample data can become unusable at full volume. B is wrong because calculated columns don't eliminate query execution — they're stored in the model and still require the visual to request data from the engine. This option confuses storage architecture with rendering behavior and introduces unnecessary model bloat. C is wrong because canvas size and zoom affect the visual's display area, not how many rows the semantic model returns. Data volume is governed by filters, measures, and the visual's data-binding configuration — not canvas dimensions. D is wrong because Premium capacity improves throughput and concurrency, but it doesn't fix an inefficient custom visual. If the visual itself has poor rendering logic, more compute capacity won't eliminate the problem — it just makes the problem more expensive. Your study tip: whenever a question involves custom visuals and performance, think measure and diagnose first — Performance Analyzer is your standard tool before any architectural or infrastructure change.

Question 7

A report developer finds an AppSource custom visual that is free during a trial. The completed report will be distributed to 2,000 external users through Power BI apps. The visual vendor offers several paid plans, and it is unclear whether only authors or also report viewers require entitlements.

What should the developer do before standardizing on the visual?

  1. Assume the Power BI app license covers the visual, because custom visual licensing is inherited from the app's workspace.
  2. Convert the workspace to Premium capacity, because Premium capacity grants unlimited use of all paid AppSource visuals.
  3. Import the visual from a file instead of AppSource, because local import removes the vendor's licensing checks for report consumers.
  4. Review the vendor's author and viewer licensing terms, test the post-trial experience, and include the cost in deployment planning. (correct answer)
Explanation: When a question involves third-party or AppSource custom visuals, your first instinct should be to think about licensing independence — custom visuals are products sold by external vendors, and Power BI's own licensing says nothing about what those vendors require from their customers. That's exactly why D is the right approach. Before committing 2,000 external users to a visual, you must understand whether the vendor charges per author, per viewer, or both. Many AppSource visuals have free tiers that silently degrade or block functionality after a trial — meaning your report consumers could see broken or watermarked visuals without warning. Testing the post-trial experience and factoring the cost into deployment planning protects both the project and the end users. A is a dangerous assumption. Power BI workspace or app licenses govern access to Power BI content, not the commercial terms of a third-party visual vendor. There is no inheritance of licensing between the two systems — they are completely separate. B is a misconception about what Premium capacity does. Premium removes per-user Power BI Pro requirements for viewers, but it grants no special rights over paid AppSource visuals. A vendor's licensing terms apply regardless of whether your workspace is on shared or Premium capacity. C describes a workaround that simply doesn't work as described. Importing a visual from a file rather than AppSource does not bypass the vendor's licensing checks. The visual code itself enforces entitlements — the installation method is irrelevant. As a study tip, whenever you see "AppSource visual" in an exam scenario, treat third-party licensing as a separate, independent concern from Power BI licensing. Never assume one covers the other.

Question 8

A custom visual displays the required data correctly. When a user selects a category in the custom visual, other visuals on the page do not respond. The report author has already configured the page's visual interactions to filter the other visuals.

What is the most likely next step?

  1. Replace the category column with a measure, because only measures can initiate cross-filtering from custom visuals.
  2. Enable bidirectional relationships throughout the model, because custom visuals require bidirectional filtering to make selections.
  3. Verify that the custom visual implements selection and interaction behavior, and choose another visual if that behavior is unsupported. (correct answer)
  4. Add the category to every visual's tooltip field, because shared tooltip fields activate cross-filtering between report visuals.
Explanation: When a custom visual fails to trigger cross-filtering even after visual interactions are properly configured, the issue almost always lives inside the visual itself — not in the report settings. This question tests your understanding of how custom visuals integrate with Power BI's selection and filtering API. Power BI's native visuals automatically participate in cross-filtering because Microsoft builds that behavior in. Custom visuals, however, are developed independently and must explicitly implement the Selection API to broadcast selection events to the report. If a developer didn't include that code, no amount of report-level configuration will make cross-filtering work. That's exactly why C is correct — your next step is to confirm whether the custom visual supports selection behavior, and if not, replace it with one that does. Answer A is wrong because the column-vs-measure distinction has nothing to do with cross-filtering capability. Cross-filtering is driven by visual interactions and the Selection API, not the field type being used. Answer B is a common trap: bidirectional relationships affect how filters propagate through your data model, but they don't control whether a visual can emit a selection event in the first place. The problem here is at the visual layer, not the model layer. Answer D is completely fabricated — tooltip fields have no role in activating cross-filtering between visuals. This is the kind of plausible-sounding distractor the exam uses to test whether you understand actual mechanics. As a study tip, remember the distinction between report-level settings (visual interactions, filters) and visual-level capabilities (Selection API support). When something works at the data level but fails at the interaction level, look at the visual's implementation first.

Question 9

A logistics report must show the relative volume moving from each warehouse to multiple destination regions. Native bar and matrix visuals were tested, but users could not easily follow the source-to-destination relationships. Company policy permits only certified visuals obtained from AppSource.

Which approach should you recommend?

  1. Use a certified flow visual from AppSource, and validate its field mappings and performance with representative report data. (correct answer)
  2. Use an uncertified flow visual from a vendor website, and rely on workspace permissions to address the security requirement.
  3. Use a native matrix with conditional formatting, because native visuals can always reproduce the behavior of custom visuals.
  4. Develop a new custom visual internally, because internally developed visuals are automatically treated as certified by Power BI.
Explanation: When a question combines data visualization requirements with organizational security policy, you need to evaluate both the technical fit and the compliance constraints together — not separately. The scenario calls for a flow-style visual (like a Sankey or chord diagram) to show source-to-destination volume relationships, and the company explicitly requires certified visuals from AppSource. A certified AppSource visual has been reviewed by Microsoft for security, performance, and coding standards, making it the only option that satisfies both needs. Answer A is correct because it selects the right visual type through the right channel, and importantly, it includes the professional step of validating field mappings and performance with real data before deployment. Answer B fails on multiple levels: downloading from a vendor website bypasses AppSource entirely, and uncertified visuals haven't passed Microsoft's security review. Workspace permissions control who can access a report — they don't compensate for an unvetted visual's potential to exfiltrate data or behave unpredictably. Answer C overstates what native visuals can do. Conditional formatting on a matrix can highlight values, but it cannot replicate directional flow diagrams. The question already tells you native visuals were tested and failed to meet user needs, so this answer ignores given evidence. Answer D contains a dangerous misconception: internally developed custom visuals are not automatically certified. Certification requires a formal submission and review process through Microsoft, regardless of who built the visual. As a study tip, watch for Power BI questions that mix visualization choice with governance requirements — the exam frequently tests whether you know that "certified" is a specific Microsoft designation, not a general term for "trusted."

Question 10

A public-sector report must be usable by keyboard-only users and users of screen readers. An AppSource custom visual has the preferred appearance and is marked as certified, but the project team has not tested its keyboard navigation, focus order, or text alternatives.

What should the team do?

  1. Approve the visual based only on certification, because certification guarantees compliance with every organizational accessibility standard.
  2. Disable the visual header, because removing header icons automatically provides screen-reader support for the custom visual's data.
  3. Add alt text to the report page, because page-level alt text makes all controls inside a custom visual keyboard accessible.
  4. Test the visual against the report's accessibility requirements and use an accessible alternative if required interactions are not supported. (correct answer)
Explanation: When a question combines accessibility requirements with custom visuals in Power BI, your focus should be on what certification actually guarantees versus what your team must independently verify. Power BI's AppSource certification confirms that a visual meets certain technical and security standards — but it does not guarantee compliance with every accessibility standard, particularly organization-specific requirements like keyboard navigation, focus order, and screen-reader support. Because the team in this scenario has done zero accessibility testing, the only responsible path is D: test the visual against the report's actual accessibility requirements and substitute an accessible alternative if it falls short. Accessibility compliance is a shared responsibility between the tool and the implementation team. Option A is the most tempting trap. "Certified" sounds authoritative, but certification is a baseline quality bar, not a blanket accessibility guarantee. Never assume certification eliminates the need for targeted accessibility testing. Option B misrepresents what disabling the visual header does. The visual header controls the toolbar icons (focus mode, more options, etc.), but removing those icons has no bearing on how a custom visual's internal content or interactions behave for screen-reader users. Option C confuses scope. Page-level alt text describes the page to a screen reader as a whole — it cannot retrofit keyboard accessibility or focus management into the internal components of a custom visual. Those capabilities must be built into the visual itself. Your study tip: watch for questions that conflate a feature flag or label (certified, alt text, header settings) with full accessibility compliance. In Power BI accessibility questions, always ask — does this feature actually solve the stated problem, or does it only sound related?