Reference https://fusionhelp.oracle.com/helpPortal/topic/TopicId_P_988B43C997365159E040D30A68813832
https://docs.oracle.com/cd/E48434_01/fusionapps.1118/e49622/F1125377AN61D92.htm

When the Accrue at Receipt option is set to Yes on a PO, the cost of the items or services is accrued when they are received, not when they are invoiced. Therefore, the cost is transferred to projects by Cost Management and not by Payables. However, if the PO is closed for receiving without creating a receipt, there will be no accounted receipt lines and no cost will be transferred to projects. To transfer the cost to projects, you need to either create a receipt or reopen the PO for receiving. https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-costs.html#OAPFM2355855

Reference https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/define-project-organizations.html#OAPFM177674 Settings That Affect Performance Data Summarization You can summarize performance data for a project unit, business unit, a range of projects, or projects managed by a project manager. When you run the Update Project Performance Data process from the Scheduled Processes page, select one of the summarization methods from the following table:
Summarization Method
Usage
Incremental
Summarizes new transactions that are yet to be summarized
Delete and re-summarize
Correct summary data when the source system data changes outside the regular transaction flow.
Do not use this summarization method when you run the Update Project Performance Data Without Producing Report process unless you are advised to do so.
Resource breakdown structure
Migrate all summary data from one resource breakdown structure version to the next.
If you select this option, you must also specify the resource breakdown structure header.

According to Oracle sources1, the inheritance between requirements, tasks, and deliverables works as follows:
You can associate a deliverable with a task independent of associating a requirement with a task. You can also associate a deliverable with a requirement independent of associating a task with a requirement1.
A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. You must manually associate the deliverable with the tasks that produce it1.
Therefore, the correct answer is B and D.
1: Can deliverables for projects and tasks be inherited from associated requirements? - docs.oracle.com (index 1) In Oracle Project Management, you can define requirements, tasks, and deliverables for your project based on your project methodology and lifecycle. Requirements are statements of needs or expectations that must be met by the project outcome. Tasks are units of work that must be performed to complete the project. Deliverables are products or services that are produced or provided as part of a task or requirement. Two correct statements about how the inheritance between requirements, tasks, and deliverables works are:
You associate a deliverable with a task independent of associating a requirement with a task. This means that you can create a deliverable for a task regardless of whether the task is linked to a requirement or not.
A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. This means that you have to manually associate a deliverable with a task even if both the deliverable and the task are linked to the same requirement.

Ref: https://docs.oracle.com/en/cloud/saas/applications-common/19b/facia/define-approval-management.html#FACIA3124477 Topic Approval Groups Each approval group includes a set of users that you configure to act on tasks in a certain pattern. Tasks can be defined to get routed to an approval group instead of an individual user. You can nest approval groups within approval groups.
You have two options for defining the group:
Static: Select the specific users to include in the group.
Dynamic: Provide the logic to use to determine the users in the group.