Microsoft DP-500 Practice Test - Questions Answers, Page 8

Configuring Azure connections is an optional setting with additional properties that can optionally be set:

* Tenant Level storage, which lets you set a default, and/or

* Workspace-level storage, which lets you specify the connection per workspace

You can optionally configure tenant-level storage if you want to use a centralized data lake only, or want this to be the default option.

Reference: https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflowsazure-data-lake-storage-integration

Tab order is the order in which users interact with the items on a page using the keyboard. Generally, we want tab order to be predictable and to closely match the visual order on the page (unless there is a good reason to deviate).

Note: If you are using the keyboard to navigate in a Power BI report, the order in which you arrive at visuals will not follow your vision unless you set the new tab order property. If you have low or no vision, this becomes an even bigger issue because you may not be able to see that you are navigating visuals out of visual order because the screen reader just reads whatever comes next.

Reference: https://datasavvy.me/2018/12/26/tab-order-enhances-power-bi-report-accessibility/

Themes, contrast and colorblind-friendly colors.

You should ensure that your reports have enough contrast between text and any background colors.

Certain color combinations are particularly difficult for users with color vision deficiencies to distinguish. These include the following combinations:

green and red

green and brown

blue and purple

green and blue

light green and yellow

blue and grey

green and grey

green and black

Avoid using these colors together in a chart, or on the same report page.

Reference: https://docs.microsoft.com/en-us/power-bi/create-reports/desktop-accessibilitycreating-reports

Report accessibility checklist, All Visuals.

* Ensure alt text is added to all non-decorative visuals on the page.

* Avoid using color as the only means of conveying information. Use text or icons to supplement or replace the color.

* Check that your report page works for users with color vision deficiency.

* Etc.

Reference: https://docs.microsoft.com/en-us/power-bi/create-reports/desktop-accessibilitycreating-reports

Using the compute engine to improve performance

Take the following steps to enable workloads trigger the compute engine, and always improve performance:

For computed and linked entities in the same workspace:

Ensure you perform the operations that fold, such as merges, joins, conversion, and others.

For ingestion focus on getting the data into the storage as fast as possible, using filters only if they reduce the overall dataset size. It's best practice to keep your transformation logic separate from this step, and allow the engine to focus on the initial gathering of ingredients. Next, separate your transformation and business logic into a separate dataflow in the same workspace, using linked or computed entities; doing so allows for the engine to activate and accelerate your computations. In our analogy, it's like food preparation in the kitchen: food preparation is typically a separate and distinct step from gathering your raw ingredients, and a pre-requisite for putting the food in the oven. Similarly, your logic needs to be prepared separately before it can take advantage of the compute engine.

Reference: https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflowspremium-workload-configuration

Instead denormalize For Performance.

Even though it might mean storing a bit of redundant data, schema denormalization can sometimes provide better query performance. The only question then becomes is the extra space used worth the performance benefit.

Reference: https://www.mssqltips.com/sqlservertutorial/3211/denormalize-for-performance/