The correct answer is D. Record-triggered flow.

The requirement is automatic: when an Account Type changes to Past-Customer, all directly related Contacts must have their Status updated to Re-Market. A record-triggered flow is the correct declarative automation because it can run when an Account record is updated and then update related Contact records. Salesforce describes record-triggered flows as automation that runs automatically when records are created, updated, or deleted. Salesforce also documents that Flow can update records related to the record that triggered the flow.

Validation rules only prevent invalid saves. Lightning components are UI elements. Screen flows require user interaction, while this requirement needs background automation.

===========

The lookup field is created on the custom object Box and points to Account. That makes Account the parent-side object and Box the related child object. Salesforce automatically creates a standard relationship report type in the format Parent Object with Child Object, so the report type is Accounts with Boxes. Salesforce Help confirms that standard report types can be generated automatically when reportable custom objects have lookup relationships.

Why others are incorrect:

A. Boxes with Accounts starts from the child object perspective.

C and D include “with or without,” which is normally configured through custom report type relationship options, not the automatically created standard relationship report type.

===========

The correct answers are A. Data loss may occur when changing custom field types and D. Field History Tracking records value changes of 255 characters or less.

A is correct because Salesforce warns that changing the data type of an existing custom field can cause data loss in certain situations. This is a key consideration before converting Text Area (Long) fields to Rich Text Area fields.

D is correct because Salesforce field history tracking has a character limitation. Salesforce tracks changes to fields with more than 255 characters as edited, but it does not record the old and new values. That means long/rich text changes beyond that limit do not provide full before-and-after history values.

Why others are incorrect:

B is not the relevant consideration for this field conversion requirement.

C is incorrect because Salesforce reports do not display rich text field values of all lengths fully; Salesforce documentation notes report display limits for long text and rich text area fields.

===========

The correct answer is C. Schema Builder.

Schema Builder is designed to help app builders visualize the Salesforce data model, including standard objects, custom objects, fields, and relationships. Salesforce Trailhead states that Schema Builder lets users visualize and edit the data model and is useful for understanding complex data models.

Object Manager and Fields & Relationships are used to configure individual objects and fields, but they do not provide the same visual relationship map. Lightning App Builder is for page layout and UI configuration, not data-model visualization.

The correct answer is C. Unable to reference the child records.

A formula field on Account cannot directly pull data from multiple related Contact records because Contacts are child records of Account. Cross-object formulas work by referencing fields through supported parent relationships, not by traversing from a parent record down to multiple child records. Salesforce documentation describes cross-object formulas as formulas that reference fields on related objects, especially parent records through relationships.

Because an Account can have many Contacts, Salesforce does not expose that child relationship in the formula editor as a single field reference. For summarized child data, the app builder would normally use a roll-up-style solution where supported, or automation such as Flow.

A is unrelated unless the formula has already exceeded character limits.

B is misleading because the core issue is not simply that Account and Contact lack master-detail; it is that formulas cannot directly reference child records.

D is not supported by the scenario.

===========

The correct answer is C.

A Partial Copy sandbox uses a sandbox template to determine which objects and data are copied from production. Salesforce states that sandbox templates let admins select specific objects and data to copy to a Full or Partial Copy sandbox. If the custom object Shipping was not included in the sandbox template, its production records would not be copied into the refreshed partial sandbox.

Why others are incorrect:

A is not the likely issue; refresh timing does not explain one object having no data.

B is less likely as the scenario points to template selection.

D is not the best answer because capacity may limit copied data, but missing all data for a specific object usually indicates the object was not selected in the sandbox template.

===========

The correct answer is B. Feed Tracking.

DreamHouse Realty wants changes to selected fields, such as Asking_Price__c and Real_Estate_Agent__c , to appear prominently in Chatter. This is exactly what Chatter Feed Tracking is used for.

Salesforce documentation states that feed tracking is available for record fields and can be configured for custom objects. Salesforce guidance also says admins can enable feed tracking from Setup, select an object, enable feed tracking, and choose fields to track.

A. Topics is used for categorizing Chatter posts, not automatically tracking field changes.

C. Pin Field is not the Chatter feature for tracking field updates.

D. Publisher Actions are actions users can take from the publisher, not automatic field-change tracking.

===========

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

The validation must happen when a Contact is saved because the missing field is Region on the Contact record. Salesforce validation rules evaluate data before a record is saved and return an error when the formula evaluates to True.

The app builder can create a validation rule on Contact that checks the related Account’s Customer Status field and requires Region only when the Account is marked High Priority.

Example logic:

AND(

ISPICKVAL(Account.Customer_Status__c, " High Priority " ),

ISBLANK(Region__c)

)

Why others are incorrect:

A is wrong because the missing field is on Contact, not Account.

B is wrong because Customer Status being required does not require Contact Region.

D is wrong because it would require Region for all Contacts, not only High Priority Account Contacts.

===========

To embed a chart on the Account detail page showing related Opportunities by Stage, the report must summarize Opportunities, not just list them. Salesforce documentation specifies that summary reports allow grouping by fields (e.g., Stage) and can be used in Report Chart components. (Salesforce Help)

Tabular reports cannot be grouped and therefore cannot provide the aggregated chart needed.

The report must be built on the Opportunity object because the records being summarized are Opportunities, not Accounts.

===========