Q102. You have an existing Power Apps environment. You need to create a Common Data Service database for the environment. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Explanation
Graphical user interface, text, application Description automatically generated
Step 1: Select an existing environment
Add a database in the admin center:
1. In the admin center, in the left navigation pane, select Environments.
2. Select the environment to which you want to add the database.
Step 2: Select Create my database
3. Select + Add database
Step 3: Configure currency and language settings
4. Enter the following, and then select Add.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/create-database
Q103. You plan to create apps for a company. You need to identify the Power Platform tools required. What should you use? To answer, drag the appropriate tools to the correct requirements. Each tool may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point.
Explanation
Box 1: Canvas App
Box 2: Model-driven app
Model-driven app design is a component-focused approach to app development. Model-driven app design doesn’t require code and the apps you make can be simple or very complex. Unlike canvas app development where the designer has complete control over app layout, with model-driven apps much of the layout is determined for you and largely designated by the components you add to the app.
Box 3: Power Automate
Power Automate is a service that helps you create automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more.
Box 4: Power Virtual Agents bot
When you create bots with Power Virtual Agents, you author and edit topics.
Topics are discrete conversation paths that, when used together within a single bot, allow for users to have a conversation with a bot that feels natural and flows appropriately.
Creating a bot with Power Virtual Agents is easy to do with the no-code authoring canvas, and there are a number of ways you can manage how topics interact, how you want the conversation to flow, and what it should feel like.
Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/authoring-fundamentals
https://docs.microsoft.com/en-us/power-automate
Q110. You need to provide the app to Tailwind Traders. What should you do?
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. Reference: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Managed-vs-Unmanaged/td-p/495685 Topic 2, Contoso, Ltd 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 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 Background 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.
Q111. You are an app and report maker. You provide visualizations for two departments in an organization. Each department requires department-specific visualizations: You need to create the visualizations. Which chart type should you use? To answer, drag the appropriate chart type to the correct requirements. Each chart type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point.
Explanation
Graphical user interface, text, application Description automatically generated
Box 1: Tag
Box 2: Multi-series
Multi-series charts: Charts that display data with multiple series values mapped to a single category value.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/understand-charts-underlying-data-ch
Q114. You need to create the solution assets. What should you use to create the visualizations? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.
Explanation:
Box 1: PowerBI Desktop
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.
PowerBI Desktop to support many data source.
Box 2: PowerBI Desktop or Power BI Service on
A dashboard that shows a capacity Heat map by month as well as expected sales that are likely to close for the next month.
Both support visualizations.
Reference:
https://docs.microsoft.com/en-us/power-bi/fundamentals/service-service-vs-desktop
Q116. You are creating a model-driven app for onboarding new employees. You need to implement business logic for the app. Which tool should you use? To answer, drag the appropriate tools to the correct requirements. Each tool may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point.
Explanation:
Graphical user interface, text, application Description automatically generated
Box 1: Business process flow
A business process flow is a visual guide meant to help users complete a business process by using a set of predefined stages. Users are not limited on how long they run a business process or how long they have a stage open.
Box 2: Business rule
Box 3: Power Automate
A Power Automate flow does not have any visual components like a business process flow. Power Automate flows can be configured to work with many different data sources, and a flow can connect to many different data sources within the same flow. A flow can be configured to time out if it is not completed in a certain time and can be triggered to move between steps based on data or user interaction.
Reference:
https://docs.microsoft.com/en-us/learn/modules/intro-business-process-flows/2-differences
Q117. A production line app maker at a manufacturing company creates a canvas app that looks for available inventory in a SQL database. The production line workers use the inventory app across all work centers. The production line workers report the following app issues from the shop floor: * The app reports a delegation warning. * Voice command functionality is unreliable. You have minimal information about the issues. You are not allowed to enter the production facility. You need to troubleshoot the issues. How should you troubleshoot the issues? To answer, select the appropriate options in the answer area.
Explanation
Graphical user interface Description automatically generated
Box 1: Check the number of items in the collection
If the data in your data source exceeds 500 records and a function can’t be delegated, Power Apps might not be able to retrieve all of the data, and your app may have wrong results.
Note: Delegation is where the expressiveness of Power Apps formulas meets the need to minimize data moving over the network. In short, Power Apps will delegate the processing of data to the data source, rather than moving the data to the app for processing locally.
Box 2: Use the Advanced Tools/Monitor feature
Monitor is available by default for all canvas apps. Using Monitor, you can trace events as they occur in a canvas app during the authoring experience in Power Apps Studio, or you can use Monitor to debug the published version of a canvas app.
Example: Consider the scenario where an app has been deployed, and the initial version of the app experiences performance degradation. The app also intermittently generates errors with no clear pattern. Loading data in the app succeeds most of the time, but fails sometimes.
When you check Monitor, you see data operations as expected. However, you also see several responses that have HTTP status code 429, indicating that there have been too many requests in a specific timeframe.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/delegation-overview
https://docs.microsoft.com/en-us/powerapps/maker/monitor-canvasapps