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

Using deployment pipelines

In software development best practices, you never want to mix development work with work that has been completed, is of a known good quality, and is used for production. To do this, most organizations will have separate environments for development and production. Some organizations will have more environments in the middle, such as specific kinds of testing or preproduction. By securing who can access production environments, it will protect the code or artifacts deployed there from the introduction of software bugs or the running of code that has not been fully tested.

Most organizations will also use these multiple environments to set up specific teams of people who will be dedicated to the function of each environment. For example, only developers creating new artifacts or code will have access to the development environment, only testers will have access to the test environment, and only production operations teams will have access to the production...