最新的Microsoft Power Platform Functional Consultant (PL-200日本語版) - PL-200日本語免費考試真題

Explanation:

Box 1: Power Apps Web Studio
Scenario: The check-in solution must continue to function if there are internet issues. If the self-service kiosks are not available, staff must be able to use the check-in solution from within their communication solution.
PowerApps Studio is a browser application used to edit your apps. PowerApps Studio includes a drag-and- drop canvas in the center of the screen and a screen or object list pane on the left. Properties, Rules, and Advanced Properties for selected screens or controls are displayed in the right pane.
Box 2: in a tab
You can customize the Teams experience by adding Power Apps canvas apps to your channels in Teams using the PowerApps tab.

Explanation:

說明：（僅 Fast2test 成員可見）

Explanation:

Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/teams/analytics-summary-teams

Explanation:
Box 1: Move the manager and reports to a separate business unit.
Keep the Manager hierarchy, and put the reports to the appropriate business unit.
Note: 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. However, if you are a part of a customer service organization and want the managers to access service cases handled in different business units, the Position hierarchy may work better for you.
Box 2: Add the CEO to the representative user record as a manager.
Set up Manager and Position hierarchies
The Manager hierarchy is easily created by using the manager relationship on the system user record. You use the Manager (ParentsystemuserID) lookup field to specify the manager of the user.
Note: Depth is used to limit how many levels deep a manager has Read-only access to the data of their reports. For example, if the depth is set to 2, the CEO can see the data of the VP of Sales, VP of Service and Sales and Service Managers. However, the CEO doesn't see the Sales data or the Support data.

Box 3: Add users to field security
Power Platform's field-level security lets you set which fields users can see or edit.
Reference: https://docs.microsoft.com/en-us/power-platform/admin/hierarchy-security
https://docs.microsoft.com/en-us/power-platform/admin/field-level-security

Explanation:
Box 1: Assign records to a service account and add the team member doing the verification by using an access team.
When to use access teams
* The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren't provided.
* The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.
* A unique set of users requires access to a single record without having an ownership of the record.
Box 2: Assign records to the QV team when the service request is completed.
Issues: More employees than are required can access individual client information and continue to have access after a service request is completed.
Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed.
* When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.
Reference: https://docs.microsoft.com/en-us/power-apps/developer/data-platform/use-access-teams-owner- teams-collaborate-share-information

Explanation:

Step 1: Create a new publisher
Solution publisher
Every app and other solution components such as entities you create or any customization you make is part of a solution. Because every solution has a publisher, you should create your own publisher rather than use the default. You specify the publisher when you create a solution.
Step 2: Create a new unmanaged solution and select the correct publisher unmanaged solution Unmanaged solutions are used in development environments while you make changes to your application.
Unmanaged solutions can be exported either as unmanaged or managed. Exported unmanaged versions of your solutions should be checked into your source control system. Unmanaged solutions should be considered your source for Microsoft Power Platform assets. When an unmanaged solution is deleted, only the solution container of any customizations included in it is deleted. All the unmanaged customizations remain in effect and belong to the default solution.
Step 3: Add the table top the solution and add the new column.
Step 4: Run the solution checker on the solution
Use solution checker to validate your model-driven apps in Power Apps.
Reference: https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm
https://docs.microsoft.com/en-us/power-apps/maker/data-platform/use-powerapps-checker

說明：（僅 Fast2test 成員可見）