Explanation:

Box 1: Create a lookup to Dynamics 365 Field Service
Scenario: Machines are assigned serial numbers and placed in stock until they are shipped to customers.
Entity lookup: Allows technicians to choose a Dynamics 365 record. In the inspection designer interface, admins must select an entity and a field to display. For a chosen entity, the Name field and mandatory fields are the entity attributes that can be displayed in the lookup.
Box 2: Create a one-to-many relationship and set the behavior to Parental Scenario: Inspection orders must:
* Allow entry of quality ratings of passed or failed for each quality metric identified for the machine being rated.
* Be automatically marked as failed if one inspection step rating is marked as failed.
Each inspection order can have one or many inspection steps, and each inspection step has a rating.
Note: Each pair of tables that are eligible to have a 1:N relationship can have multiple 1:N relationships between them. Yet usually only one of those relationships can be considered a parental table relationship.
Reference:
https://docs.microsoft.com/en-us/dynamics365/field-service/inspections
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships