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

Explanation:

https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/working-with-test-studio

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

To implement field-level security, a system administrator performs the following tasks.
* Enable field security on one or more fields for a given entity.
* Associate one more existing security profiles, or create one or more new security profiles to grant the appropriate access to specific users or teams.
A security profile determines the following:
* Permissions to the secure fields
* Users and Teams
A security profile can be configured to grant user or team members the following permissions at the field level:
* Read. Read-only access to the field's data.
* Create. Users or teams in this profile can add data to this field when creating a record.
* Update. Users or teams in this profile can update the field's data after it has been created.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/field-level-security