Explanation:

Explanation:
Box 1: 0 0 4 * * 1-5
Azure Functions uses the NCronTab library to interpret NCRONTAB expressions.
An NCRONTAB expression is similar to a CRON expression except that it includes an additional sixth field at the beginning to use for time precision in seconds:
{second} {minute} {hour} {day} {month} {day-of-week}
NCRONTAB time zones
The numbers in a CRON expression refer to a time and date, not a time span. For example, a 5 in the hour field refers to 5:00 AM, not every 5 hours.
The default time zone used with the CRON expressions is Coordinated Universal Time (UTC).
To have your CRON expression based on another time zone, create an app setting for your function app named WEBSITE_TIME_ZONE.
1-5 is weekdays
Box 2: 0 0 4 * * 1-5
Reference:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-timer?

Explanation:

Scenario: Customer satisfaction surveys are recorded with Microsoft Forms Pro.
Box 1: Flip switch
The flip switch is like an on/off switch, providing a choice between two values.
Box 2: Linear gauge
The linear gauge lets your users input numerical values by dragging a slider instead of typing in the exact quantity. The slider provides whole number input and display only. Use this control for any numerical and money columns.
Box 3: Option set
The choice control presents a set of options for your users to choose from when entering data.
You can customize forms (main, quick create, and quick view) and email templates by adding multi-select columns that are called Choices. When you add a choices column, you can specify multiple values that will be available for users to select. When users fill out the form they can select one, multiple, or all the values displayed in a drop-down list.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/additional-controls-for-dynamics-365-for-phones-and-tablets

Explanation:

Box 1: Custom self-service portal for both employers and job candidates If you select an environment that contains customer engagement, you can create the following portals:
Customer self-service portal: A customer self-service portal enables customers to access self-service knowledge, support resources, view the progress of their cases, and provide feedback.
Partner portal: A partner portal allows every organization with resellers, distributors, suppliers, or partners to have real-time access to every stage of shared activities.
Employee self-service portal: An employee self-service portal creates an efficient and well-informed workforce by streamlining common tasks and empowering every employee with a definitive source of knowledge.
Box 2: Model-driven app with push notifications
Compared to canvas apps, model-driven apps in PowerApps are based on underlying data - specifically, the data stored in Common Data Service (CDS).
Box 3: Webform with target set to the job custom entity
Box 4: Configure a value for the Execute Workflow on Redeeming Contact option only.
Execute Workflow on Redeeming Contact: A workflow process to be executed when the invite is redeemed.
The workflow will be passed the redeeming contact as the primary entity.
Box 5: Configure the value for the Assigned to Account option only.
Assign to Account: An account record to be associated as the redeeming contact's parent customer when the invite is redeemed.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/portals/portal-templates
https://global.hitachi-solutions.com/blog/canvas-vs-model-driven-apps
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/invite-contacts#invitation-attributes

By default, model-driven apps allows a specified set of query string parameters to be passed to a form. You use these parameters to set default values when you create a new record in the application. Each parameter must use a standard naming convention that includes a reference to the column logical name.
There are two ways to specify which query string parameters will be accepted by the form:
Edit form properties
Edit form XML
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/configure-form-accept-custom-querystring-parameters