[Jul 13, 2023] Genuine PL-100 Exam Dumps Free Demo [Q11-Q25]

Reference:
https://docs.microsoft.com/en-us/power-bi/fundamentals/service-get-started
https://docs.microsoft.com/en-us/power-bi/visuals/power-bi-report-visualizations

Explanation:
Box 1: No
Records are added, not updated.
Box 2: Yes
The Collect function adds records to a data source.
Syntax: Collect( DataSource, Item, … )
DataSource – Required. The data source that you want to add data to. If it doesn’t already exist, a new collection is created.
Item(s) – Required. One or more records or tables to add to the data source.
Box 3: No
No records are cleared.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-clear-collect-clearcollect

User access diagnostic tool in the Power Platform admin center:
Several factors influence user access in a Microsoft Dataverse environment. To help administrators with diagnosing user access to an environment and reasons for access or no access, the new “Run diagnostics” feature in the Power Platform admin center provides basic access diagnostics for individual users in the environment. The feature helps to detect potential causes to user sign-in and other issues and suggests potential mitigations.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/troubleshooting-user-needs-read-write-access-organization
Topic 1, Contoso, Ltd
Current environment
Overview
Operations for the company are managed very informally. Only a small number of long-term employees are aware of all manufacturing processes.
Accounting system and purchasing
The company has a cloud-based ERP/accounting system and uses the General Ledger, Accounts Receivable, and Accounts Payable modules. The current system does not have any modules that handle shop floor or manufacturing planning functionality.
Employee information is maintained only within the accounting system. Access to the information is strictly controlled due to privacy regulations and company policies.
All purchasing of raw materials is performed based on bills of material (BOMs) generated by the engineering department when engineering prints are created.
The corporate office uses Dynamics 365 Finance. The operations manager reports that Dynamics 365 Finance will not be implemented for the manufacturing plants for at least five years.
Manufacturing and planning
The plant that Contoso, Ltd. acquires uses Microsoft Excel workbooks and Microsoft Word documents to track the sales pipeline, requests for quote responses, and work estimates. The documents are stored on shared network drives.
Printed engineering drawings are sometimes accidently used across orders. This results in rework, cost over runs, and missed deliveries.
The company uses Job Traveler documents to detail the operations that need to be performed and the materials needed for a given job number.
Sales
Requests for quotes are currently stored in a Sales Log workbook. The workbook includes the following information:
Customer request number
Customer name
Description
Estimated value of the sale
Status of the Request for Quote (RFQ) with the values of Won, Lost, No Bid, and Cancelled Names of the sales manager, salesperson, and estimator Name of the product line Date the quote was sent to the customer Approximate start and finish dates of the project Date the order was received, if won Job number, which is assigned if won The company has a formal process in place for managing estimates. Some sales quotes lack required supporting documentation including estimates for labor and materials even though a formal process is in place. The company wants to incorporate the formal process as part of an app.
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.
An accurate sales pipeline and win/loss information cannot currently be reported because the close probability field in the Sales Log is being set to 100% when a sale is closed and 0% when a sale is lost.
Setting up a folder system on the network drive by a customer had not improved the hand-off of the current version of the sales quote to manufacturing.
Requirements
Solution
You plan to create a solution that uses Microsoft Teams and Power Platform.
You must convert the Sales Log workbook to a Common Data Service database.
Each department will have a separate Teams channel. Employees must only be able to access the channel for their department. All employees and management will have read access to a general company channel. The Teams site must include the following channels:
Sales
The Sales dashboard must reside in the Sales channel and must include information about active quotes, sales pipeline, and year-to-date sales KPIs for sales quotas by region.
All Sales-related documents must be stored in folders in the files location for this channel. Document versioning will be enabled. You must store the 10 most recent versions of a document.
Manufacturing
A dashboard that shows a capacity Heat map by month as well as expected sales that are likely to close for the next month.
A sortable listing of all in-process jobs from the Job Setup table, by customer, start date, and product.
Printed paper drawings must no longer be used. The drawings must be stored in folders in the files location for the manufacturing channel.
General
You must create the following apps:
Time Tracking
You must create a canvas app to track time for each employee on mobile devices. The app must include the following:
a Sign-in screen
a screen to list the week’s time entries for the employee
a screen to edit current time entries for the employee
The app must meet the following requirements:
The app must store its data in the existing on-premises Microsoft SQL Server instance.
Employees must only be able to access their own time tracking records from the app.
Employees must record all time spent in the fabrication of each customer job.
Employees must only be able to modify time records for the current and previous day.
Employees must be able to scan their badges to check in and out of work. Each badge contains the employee name and a current picture.
A QR code must be added to all employee badges. The code must include the employee’s number.
Job Traveler documents must be printed as PDF documents and must include UPC E barcodes for the job number and task number. The barcodes will be used with the time tracking application.
Sales
The Sales app must meet the following requirements:
Provide a central location for all sales pipeline and quote information that is easily accessible and maintains all of the versions of the estimate, quote, and engineering documents.
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.
The Sales Log app must enforce process standards related to the completion of estimates and supporting materials needed during the sales lifecycle.
Automatically perform the following actions immediately when a sale is won:
Generate a sequential job number.
Copy key sales information to the Job Setup entity used by manufacturing.
If the sale is lost, the Status field must be set to Lost and the reason for the loss must be entered into a provided text field. The reason must be added to the end of the description field.
Ensure that employees can easily update the Sales Log even if they are at a customer site.
Manufacturing and planning
The app must meet the following requirements:
Provides features to plan and predict capacity resource requirements for current and upcoming orders in the pipeline.
Replace paper timesheets and track check-in, check-out, breaks, and the time spent on each job task.
Record time elapsed while performing work and for viewing of engineering drawings.
The Job Setup entity must store its data in the existing on-premises SQL Server instance.
Job Traveler documents must be generated as a PDF document and printed from the Job Setup entity.
Issues
Uses report that the customer request number is difficult to interpret. They request that you change the number to a system generated sequential number.
The operations manager reports that users often incorrectly sign in to the time tracking app. The operations manager asks that the time tracking app display the employee’s photo once they have scanned their badge.
Users want to be able to see their weekly total time entered from all screens.
Testers report that they can see time entries in the Time Tracker app, not just their own. Additionally, they can also edit any existing time entries.

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-nn-relationships-portal

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-screen
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-form

Explanation
Common Data Model is built upon a rich and extensible metadata definition system that enables you to describe and share your own semantically enhanced data types and structured tags, capturing valuable business insight which can be integrated and enriched with heterogeneous data to deliver actionable intelligence.
Common Data Model can be used by various applications and services including Microsoft Dataverse, Dynamics 365, Microsoft Power Platform, and Azure ensuring that all of your services can access the same data.
Note: A wide variety of applications and services can easily access data in a data lake, however, each consumer must understand the format and meaning of the data before it can provide value. The Common Data Model simplifies this process by providing a metadata system that describes the data and standard entities to which producers can map.
Reference:
https://docs.microsoft.com/en-us/common-data-model/use

The Data table control shows a dataset.
In a canvas app, add and configure a Display form control to show all fields in a record.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-data-table
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/working-with-form-layout

Explanation:
Box 1: View the sessions details page for the app in Power Apps Studio
Use PowerApps Studio, select the App, and choose and you will be directed to the app’s Versions tab in PowerApps portal. There should be one version marked Live.

Box 2: Select Restore on the previous version of the app.
Restore an app from your account
1. Open powerapps.com, and then click or tap Apps in the left navigation bar.
2. Near the right edge, click or tap the info icon for the app that you want to restore.
3. Click or tap the Versions tab, and then click or tap Restore for the version that you want to restore.

Reference:
https://powerapps.microsoft.com/sk-sk/blog/saveandpublish/
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/restore-an-app

Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/set-aspect-ratio-portrait-landscape

1 – Add a Subgrid component to a form
2 – Select Show related records and then select the related entity and default view for the subgrid
3 – Select the Allow users to change view option
4 – Save and publish the form
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/form-designer-add-configure-subgrid

1 – Open the maker app and navigate to the student table
2 – Create new options for College – 1 Year and College – 2 years
3 – Publish the student entity

Explanation

Box 1: Fill
Scenario: You must display a visual indicator in the app so that sales representatives know whether the app is offline before submitting reports.
Fill – The background color of a control.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-screen
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-form

“Microsoft Power Platform and AI Builder components allowed us to quickly deliver an innovative and well-integrated solution within our Dynamics 365 platform for our marketing and sales business partners. The platform is a game-changer in this new world of rapid app delivery.” Jim Parker: Web and Collaboration Services Manager Reference:
https://customers.microsoft.com/en-au/story/810656-hexion-manufacturing-power-platform
Topic 1, Contoso, Ltd
Accounting system and purchasing
The company has a cloud-based ERP/accounting system and uses the General Ledger, Accounts Receivable, and Accounts Payable modules. The current system does not have any modules that handle shop floor or manufacturing planning functionality.
Employee information is maintained only within the accounting system. Access to the information is strictly controlled due to privacy regulations and company policies.
All purchasing of raw materials is performed based on bills of material (BOMs) generated by the engineering department when engineering prints are created.
The corporate office uses Dynamics 365 Finance. The operations manager reports that Dynamics 365 Finance will not be implemented for the manufacturing plants for at least five years.
Manufacturing and planning
The plant that Contoso, Ltd. acquires uses Microsoft Excel workbooks and Microsoft Word documents to track the sales pipeline, requests for quote responses, and work estimates. The documents are stored on shared network drives.
Printed engineering drawings are sometimes accidently used across orders. This results in rework, cost over runs, and missed deliveries.
The company uses Job Traveler documents to detail the operations that need to be performed and the materials needed for a given job number.
Sales
Requests for quotes are currently stored in a Sales Log workbook. The workbook includes the following information:
Customer request number
Customer name
Description
Estimated value of the sale
Status of the Request for Quote (RFQ) with the values of Won, Lost, No Bid, and Cancelled Names of the sales manager, salesperson, and estimator Name of the product line Date the quote was sent to the customer Approximate start and finish dates of the project Date the order was received, if won Job number, which is assigned if won The company has a formal process in place for managing estimates. Some sales quotes lack required supporting documentation including estimates for labor and materials even though a formal process is in place. The company wants to incorporate the formal process as part of an app.
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.
An accurate sales pipeline and win/loss information cannot currently be reported because the close probability field in the Sales Log is being set to 100% when a sale is closed and 0% when a sale is lost.
Setting up a folder system on the network drive by a customer had not improved the hand-off of the current version of the sales quote to manufacturing.
Requirements
Solution
You plan to create a solution that uses Microsoft Teams and Power Platform.
You must convert the Sales Log workbook to a Common Data Service database.
Each department will have a separate Teams channel. Employees must only be able to access the channel for their department. All employees and management will have read access to a general company channel. The Teams site must include the following channels:
Sales
The Sales dashboard must reside in the Sales channel and must include information about active quotes, sales pipeline, and year-to-date sales KPIs for sales quotas by region.
All Sales-related documents must be stored in folders in the files location for this channel. Document versioning will be enabled. You must store the 10 most recent versions of a document.
Manufacturing
A dashboard that shows a capacity Heat map by month as well as expected sales that are likely to close for the next month.
A sortable listing of all in-process jobs from the Job Setup table, by customer, start date, and product.
Printed paper drawings must no longer be used. The drawings must be stored in folders in the files location for the manufacturing channel.
General
You must create the following apps:
Time Tracking
You must create a canvas app to track time for each employee on mobile devices. The app must include the following:
a Sign-in screen
a screen to list the week’s time entries for the employee
a screen to edit current time entries for the employee
The app must meet the following requirements:
The app must store its data in the existing on-premises Microsoft SQL Server instance.
Employees must only be able to access their own time tracking records from the app.
Employees must record all time spent in the fabrication of each customer job.
Employees must only be able to modify time records for the current and previous day.
Employees must be able to scan their badges to check in and out of work. Each badge contains the employee name and a current picture.
A QR code must be added to all employee badges. The code must include the employee’s number.
Job Traveler documents must be printed as PDF documents and must include UPC E barcodes for the job number and task number. The barcodes will be used with the time tracking application.
Sales
The Sales app must meet the following requirements:
Provide a central location for all sales pipeline and quote information that is easily accessible and maintains all of the versions of the estimate, quote, and engineering documents.
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.
The Sales Log app must enforce process standards related to the completion of estimates and supporting materials needed during the sales lifecycle.
Automatically perform the following actions immediately when a sale is won:
Generate a sequential job number.
Copy key sales information to the Job Setup entity used by manufacturing.
If the sale is lost, the Status field must be set to Lost and the reason for the loss must be entered into a provided text field. The reason must be added to the end of the description field.
Ensure that employees can easily update the Sales Log even if they are at a customer site.
Manufacturing and planning
The app must meet the following requirements:
Provides features to plan and predict capacity resource requirements for current and upcoming orders in the pipeline.
Replace paper timesheets and track check-in, check-out, breaks, and the time spent on each job task.
Record time elapsed while performing work and for viewing of engineering drawings.
The Job Setup entity must store its data in the existing on-premises SQL Server instance.
Job Traveler documents must be generated as a PDF document and printed from the Job Setup entity.
Issues
Uses report that the customer request number is difficult to interpret. They request that you change the number to a system generated sequential number.
The operations manager reports that users often incorrectly sign in to the time tracking app. The operations manager asks that the time tracking app display the employee’s photo once they have scanned their badge.
Users want to be able to see their weekly total time entered from all screens.
Testers report that they can see time entries in the Time Tracker app, not just their own. Additionally, they can also edit any existing time entries.

Explanation
Graphical user interface, text, application Description automatically generated

Box 1: Adaptive card flow
Adaptive Cards are a platform-agnostic method of sharing and displaying blocks of information without the complexity of customizing CSS or HTML to render them.
Directing content to Teams channels:
Post your own adaptive card as the Flow bot to a channel
This action posts an adaptive card as a Flow bot to a specific Teams channel. In this case, you will be prompted for Teams instance, and a channel where the card will be posted. The flow-maker will have to have access to the Teams instance in order to post an adaptive card there. In this case, only URL buttons function by redirecting to the URL configured within the flow.
Box 2: Button flow
Create a button flow to run routine tasks by simply tapping a button. Customize your flow by allowing the user to provide specific details that will be used when the flow runs.
Reference:
https://docs.microsoft.com/en-us/power-automate/overview-adaptive-cards
https://docs.microsoft.com/en-us/power-automate/button-flow-with-user-input-tokens

Reference:
https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm