Are you Ready for Microsoft Power

Platform Fundamentals (PL-900)? Self-

assess yourself with “Whizlabs FREE TEST”

Microsoft Power Platform

Fundamentals (PL-900)
Quick Bytes for you before the exam!

The information provided in WhizCards is for educational purposes only; created in our efforts to
help aspirants prepare for the Microsoft Power Platform Fundamentals (PL-900) certification exam.
Though references have been taken from Microsoft documentation, it’s not intended as a
substitute for the official docs. The document can be reused, reproduced, and printed in any form;
ensure that appropriate sources are credited and required permissions are received.
 Index
Describe the Business Value of Power Apps …………..03
• Describe the Business Value of Power Platform Services…..04 Demonstrate the Capabilities of Power Apps…………..24
• Describe the business value of extending business solutions by • Identify common Power App Components…..25
using Power Platform………06 • Use cases for formulas…………26
• Describe Power Platform Administration • Build a Basic Canvas app……..27
and Security……..07 • Describe Power App Portals…………29
• Steps to Manage Power Apps…………08 • Build a Basic Model Driven App…………30
• Create Users and Assign Security Roles…………09
• Environments Overview……..10
• Data loss Prevention Policies and Compliance and Data
Privacy…….11
• Accessibility Standards and Guidelines……12 Demonstrate the Capabilities of Power Automate………….31
• Identify common Power Automate Components…….32
Identify the Core Components of Power Platform…………..13 • Build a Basic Flow……….34
• Describe Microsoft Dataverse…..14
• Describe Connectors…….16
• Describe AI Builder…….18
Demonstrate the Capabilities of Power Virtual Agents……..35
• Describe Power Virtual Agent Capabilities………36
Describe the Capabilities of Power BI…………..19 • Build and Publish a Chatbot…………39
• Identify Common Power BI Components…..20
• Connect to and Consume Data…….21
• Share a Dataset…….22
• Build a Basic Dashboard using Power BI…23

02
Describe the Business Value of
Power Apps

03
 Describe the Business Values of Power Platform Services

Power BI Power Automate

Collection of software services, apps, and connectors that Include powerful workflow automation directly in
work together to turn your unrelated data sources into your apps with a no-code approach that connects to
coherent, visually immersive, and interactive insights. hundreds of popular apps and services.

Power Apps Power Virtual Agents

Power Apps is a suite of apps, services, connectors, and

data platform that provides a rapid application Easily build chatbots to create rich conversational
development environment to build custom apps for your experiences with your customers and employees—
business needs. This Low-code/no-code tools allow citizen no coding required
developers to develop business workflow applications via
drag-and-drop interfaces.

04
 Describe the Business Values of Power Platform Services

Microsoft Dataverse Flow in Power Automate

Dataverse lets you securely store and manage data that are Cloud flows: Flow automatically be triggered either
used by business applications. Data within Dataverse is automatically, instantly, or via a schedule.
stored within a set of tables. A table is a set of rows and
columns. Desktop flows: Desktop flows are used to automate
tasks on the Web or the desktop.
Connectors
Business process flows: A streamlined user
Data is stored in a data source, and you bring that data into experience that leads people through their
your app by creating a connection. The connection uses a organization’s processes has been defined for
specific connector to talk to the data source. interactions that need to be advanced.

05
 Describe the business value of extending business solutions by using Power Platform

Out of the box tenant-wide analytics Usage reporting: Power Apps and Power Automate

Maker activity reporting: Power Apps and Power Inventory reporting: Power Apps and Power
Automate Automate

06
 Describe Power Platform Administration and Security

Security Model Dependencies between Action Rights

Action Access rights required

Create a record and be the
CREATE, READ
record owner
➢ Least Privilege: SHARE. This right is required
Provide users with access only to the appropriate levels of by the person doing the
information that are required to do their jobs. share operation.
➢ Categorize users by role and restrict access based on those
roles. Share a record READ. This right is required
➢ Support data sharing so that users and teams can be granted by the person doing the
access to records that they do not own for a specified share operation and the
collaborative effort. person with whom the
➢ Prevent a user's access to records the user does not own or record is being shared.
share.
Assign a record ASSIGN, WRITE, READ
Append to a record WRITE, READ, APPENDTO
Append a record WRITE, READ, APPEND

07
 Steps to Manage Power Apps

In the navigation pane, select Environments,

Sign into the Power Platform admin center.
select an environment with resources, and
then select the Power Apps resource.

Select an app to manage. Select your desired action, e.g., Share and
Delete.

08
 Create users and Assign Security Roles

Create a Security Account Assign a Security Role to the User

➢ Security roles control a user's access to data through

a set of access levels and permissions. The
You use the Microsoft 365 combination of access levels and permissions
admin center to create user included in a specific security role limits the user's
accounts for every user who view of data and the user's interactions with that
needs access to apps created data.
using Power Apps and ➢ You can assign more than one security role to a user.
customer engagement apps in The effect of multiple security roles is cumulative,
Dynamics 365. The user which means that the user has the permissions
account registers the user with associated with all security roles assigned to the
the Microsoft Online Services user.
environment. ➢ Security roles are associated with business units. If
you've created business units, only those security
roles associated with the business unit are available
for the business unit users. You can use this feature
to limit data access to data owned by the business
unit.

09
 Environments Overview

An environment is a space to store, manage, and share your Environment scope:

organization's business data, apps, and flows. Each environment is created under an Azure Active
Directory (Azure AD) tenant, and users within that tenant
can only access its resources.

Environment permissions
1. Environment Admin: Perform all administrative actions
Types of environments
on an environment
Production, Default, Sandbox, Trial, Developer, Microsoft
2. Environment Maker: Create resources within an
Dataverse for Teams
environment, including apps, connections, custom
connectors, gateways, and flows using Power Automate.

The default environment:

A single default environment is automatically created by
Power Apps for each tenant and shared by all users in that
tenant. Whenever a new user signs up for Power Apps,
they're automatically added to the default environment’s
Maker role

010
 Data loss Prevention Policies and Compliance and Data Privacy

Data loss prevention (DLP) policies: Compliance and Data Privacy

➢ Trust Center:
Centralized resource for obtaining information on Microsoft’s
Ability to create and enforce policies that define which portfolio of products
connectors can access and share business data. The ➢ Data Location
policies that define how data can be shared are referred ➢ Data Protection:
to as data loss prevention (DLP) policies. TLS 1.2 (or higher) is required for accessing the server
Compliance and data privacy endpoints.
➢ Resources to manage GDPR Compliance

011
Accessibility Standards and Guidelines

Layout and Color

Keyboard Support

Screen reader support

Control type and structure

Multimedia

Working with Signatures

012
Identify the Core Components of
Power Platform

013
 Describe Microsoft Dataverse

Dataverse Database Table Relationships

Relationship Type Description

➢ Tables are used to model and manage business A table relationship where one table row for
data. the Primary table can be associated with many
other Related table rows because of a lookup
➢ Dataverse provides standard tables by default.
column on the related table.
Following best practices these are designed to
capture the most common concepts and 1:N (One-to-Many) When viewing a primary table row, you can see
a list of the related table rows associated with
scenarios within an organization.
it.
➢ Columns define the individual data items that
can be used to store information in a table. In the Power Apps portal, the Current table
represents the primary table.
A table relationship that depends on a special
Relationship table is sometimes called an
Intersect table. Many rows of one table can be
N:N (Many-to- related to many rows of another table.
Many)
When viewing rows of either table in a N:N
relationship, you can see a list of any other
table rows related to it.

014
 Describe Microsoft Dataverse

Table Relationships Behaviour Business Rule

➢ Can define a business rule for a specific model-driven form
Preserve data integrity ➢ Canvas apps cannot have a business rule applied to a specific
form, but it enforces when interacting with data
➢ Prevent deleting the primary table so that the related
table rows can be reconciled, perhaps associating them ➢ Maintain business logic at the data layer instead of the app layer
with a different primary table.
➢ Better control of data
➢ Allow the related tables to be deleted automatically with ❖ Confirm data follow business logic
the deletion of the primary table row. ❖ Rule are tied to the data, not the app

Metadata means data about data:

Common Data Model: In Dataverse, the metadata is a collection of tables.

Common Data Model includes a set of standardized, extensible ❖ Existing metadata: Dataverse comes with several standard
data schemas that Microsoft and its partners have published. This tables that support core business application capabilities.
collection of predefined schemas includes entities, attributes,
semantic metadata, and relationships. ❖ Limitations on creating metadata items: Within each table,
there is an upper limit on the number of columns you can
create. This limit is based on the technical limitations on
the amount of data stored in a database table row.

015
 Describe Connectors

Tabular Data
Types of Data Actions
sources
Function-based Data

Using a blank custom

Time Based Types of Custom connector
Types of Triggers Connectors
Use a webhook as a trigger
Event Based for Azure Logic Apps and
Power Automate

From an OpenAPI definition From a Postman collection

016
 Describe Connectors

Power Automate
License by Platform
Licensing
Power Apps

Run Specific Apps: Up to Run Unlimited Apps Per-User Plan

2 specific apps

Per-User Plan with

attended RPA
The licensing comes in a single
Publish and share an App pricing model – 2000 session
buckets per month.
Per Flow Plan

017
 Describe AI Builder

Business Value: Low code platform enables organizations to analyze data, act on it through
applications, and automate business processes.

Types of Model Form Processing Prediction Model

Model

❖ Business card Reader:

Scan business cards. Extract contact
information from pictures of business ❖Define fields and tables to extract ❖ From two available options (binary)
cards or your mobile phone’s camera ❖Analyze ❖ From multiple possible outcomes
❖ Detection Model ❖Tag documents ❖ Where an answer is a number
Model domain: ❖Tag all documents across all
Common objects, Objects on retail collections
shelves, Brand logo

018
Describe the Capabilities of
Power BI

019
 Identify Common Power BI components

Power BI Desktop
Filters in Power BI reports
Element Power BI Service

Power BI Mobile
Automatic Filters

Workspaces are created on capacities. Workspaces are

Workspace places to collaborate with colleagues to create collections Manual Filters
of dashboards, reports, and paginated reports.
Include/Exclude Filters
✓ My workspace
✓ Workspaces : share content with colleagues
Drill-down Filters
✓ App : Collection of dashboard and reports

Datasets Cross-drill Filters

Single source of data

Reports One or more pages of visualization Drill-through Filters

✓ Reading view
✓ Editing view URL Filters

Dashboards: Pass-through Filters

Single canvas that contains zero or more tiles and widgets

020
 Connect to and Consume Data

Data Modeling and Visualizations

Modeling View:
View and work with complex datasets that contain many tables.

Shape Data

Adjust Data
Steps to shape and combine data in Power BI Desktop
Combine Data

Combine Queries

Merging: When you have one or more Appending: When you have additional rows of
columns that you’d like to add to data that you’d like to add to an existing query,
another query, you merge the queries. you append the query.

021
 Share a Dataset

You start by creating a .pbix file with a data Publish the .pbix file to a new workspace
model in Power BI Desktop experience in the Power BI service.

You can also publish an app from this workspace. Limitation and considerations: Use row-level
When you do, on the Permissions page, you security (RLS) in the dataset so that each
specify who has permissions and what they can person's credentials determine which data
do. they can access.

022
 Build a Basic Dashboard using Power BI

Share and collaborate with colleagues in Power BI

Create Groups, which you can use as a

Publish your reports from Power BI Desktop security model to identify a subset of users
to the Power BI service. who have access to dashboards, reports, and
datasets that you create.

Create Apps that package a dashboard, report,

and dataset to send to your colleagues, who can Publish to the web so that live reports can be
use the content pack as a starting point and embedded in a webpage.
further enhance it.

023
Demonstrate the Capabilities of
Power Apps

024
 Identify common Power App Components
Reusable components
Types of Power Apps Canvas Component libraries: Reusable building blocks for canvas apps

Limitation
Canvas Apps Model-driven apps Portal Apps
1. Can't save data sources, forms, and data tables with
Design the app by A component-focused Externally facing components
dragging and dropping approach to app website.
2. Collections in components are not supported.
elements onto a development. The layout
canvas is determined by the 3. Can't insert a component into a gallery or a form
user of the component
4. A master instance of a component is a local master and
add to the app.
scoped to the app. If the user changes a master instance,
only copies of the app’s component will reflect the
change.
Manifiest
5. Can't package media files when user import a component

Code component 6. Components don't support the UpdateContext function

consists of 3 Component Implementation
elements: Power Apps Component Framework (PCF) components
Empowers professional developers and app makers to create
Resources code components for model-driven and canvas apps.

025
 Use Cases for Formulas

Elements

Functions take parameters, perform an operation, Signals return information about the environment.
and return a value.

Named operators, such as ThisItem and Self, provide Enumerations return a pre-defined constant value
access to information from within a container.

026
 Build a Basic Canvas App
Display
Cloud Service
Cloud Service Modify
Types of Data Sources
Elements of Table
Local

Elements of Table Local

Records Fields Columns Table Collections

➢ Created dynamically with the Collect

function.

A table comprises ➢ Allow duplicate records

A column refers one or more
An individual piece
to the same field records, each with ➢ Users can use the SaveData and
of information in a
for one or more multiple fields with LoadData functions to save and
record
records in a table consistent names reload a copy of the collection.
across the records.
➢ Users can use the Export and Import
controls to save and reload a copy of
the collection to a file that the user
can interact with.

027
 Build a Basic Canvas App

Standard Azure AD Integrated

Types of Connectors Connectors Security and
Open-standard authorization (OAuth)
Types of
Custom Connectors Authentication SQL username and password authentication
Windows Authentication

• Everyone in organization
Publish and share an App Share
• Share an app with a list of aliases, friendly names, or a
combination of those.
Identify the live version: Live version is • Can't share an app with a distribution group in your
Publish
organization
published for everyone with whom the
app is shared.

Co-owner
Limitation: Regardless of permissions, no two people can edit an app at the same time. If one person
opens the app for editing, other people can run it but not edit it.

028
 Describe Power App Portals

Portal Templates Security

Community portal Common identity providers for portals

Customer self-service portal Open registration: Least restrictive sign-up
configuration
Employee self-service portal
• The portal allows a user account to be
Partner portal registered by providing a user identity.
Customer portal • Require users to provide an invitation code or
valid email address to register with the portal.
Portal from bank

029
 Build a Basic Model-Driven App

Approach Build Blocks Security Role

Data
▪ Relationship
Logic
Step 1 ▪ Business process flow
Model the business data ▪ Workflow
▪ Consider metadata-driven ▪ Actions
architecture ▪ Business rule
▪ Consider the structure of ✓ To set field
data stored in Data verse requirements, hide or
Step 2 show fields, validate
Define business processes data.
Step 3 • Flows
Build the app Visualization
• Chart
▪ Dashboard
▪ Embedded Microsoft
Power BI

030
Demonstrate the Capabilities of
Power Automate

31
 Identify common Power Automate Components

Types of Flows Connectors

Desktop
DesktopFlows/
Flows/
Fields
Cloud Flows Robotc Business Process Fields
Cloud Flows
Cloud Flows RoboticProcess
Process Flows
Actions Triggers Custom Connectors
Automation
AutomationFlows
Flows

Automated flows: Provide a Polling Triggers:

Create an streamlined user Call service at a
automation that is experience that specified To support more
triggered by an leads people frequency to tailored
event through the check for new scenarios, users
Automate tasks
Instant flows: processes their data can build custom
on the Web or
Start an organization has Push Triggers: connectors with
the desktop
automation with a defined for Listen for data on their own triggers
click of a button interactions that an endpoint, wait and actions.
Scheduled flows: need to be for an event to
Schedule an advanced to a occur.
automation conclusion

32
 Identify common Power Automate Components

Steps to create
Flow Controls
approval flow

1. Create an automated cloud flow

Switch 2. Add a trigger

3. Add a profile action (Using Get my profile (V2) connector)
4. Add an approval action
5. Add a condition
Do until
6. Add an email action for approvals (Using Send an email (V2) connector
7. Add an update action for approved requests
8. Add an email action for rejections
Apply to each
9. Add update action for rejected requests

33
 Build a Basic Flow

Creating a Use Data Export

Flow Operations

➢ Instant flows:
Creating a button ➢ Use the compose action
➢ Automated: ➢ Use the join action Export to a package:
e.g.
➢ Event Trigger ➢ Use the select action
Send the resulting zip
➢ Scheduled ➢ Use the filter array action file to a co-worker in
➢ Use the create CSV table the same tenant to
➢ Time zone: UTC
import or to someone
➢ Start time format: action in another tenant
YYYY-MM- ➢ Use the create HTML
DDTHH:MM:SSZ
table action

34
Demonstrate the Capabilities of
Power Virtual Agents

14
 Describe Power Virtual Agent Capabilities

Web app User Topics

Use cases Types of Topic
MS Team app System Topics
Limit: Up to 1000
topics in a bot

Publish via PVA portal

Publish Integrate with MS
Chatbots Teams
Add to Teams using App Studio

Node: Entire node is incorrect

Types of errors in topic
checker Field: Field might be missing required data
Expression: Expression might be invalid

36
 Describe Power Virtual Agent Capabilities

Prebuilt entities: The most commonly used Nodes in

stereotype information in real-world dialogs conversation path
Entities
Custom entities: Include domain-specific knowledge
Information unit that Message Nodes After the Last Node
represents a certain type of a
real-world subject

• Go to
• Ask a question
Natural language understanding concept that another topic
• Call an action
means saving an extracted entity to an object • End the
Slot Filling • Show a message
conversation
Landing the extracted entity value into a variable

Add a condition
E.g.: Calling a Power Automate flow: A flow
Actions Conditions
can only be called from a topic located in the
same Data verse environment Branch based on a condition

37
 Describe Power Virtual Agent Capabilities

Trigger Phases A user is likely to type that is related to a specific issue

Authoring Canvas
Phrases

Keywords
Access and update Power Automate flows
directly

Questions

38
 Build and Publish a Chatbot

Create a Publish a Analyze a

Chatbot Chatbot Chatbot

Test chat:
Known issues: ➢ It is for bot authors to test
➢ No access to any how conversation nodes
environments. flow and if there are errors
Analyze bot
when they are creating and
➢ The environment performance and
testing their bot.
doesn't have a usage:
Demo website:
database created.
➢ It lets user share a URL with Review overall analytics
➢ The environment is other members of the for your bots.
created in an team, or other stakeholders
unsupported region. who want to try out the
bot. It's not intended for
production use.

39
 Build and Publish a Chatbot

Analyze a Chatbot

Summary Charts

Total
Total number of sessions within the specified time period.
sessions
Engagement
% of total sessions that are engaged sessions (either resolved, escalated, or abandoned)
rate
Resolution % of engaged sessions that are resolved. (In the end-of-conversation survey, user either does not
rate respond or responds Yes.)
Escalation
% of engaged sessions that are escalated to a human agent.
rate
Abandon
% of engaged sessions that are abandoned. (neither resolved nor escalated after 1 hour)
rate
CSAT Graphical view of the average of CSAT scores for sessions.

40
 Build and Publish a Chatbot

Analyze a Chatbot

✓ Engagement over time chart:

Number of engaged and unengaged sessions over time
✓ Analyze customer satisfaction:
✓ Session outcomes over time chart:
Identify overall trends in customer satisfaction,
Resolved, Escalated, Abandoned. and where satisfaction is falling behind.
✓ Resolution rate drivers chart: ✓ Customer satisfaction drivers:
Topic, Rate, Impact Topic, Engaged sessions, Resolution rate,
✓ Escalation rate drivers chart: Abandon rate, Escalation rate, Avg CSAT,
Impact
Topic, Rate, Impact
✓ Abandon rate drivers chart:
Topic, Rate, Impact

41
 Build and Publish a Chatbot

Analyze a Chatbot

✓ Analyze topic usage:

See how individual topics are doing and how well
they're working at resolving issues.
✓ Analyze session information:
Review and monitor how sessions are doing, including
analytics from the topics triggered during a session

✓ Session Transcript
SessionID, StartDateTime,
InitialUserMessage, TopicName,
ChatTranscript

42
 Build and Publish a Chatbot

Billed Sessions

An interaction between a customer and a bot, and represents one unit of consumption

Reasons for a session end

User ends the chat session No new message for more than 30 minutes, the session is considered closed.
Session is longer than 60
The first message is sent after 60 minutes starts a new session.
minutes
Session has more than 100 A turn is defined as one exchange between a user and the bot. The 101th turn starts
turns a new session.

43