Microsoft PL-400 Exam With Confidence Using Practice Dumps

Box 1: Field level security

Only supervisors must be able to view phone numbers in the Accounts form.

You use field security tables to apply field-level security, which restricts field access to specified users and teams. The scope of field-level security is global, which means that it applies to all records within the organization, regardless of the business unit hierarchical level to which the record or the user belongs. Field security works in all Microsoft Dataverse clients, including the Web client, Dynamics 365 for Outlook, and Dynamics. It applies to all components, such as the Dataverse web services, reports, search, offline, filtered views, auditing, and duplicate detection.

Box 2: Team Security

Sales users must only have access to their own records.

Owner team: An owner team owns records and has security roles assigned to the team. A user's privileges can come from their individual security roles, those of the teams that they're part of or the ones they inherit. A team has full access rights on the records that the team owns. Team members are added manually to the owner team.

Box 3: Environment security

Developers must be able to create new apps for all users.

Environment maker: Can create new resources associated with an environment, including apps, connections, custom APIs, gateways, and flows using Microsoft Power Automate. However, this role doesn't have any privileges to access data within an environment.

Scenario: User2 reports that Azure consumption for API calls has increased significantly to 100 calls per minute in the last month.

Example:

In the following example, the rate limit of 10 calls per 60 seconds is keyed by the caller IP address. After each

policy execution, the remaining calls allowed in the time period are stored in the variable remainingCallsPerIP.

renewal-period="60"

increment-condition="@(context.Response.StatusCode == 200)"

counter-key="@(context.Request.IpAddress)"

remaining-calls-variable-name="remainingCallsPerIP"/>

Note: The rate-limit-by-key policy prevents API usage spikes on a per key basis by limiting the call rate to a

specified number per a specified time period. The key can have an arbitrary string value and is typically

provided using a policy expression. Optional increment condition can be added to specify which requests

should be counted towards the limit. When this call rate is exceeded, the caller receives a 429 Too Many

Requests response status code.