Limited Time 30% Discount Offer Use Code - off30

PL-100 - Bundle Pack

Actualkey Prepration Latest PL-100 : Microsoft Power Platform App Maker Exam Questions and Answers PDF's, Verified Answers via Experts - Pass Your Exam For Sure and instant Downloads - "Money Back Guarantee".


Vendor Microsoft
Certification Microsoft Certified: Power Platform App Maker Associate
Exam Code PL-100
Title Microsoft Power Platform App Maker Exam
No Of Questions 278
Last Updated November 8,2024
Product Type Q & A with Explanation
Bundel Pack Included PDF + Offline / Andriod Testing Engine and Simulator

Bundle Pack

PRICE: $25

PL-100 : BUNDLE PACK LEARNING TOOLS INCLUDED

Actualkey Products

PDF Questions & Answers

Exam Code : PL-100 - Nov 8,2024
Try Demo
Testing Engine

Offline Test Engine

Exam Code : PL-100 - Nov 8,2024
Try Demo
android testing engine

Android Test Engine

Exam Code : PL-100 - Nov 8,2024
Try Demo
online Exam Engine

Online Test Engine

Exam Code : PL-100 - Nov 8,2024
Try Demo

Skills Measured

Audience profile
The candidate envisions and creates business solutions to simplify and automate tasks and processes for themselves and their team. They understand the data that they are working with, the issues that they need to resolve, and the required processes and app experiences. The candidate may not have formal IT training but is comfortable using technology to solve business problems.

The candidate is self-directed and focuses on solving problems that they encounter as part of their primary job role. They may connect to and use features of apps including Microsoft Power Platform, Microsoft Teams, Microsoft 365 apps and services, and third-party solutions. The candidate has a desire to understand the capabilities and limitations of available tools and understand how to apply them.

Design business solutions (20–25%)
Analyze and visualize data (10–15%)
Create business solutions (60–65%)


Design business solutions (20–25%)
Create a high-level design
Identify existing data sources needed to support a business solution
Describe the expected user experience for targeted devices and describe the differences between Microsoft Power Platform app types
Describe the expected logic and steps that a process will execute
Create a high-level structure for a new data source
Identify Microsoft Power Platform components
Determine the required Microsoft Power Apps app type for a business solution
Determine when to use Microsoft Dataverse for Teams
Map a problem domain to Microsoft Power Platform tools
Identify options for implementing business logic
Describe connectors
Describe uses cases for cloud flows and desktop flows
Describe use cases for chatbots
Design the user interface (UI) for a business solution
Identify opportunities for component reuse
Select UI elements for canvas apps
Identify the model-driven forms and Dataverse views that are needed
Design reporting and visualizations for business solutions
Select reporting options for business solutions including views, Microsoft Power BI visualizations, and dashboards
Define visualizations for Power BI dashboards
Define visualizations for model-driven dashboards
Define visualizations for canvas apps

Analyze and visualize data (10–15%)
Create and consume Power BI dashboards
Create a simple report from an existing dataset by using Power BI Service
Create Power BI dashboards from existing reports
Embed Power BI dashboards and tiles in canvas apps and model-driven apps
Share Power BI dashboards
Describe AI Builder models
Describe use cases for AI Builder
Describe differences between prebuilt models and custom models
Describe the process for training custom models
Use a model from within Microsoft Power Automate or Microsoft Power Apps

Create business solutions (60–65%)
Manage Microsoft Power Platform components during development
Create a publisher in Dataverse
Create a Dataverse solution
Export or import Dataverse solution
Export or import a canvas app or a cloud flow
Add existing apps and flows to a Dataverse solution
Create model-driven apps
Create model-driven apps
Create and configure Dataverse table forms
Create and configure Dataverse table views
Share model-driven apps with other users and groups
Create and configure model-driven dashboards
Create and manage canvas apps
Connect to data sources in canvas apps
Interpret App checker results
Manage versions of canvas apps
Publish canvas apps
Share canvas apps with other users and groups
Build canvas apps screens
Add canvas app assets and components to screens
Create screens for canvas apps
Determine when to use forms, galleries, button, labels, input controls, images, and custom controls
Configure UI elements
Implement Power Fx formulas
Implement collections and variables
Run a cloud flow from a canvas app
Configure Microsoft Dataverse
Create tables and table columns based on a data model
Link tables by using lookups
Describe use cases and capabilities of business rules
Create Dataverse business rules
Describe how Dataverse uses role-based access control (RBAC)
Add table permissions to existing Dataverse security roles
Create Power Automate flows
Describe types of triggers for cloud flows
Create cloud flows
Configure triggers for cloud flows
Configure flow actions
Test a cloud flow and interpret flow checker results
Implement conditional logic for a cloud flow
Create approvals and monitor the approval process by using Power Automate and Teams
Share cloud flows
Create a desktop flow for personal use
Create Microsoft Power Virtual Agents chatbots in Microsoft Teams
Identify use cases and capabilities for chatbots
Create a chatbot that uses topics and trigger phrases
Test a chatbot
Publish a chatbot

Sample Questions and Answeers
 

New Topic: Topic 1, Wide World Importers
This is a case study. Case studies are not timed separately. You can use as much exam time as you
would like to complete each case. However, there may be additional case studies and sections on
this exam. You must manage your time to ensure that you are able to complete all questions included
on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is
provided in the case study. Case studies might contain exhibits and other resources that provide
more information about the scenario that is described in the case study. Each question is
independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your
answers and to make changes before you move to the next section of the exam. After you begin a
new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane
to explore the content of the case study before you answer the questions. Clicking these buttons
displays information such as business requirements, existing environment, and problem statements.
When you are ready to answer a question, click the Question button to return to the question.
Background
Current environment
Sales representatives submit weekly status reports to regional managers. There is no standardized
format for these status reports. The process for managing status reports is challenging.
Wide World Importers has decided to use Microsoft 365, Microsoft Azure, and Power Platform for
future app development. Both Wide World Importers and Tailwind Traders have identical Microsoft
SharePoint and Azure configurations. Both companies use separate tenants.
Requirements
Application
You must create a mobile app to streamline the creation of status reports by sales representatives.
You must make the same app available to Tailwind Traders. The mobile app must meet the following requirements:
Minimize the use of code.
Use formulas and expressions when necessary.
Support a variety of visual layouts.
Use a SharePoint list to store information about regional managers and sales representatives.
Use Azure SQL Database to store other data.
Status reports
Sales representatives must provide a weekly status report for all work processes each Monday.
Representatives must enter the following information for each process:
If a sales representative submits a status report and assigns the At Risk status to a process, the app
must prompt the sales representative to enter a detailed description for the risk. This information
must be emailed to the regional manager. If the category is Work/life balance, the information must
be carbon copied to the human resources department.
If a sales representative does not submit a weekly status report by an agreed upon deadline, the
system must send an email to remind the sales representative.
The app must be able to run both online and offline. If the mobile device on which the app runs is
connected to the internet, the app must immediately submit the status report.
You must display a visual indicator in the app so that sales representatives know whether the app is
offline before submitting reports.
When data is submitted offline, the data must be stored in the app until the app is back online.
Technical
Regardless of the UI layouts, the data recorded must be standardized in the Azure DB tables. You
must use global variables in the app.
Deployment
Before deploying the app to production, you must ensure that the app conforms to Microsoft
accessibility and performance guidelines.
The completed app and all supporting components must be provided to Tailwind Traders.
Tailwind Traders must not be able to make changes to any of the components.
You must use the following version control numbering scheme:
Major: The last two digits of the year the app is packaged
Minor: Two digits that represent the month when the app is packaged
Build: A number that is incremented to represent significant changes to the app
Revision: The incremented revision for a package
New versions of the application must completely replace previous versions of the app.
When identifying versions of the app solution, all dependencies, entities, and user interfaces
components must be identified to avoid any unintentional issues caused by reverting individual
components to a previous version.
Previous versions of the mobile app must be available for roll back purposes.
All versions of software that have been used in production must be retained for five years.
Issues
The mobile app has been live for several months. Eight versions of the app have been released since
the initial version of the app was deployed to sales representatives. You must revert the app to an
earlier version and redesign some features.
User1 often works in a warehouse that does not have internet connectivity. User1 needs to edit an
existing status report and submit a new status report.
Several sales representatives have accessibility restrictions. User2 is visually impaired and cannot see
images. User3 is unable to use a mouse.

QUESTION 1
You need to provide the app to Tailwind Traders.
What should you do?

A. Within Managed Properties, set the value of the Allow customizations option to true. Export the app as a managed solution.
B. Use the Share App feature.
C. Within Managed Properties, set the value of the Allow customizations option to false. Export the app as a managed solution.
D. Within Managed Properties, set the value of the Allow customizations option to false. Export the app as an unmanaged solution.

Answer: C

Explanation:
Scenario: The completed app and all supporting components must be provided to Tailwind Traders.
Tailwind Traders must not be able to make changes to any of the components.
Managed Solution: A managed solution is a finalized solution that can be distributed and installed.
They are created by exporting an unmanaged solution by setting restrictions to prevent any further
customizations. The whole point of Managed is locking down the Component states so they cannot
be edited. Deleting the Managed Solution will remove all its customisations as well as data
contained. Managed Solutions become read only once deployed so they cannot be manipulated.

QUESTION 6
You need to provide all app components of the application to Tailwind Traders.
What should you do?

A. Package the application and flow components into a single solution for export.
B. Run the app checker and flow checker prior to publishing each component for export.
C. Export each component separately but use the same version number for each component.
D. Publish the application and flow solutions at the same time before exporting each one.

Answer: B

Explanation:
Scenario: When identifying versions of the app solution, all dependencies, entities, and user
interfaces components must be identified to avoid any unintentional issues caused by reverting
individual components to a previous version.
Power Apps has added components to the rule set that encourages best practices in the Power Apps
Checker. You can check your canvas apps and flows that are included in solutions and then review all
issues in a single, consolidated report.

QUESTION 8
You need to meet the requirements for sales representative that submit status reports.
How should you configure the flow?

A. Add a parallel branch that uses the value of a dynamic content variable
B. Add a number functions action that evaluates the risk value by using a static variable to determine if an email is required
C. Add a condition that evaluates the risk value by using a dynamic content variable
D. Add a data operation action that evaluates a dynamic content variable

Answer: C

Explanation:
Salespeople often do not set status of RFQs in the Sales Log to Won when a sale is closed and the
customer purchase order is received.
Include a dashboard that shows all currently active quotes, their status in the sales cycle, the
probability of closing, and estimated manufacturing and installation dates, by customer, product
division, status, and salesperson.

QUESTION 10
You need to create the mobile app.
Which type of app should you create?

A. model-driven app
B. portal app
C. Microsoft 365 web app
D. canvas app

Answer: D

Explanation:
An accessible canvas app will allow users with vision, hearing, and other impairments to successfully
use the app. In addition to being a requirement for many governments and organizations, following
the below guidelines increases usability for all users, regardless of their abilities.

SATISFIED CUSTOMERS