Correct Answer: AC

Scenario: The testing team reports that one of the canvas apps is not working as expected. An error message displays as specific pages load.

A: The App checker is now available to help provide a clear list of formula issues in your app, and to provide items to fix to make your app accessible. The App checker is an area that the PowerApps team will continue to invest in, and build on in order help to make debugging, performance and best practice decisions an easier and more guided experience.

C: With the solution checker feature, you can perform a rich static analysis check on your solutions against a set of best practice rules and quickly identify these problematic patterns. After the check completes, you receive a detailed report that lists the issues identified, the components and code affected, and links to documentation that describes how to resolve each issue.

Reference: https://powerapps.microsoft.com/en-us/blog/new-app-checker-helps-you-fix-errors-and-make-accessible-apps/

Correct Answer: A

Scenario: Information about each machine produced must be transferred to Dynamics 365 Field Service.

Use the Microsoft Dataverse connector when connecting to the Microsoft Dataverse used for Microsoft Dynamics 365 Sales, Microsoft Dynamics 365 Customer Service, Microsoft Dynamics 365 Field Service, Microsoft Dynamics 365 Marketing, and Microsoft Dynamics 365 Project Service Automation.

Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/connections/connection-dynamics-crmonline

Correct Answer: AB

Correct Answer: AD

A: Power BI is a business analytics service by Microsoft. It aims to provide interactive visualizations and business intelligence capabilities with an interface simple enough for end users to create their own reports and dashboards. It is part of the Microsoft Power Platform.

D: Power BI Apps are an easy way for designers to share different types of content at one time. App designers create the dashboards and reports and bundle them together into an app. The designers then share or publish the app to a location where you, the business user, can access it. Because related dashboards and reports are bundled together, it's easier for you to find and install in both the Power BI service (https://powerbi.com) and on your mobile device. After you install an app, you don't have to remember the names of a lot of different dashboards or reports because they're all together in one app, in your browser or on your mobile device.

Reference:

https://docs.microsoft.com/en-us/power-bi/consumer/end-user-apps

Correct Answer: ADE

A (not B): Put the delay in the form loading instead.

E (not C): Changing the limit

500 is the default number of records, but you can change this number for an entire app:

Select Settings.

Under General, change the Data row limit setting from 1 to 2000.

In some cases, you'll know that 2,000 (or 1,000 or 1,500) will satisfy the needs of your scenario. With care, you can increase this number to fit your scenario. As you increase this number, your app's performance may degrade, especially for

wide tables with lots of columns. Still, the best answer is to delegate as much as you can.

Microsoft Power Platform canvas app on premises cloud data rows limits.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/delegation-overview#non-delegable-limits

Correct Answer: BCE

Correct Answer: CDE

Explanation:

* Store employees must be able to view data for their store only.

(D) Security roles Dataverse uses role-based security to group together a collection of privileges. These security roles can be associated directly to users, or they can be associated with Dataverse teams and business units. Users can then be associated with the team, and therefore all users associated with the team will benefit from the role. A key concept of Dataverse security to understand is all privilege grants are accumulative with the greatest amount of access prevailing. If you gave broad organization level read access to all contact records, you can't go back and hide a single record.

* Regional managers must be able to view data for all stores in a region.

(C) Manager hierarchy

Hierarchy security to control access The hierarchy security model is an extension to the existing security models that use business units, security roles, sharing, and teams. It can be used in conjunction with all other existing security models. The hierarchy security offers a more granular access to records for an organization and helps to bring the maintenance costs down. For example, in complex scenarios, you can start with creating several business units and then add the hierarchy security. This will achieve a more granular access to data with far less maintenance costs that a large number of business units may require.

Manager hierarchy and Position hierarchy security models Two security models can be used for hierarchies, the Manager hierarchy and the Position hierarchy. With the Manager hierarchy, a manager must be within the same business unit as the report, or in the parent business unit of the report's business unit, to have access to the report's data. The Position hierarchy allows data access across business units. If you are a financial organization, you may prefer the Manager hierarchy model, to prevent managers’ accessing data outside of their business units.

* The reporting team must be able to view all data across all stores.

(E) Owner teams

With owner teams or access teams, you can easily share business objects and collaborate with the users across business units in Microsoft Dataverse. A team belongs to one business unit, but it can include users from other business units. A user can be associated with more than one team.

An owner team owns rows and has security roles assigned to the team. The team's privileges are defined by these security roles. In addition to privileges provided by the team, team members have the privileges defined by their individual security roles and by the roles from other teams in which they are members. A team has full access rights on the records that the team owns.

Reference: https://learn.microsoft.com/en-us/power-platform/admin/wp-security-cds https://learn.microsoft.com/en-us/power-platform/admin/hierarchy-security https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-access-teams-owner-teams-collaborate-share-information

Correct Answer:

Box 1: Functional

Functional requirements describe what the solution needs to do or its behaviors, and non-functional requirements commonly describe non-behavior aspects of the solution such as performance requirements.

Example functional requirements

The following scenarios describe simple examples of functional requirements:

As a sales user, I need to be able to close an opportunity as lost and then capture why it was lost so that we can improve our sales tactics in the future.

As a sales manager, I need to be able to approve a discount on a quote so that I can reduce the total price and give a discount to the customer.

As a staff accountant, I want to be prevented from closing a batch that has pending items so that I do not have to reopen it later.

Box 2: Non-Functional

Examples of common non-functional requirement types include:

1.

Availability

2.

Compliance/regulatory

3.

Data retention/residency

4.

Performance (response time, and so on)

5.

Privacy

6.

Recovery time

7.

Security

8.

Scalability Reference: https://learn.microsoft.com/en-us/training/modules/work-with-requirements/3-functional-requirements

Correct Answer:

Explanation:

Step 1: Create an Azure DevOps Project.

If you're using the segmented code component solution project, you can build the project inside an Azure DevOps Pipeline (using Microsoft Power Platform Build Tools) or GitHub Pipeline (using GitHub Actions for Microsoft Power Platform).

Step 2 Install the Microsoft Power Platform Build Tools.

After installation, all tasks included in the Microsoft Power Platform Build Tools will be available to add into any new or existing pipeline.

Note: Use Microsoft Power Platform Build Tools to automate common build and deployment tasks related to apps built on Microsoft Power Platform.

Microsoft Power Platform Build Tools tasks can be used along with any other available Azure DevOps tasks to compose your build and release pipelines. Pipelines that teams commonly put in place include Initiate, Export from Dev, Build, and

Release.

Microsoft Power Platform Build Tools are a collection of Power Platform–specific Azure DevOps build tasks that eliminate the need to manually download custom tooling and scripts to manage the application lifecycle of apps built on Microsoft

Power Platform. The tasks can be used individually to perform a task, such as importing a solution into a downstream environment, or used together in a pipeline to orchestrate a scenario such as "generate a build artifact", "deploy to test", or

"harvest maker changes."

Step 3: Create a Release pipeline.

Create a DevOps pipeline to export your completed unmanaged solution to a managed solution.

Step 4: Add a task for Microsoft Power Platform Import Solution

Solution tasks

This set of tasks can automate solution actions. The environment tasks outlined later in this section that create, copy, or restore an environment will overwrite the service connections with the newly created environments. This makes it

possible to perform solution tasks against environments that are created on demand.

Power Platform Import Solution

Imports a solution into a target environment.

Incorrect:

*

Create an Export pipeline.

*

Run the pipeline.

Reference: https://learn.microsoft.com/en-us/power-platform/alm/new-project-alm https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tools

Correct Answer:

Explanation:

Box 1: By license How API limits are allocated Entitlement limits

These limits represent the number of requests users are entitled to make each day. The allocated limit depends on the type of license assigned to each user.

If any user exceeds their request entitlement, the administrator would be notified and would be able to assign Power Apps and Power Automate request capacity to that user. Users won't be blocked from using apps for occasional and reasonable overages at this point of time. Box 2: Dataverse, Power Apps, and Power Automate

Which Microsoft Power Platform components count toward its API limits Power Platform API request allocations include use of Power Automate, AI Builder, and Connector APIs. All requests through a connector that result in a Dataverse request will represent 1 Power Platform request. Box 3: Each step counts as one API request

Which Power Automate flow steps count toward API limits

What is a Microsoft Power Platform request?

Requests in Microsoft Power Platform consist of various actions that a user makes across various products. At a high level, below is what constitutes an API request:

* Power Automate – all API requests to connectors, process advisor analysis, HTTP actions, and built-in actions from initializing variables to a simple compose action. Both succeeded and failed actions count towards these limits. Additionally, retries and other requests from pagination count as action executions as well.

Note: Service protection API limits aren't applied against API calls made within workflows, custom workflow activities, or plug-in code. These operations are invoked internally.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/api-limits-overview https://learn.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations