The requirement specifies that a new vendor must accept terms on Agreements before an Opportunity can be closed. Salesforce Approval Processes are the declarative solution for enforcing such business rules. An approval process can:
* Require users (vendors) to accept or approve records (Agreements).
* Prevent Opportunities from moving to a closed stage until approval is completed.
* Send email notifications automatically to approvers.
Salesforce documentation confirms that approval processes are used to enforce conditions on record lifecycle and ensure required steps are completed before record status changes. (Salesforce Help)
* A. Email Alert cannot enforce record progression.
* B. Dynamic Action only controls field-level UI visibility, not enforcement.
* D. Validation Rule could prevent saving a record, but it cannot require explicit approval from a specific user group.

The correct answers are B. Use a roll-up summary field on the Park record and C. Use a master-detail relationship between the Park and Trail objects.
Northern Trail Outfitters wants the total number of Trails displayed on the Park record without code. In Salesforce, a standard roll-up summary field can count related child records, but it requires a master-detail relationship between the parent and child objects. Salesforce documentation confirms that roll-up summary fields calculate values from related records, and this is the correct declarative feature for this requirement.
A is incorrect because a formula field cannot count child records. D is incorrect because standard roll-up summary fields do not work on ordinary lookup relationships.

The correct answers are A. Dynamic Actions and C. Approval Process.
An Approval Process is required because sales managers must provide formal sign off when an Opportunity discount meets the defined criteria. Salesforce approval processes define the criteria a record must meet, the steps required for approval, and who must approve it.
Dynamic Actions are also needed because Universal Containers wants the sign-off action available quickly from the Opportunity record page. Dynamic Actions let app builders control which actions appear on Lightning record pages based on conditions.
Why others are incorrect:
Schema Builder is for data model design, not approval/sign-off UI behavior.
Validation Rule can block invalid data, but it does not provide manager approval or sign-off.

The correct bulk-safe Flow pattern is to modify each current Case with an Assignment element and add the modified record to a record collection variable. After the Loop finishes, one Update Records element should update the complete collection. Salesforce explicitly warns against putting Get Records, Create Records, Update Records, or Delete Records elements inside loops because repeated SOQL or DML operations can quickly exceed governor limits. Trailhead ' s recommended pattern is to retrieve records before the loop, use assignments while iterating, store changed records in a collection, and perform one database update after the loop. A Collection Filter does not replace the collection used to stage modified records. An Update Records element inside the loop defeats the stated requirement for one database operation. Therefore, Assignment plus a collection variable is the correct architecture.

The correct design is to create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact.
The Account relationship must be master-detail because Salesforce deletes related detail records when the master record is deleted. That matches the requirement that if the Account is deleted, the related Testimonial__c records are also deleted. The Contact relationship must be lookup because the Testimonial__c record must remain when the Contact is deleted. Salesforce lookup relationships can keep the child record and clear the lookup value when the referenced record is deleted.
Why the other options are wrong:
A reverses the required behavior. B would delete the testimonial if either master side caused deletion behavior, which does not fit the Contact requirement. D uses lookup for Account, so it does not guarantee Account deletion will also delete Testimonial__c record