The correct answer is B. Create both customer and dealer as accounts, add each rep as a contact to the corresponding account and create an account hierarchy.
Customers and dealers are both separate business entities, and separate bills are sent to each. In Salesforce, business entities are best represented as Accounts, while the single individual at each business should be stored as a Contact under the correct Account. Salesforce account hierarchy is used to show parent-child relationships between related accounts.
Why not D? Account Teams represent internal Salesforce users working on an account, not external customer/dealer representation.

The correct answer is D. Sum.
Cloud Kicks wants the total value of all won Opportunities displayed on the Account record. In a roll-up summary field, SUM totals the values in a selected numeric/currency field, such as Opportunity Amount. Salesforce documentation identifies SUM as the roll-up summary type used to total values in the selected field.
The app builder would create a roll-up summary field on Account, summarize Opportunities, use SUM on the Amount field, and apply filter criteria for won Opportunities, such as Stage equals Closed Won.
A . Count would only count the number of Opportunities.
B . Total is not the Salesforce roll-up summary type name.
C . Aggregate is not the specific roll-up summary option used here.

The correct answer is B. Unable to reference the child records.
Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.
However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.
A is incorrect because the issue described is about relationship direction, not the number of formula fields.
C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.
D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

The correct answer is B. Universal Containers has internal Account OWD set to Public Read/Write, which lets internal users broadly access Account records. However, Experience Cloud / customer community users can have a separate external sharing model. Salesforce documentation explains that External Organization-Wide Defaults provide separate default access for external authenticated users so companies can better secure data for community users.
Setting the Account external OWD to Private prevents customer community users from seeing all company Account records by default.
Why others are incorrect:
A record types do not control record visibility.
C an owner-based sharing rule would grant more access, not restrict default access.
D permission sets grant object/field permissions; they do not replace OWD record-sharing control.

The correct answer is A. Configure Campaign Interactions and Campaign statistics.
The option text appears to contain an OCR/wording issue. The intended Salesforce feature is Campaign Hierarchies and Campaign statistics. For advertising ROI, Salesforce Campaigns are the correct feature because Campaign ROI reports calculate return on investment using campaign cost and won opportunity value. Salesforce also states that campaign hierarchy metrics roll up from child campaigns to parent campaigns, which helps analyze campaign performance across related marketing efforts.
B is incorrect because Account interactions and roll-up summary fields are not the standard marketing ROI solution.
C is incorrect because changing the whole org to a public security model is unnecessary.
D is incorrect because an opportunity pipeline report alone does not provide campaign ROI analysis.