Explanation:

Box 1: Yes
setNotification displays an error message for the control to indicate that data isn't valid. When this method is used, a red "X" icon appears next to the control. On Dynamics 365 mobile clients, tapping on the icon will display the message.
Syntax: formContext.getControl(arg).setNotification(message,uniqueId);
Box 2: No
Box 3: Yes
setFormNotification displays form level notifications. You can display any number of notifications and they will be displayed until they are removed using clearFormNotification.
Syntax: formContext.ui.setFormNotification(message, level, uniqueId);
Box 4: No
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/formcontext-ui
/setformnotification
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/controls
/setnotification

Explanation:

Box 1: less
less checks whether the first value is less than the second value. Return true when the first value is less, or return false when the first value is more.
Box 2 : ticks
ticks(timestamp: string) - Returns the number of ticks (100 nanoseconds interval) since 1 Jan 1601 00:00:00 UT Syntax: ticks('<timestamp>') Box 3: triggerBody triggerBody returns a trigger's body output at runtime.
Box 4: ticks
Box 5: getFutureTime
getFutureTime teturn the current timestamp plus the specified time units.
Syntax: getFutureTime(<interval>, <timeUnit>, <format>?)
Reference:
https://docs.microsoft.com/en-us/azure/logic-apps/workflow-definition-language-functions-reference

Explanation:
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.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/field-security-entities
https://docs.microsoft.com/en-us/power-platform/admin/database-security
https://docs.microsoft.com/en-us/power-platform/admin/database-security
https://docs.microsoft.com/en-us/power-platform/admin/manage-teams-types-of-teams
https://docs.microsoft.com/en-us/power-platform/admin/manage-teams#types-of-teams

Improve operational efficiency with a unified view of business data by creating flows that use Dataverse (Common Data Service has been renamed to Microsoft Dataverse as of November 2020).
For example, you can use Dataverse within Power Automate in these key ways:
Create a flow to import data, export data, or take action (such as sending a notification) when data changes.
Instead of creating an approval loop through email, create a flow that stores approval state in an entity, and then build a custom app in which users can approve or reject items.
Reference:
https://docs.microsoft.com/en-us/power-automate/common-data-model-intro

Explanation: