Explanation:
Box 1: Opportunity
Entity
Dynamics 365 Sales, Define goal metric and rollup fields
For each goal metric, you can create up to three rollup field records. Each record can specify actual, in-progress, or custom amount or count. You can use the same source table or difference source tables for all rollup field records. For example, in a goal metric that specifies the Money type, you can use an opportunity table as a source table and Opportunity.ActualValue as a source attribute. This lets you track the actual money amounts in all opportunities that are closed as "Won". The Opportunity.EstimatedValue can be used to track the revenue that is expected after the opportunity is closed.
Box 2: Actual Close Date
Date field
Specify Rollup Fields
To specify other important rollup information, use the rollup field table.
* RollupField.DateAttribute
The date that is validated against the goal time period, such as Opportunity.ActualCloseDate or Lead.EstimatedCloseDate. A record participates in the goal rollup, if the specified date falls between the start date and the end date for the goal. For example, if an opportunity is closed between the start and end dates for the goal, revenue generated from this opportunity is added to the goal's total revenue; otherwise, it is not included.
Box 3: Actual Revenue
Revenue field
Examples of rollup data are Lead.EstimatedAmount and OpportunityClose.ActualRevenue that can be rolled into the Goal.InProgressMoney and the Goal.ActualMoney rollup fields.

Explanation:
Box 1: Campaign
Table, Related (Many)
Hierarchical relationships are self-referential one-to-many relationships.
In this case from the Campaign table, to the Campaign table.
Example:

Box 2: Child campaign
Lookup column display name
Self-referential means that the table is related to itself. For example, the account table has a lookup column to associate it with another account table row.
The Parent table is on the 1-side of the 1-M relation, and it refers to Child Campaign with the Lookup column.
Box 3: Configurable Cascading
Relationship behavior, Type of behavior
Any actions taken on parent records should automatically be taken on child records.
When a one-to-many entity relationship exists there are cascading behaviors that can be configured to preserve data integrity and automate business processes.
Note: Parental entity relationships
Each pair of entities that are eligible to have a 1:N relationship can have multiple 1:N relationships between them. Yet only one of those relationships can be considered a parental entity relationship.
A parental entity relationship is any 1:N entity relationship where one of the cascading options (defined in CascadeType) in the Parental column of the following table is true.

In Dynamics 365 Sales, to ensure that all prices end in a specific format, such as $.98, you should use the Rounding Policy. This function allows you to define how prices should be rounded, including the ability to specify that they should end in particular digits. By setting a rounding policy, you can enforce this pricing requirement consistently across your pricing lists.

Correct:
* Salesperson [Preferred]
* Vice president of sales [Too much privilege compared to Salesperson. It is the second best option to be used if Salesperson is not an option] Incorrect:
* Forecast manager [Too limited]
* System customizer [Too limited]]
Users who have full permission to customize the environment. Users with this role have organization-level access to custom entities and user-level access to system entities.
Access includes but not limited to
reate, read, write, delete, and customizations across all features in the application.
* Sales team member [Too limited]
* Sequence manager [Too limited]
* Vice president of sales [Too much privilege compared to Salesperson]
Users who typically manage the sales organization for several business units or the entire organization Access includes but not limited to Same permissions as the Sales Manager, except that their scope of access is broader.
Note 1:
* Sales Manager
Users who manage a team of sellers and are responsible for the team's performance. They're also responsible for creating and managing products, setting sales targets, and projecting sales forecasts.
Access includes but not limited to
Access to product management, sales management, sales forecasting, and goal management, along with the privileges of the Salesperson role.
Note 2:
The principle of least privilege means granting the user only the minimum permissions necessary to perform their tasks. In this case, to allow User1 to assign salespeople to sales territories, the Salesperson role typically includes privileges related to managing sales processes, such as territories, while limiting access to broader system functions like those available to a Vice President of Sales or System Customizer.
The System Customizer and Vice President of Sales roles would grant more permissions than necessary, which would violate the principle of least privilege. The Sales Team Member role is typically too limited for assigning salespeople to sales territories, which requires more specific access.