Book Image

Microsoft Power BI Data Analyst Certification Guide

By : Orrin Edenfield, Edward Corcoran
5 (1)
Book Image

Microsoft Power BI Data Analyst Certification Guide

5 (1)
By: Orrin Edenfield, Edward Corcoran

Overview of this book

Microsoft Power BI enables organizations to create a data-driven culture with business intelligence for all. This guide to achieving the Microsoft Power BI Data Analyst Associate certification will help you take control of your organization's data and pass the exam with confidence. From getting started with Power BI to connecting to data sources, including files, databases, cloud services, and SaaS providers, to using Power BI’s built-in tools to build data models and produce visualizations, this book will walk you through everything from setup to preparing for the certification exam. Throughout the chapters, you'll get detailed explanations and learn how to analyze your data, prepare it for consumption by business users, and maintain an enterprise environment in a secure and efficient way. By the end of this book, you'll be able to create and maintain robust reports and dashboards, enabling you to manage a data-driven enterprise, and be ready to take the PL-300 exam with confidence.
Table of Contents (25 chapters)
1
Part 1 – Preparing the Data
6
Part 2 – Modeling the Data
11
Part 3 – Visualizing the Data
15
Part 4 – Analyzing the Data
18
Part 5 – Deploying and Maintaining Deliverables
21
Part 6 – Practice Exams

Define the tables

As mentioned in the introduction, once you've acquired your data, cleaned it, and organized it, you can start to model it. Usually, a simpler model will perform better than a complicated model. As every situation is different, there are a few hard-and-fast rules for simplifying your data model. This is good news for you, as you will encounter a few questions about this and most are common sense.

When creating tables, what you leave out can be as important as what you keep. Typically, if a column or table is not necessary for a visual or a calculation, do not include it in the model. If you bring in more tables and columns than you need, not only will the reports based on the model be slower but it can also lead to confusion. If you import all the tables from your database, report creators will have to search through all the tables to find the columns they need to report on. This can lead to frustration, especially if the end result is a slow-running report...