Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (Plat-Admn-202)

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

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

Formula fields can reference fields from related parent records using cross-object formulas, but they cannot directly pull values from multiple child records onto a parent record. Salesforce describes cross-object formulas as formulas that can reference fields from a parent object when the formula is created on the child/detail side of the relationship.

In this case, Account is the parent and Contacts are child records. Since the formula is being created on Account and trying to reference related Contacts, the relationship does not appear in the formula editor.

Correct design alternatives: use a roll-up summary where supported, Flow, Apex, or reporting.

===========

The correct sandbox type is Partial Copy.

A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.

Why the other options are wrong:

Developer and Developer Pro sandboxes are mainly for development and do not copy a production data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

===========

The correct validation rule is:

AND(

ISNEW(),

ISBLANK(Lead.Owner:User.Id)

)

This rule prevents a new Campaign Member from being created when the related Lead does not have a User as owner. Leads can be owned by either a user or a queue, and Salesforce queues can own Lead records.

Salesforce validation rules block a save when the formula evaluates to True. The ISNEW() function checks whether the record is being created, and ISBLANK() checks whether the Lead owner’s User Id is empty.

For owner fields in cross-object formulas, Salesforce requires being explicit about the owner type, such as Owner:User or Owner:Queue .

Why not others:

A is wrong because Lead.Owner.Id is normally populated whether the owner is a user or queue.

B and D focus on queue ownership, but the best exam answer checks that the Lead has an actual User owner when the Campaign Member is created.

The correct answers are C. Unique and D. External ID.

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

The correct answers are B. Set organization-wide default to Private, D. Disable Grant Access Using Hierarchies, and E. Create a criteria-based Sharing Rule for the HR Department.

Set the Review object’s OWD to Private so review records are not visible to all employees by default. Organization-wide defaults define the baseline record access users have to records they do not own.

Disable Grant Access Using Hierarchies because this is a custom object and the requirement says only HR and the submitting employee should see the review. Salesforce allows this setting to be disabled for custom objects so managers higher in the role hierarchy do not automatically inherit access.

Create a criteria-based sharing rule for the HR department so HR can see the Review records even though the default access is private. Salesforce sharing rules are used to grant wider access beyond OWD.

Why others are incorrect:

A is not needed and a Master-Detail relationship to User is not the right access-control design.

C is incorrect because removing Review Read permission from non-HR users would also prevent the submitting employee from viewing their own submitted review.

===========

The correct answer is D.

Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object’s master-detail relationship can’t be converted into a lookup relationship.

In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.

A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.

===========

The correct answer is A. Partial Copy.

A sandbox template is used to define which object data is copied into a sandbox. Salesforce documentation states that sandbox templates control what data is copied into Full or Partial Copy sandboxes. Since the question says the app builder created a sandbox template for Accounts, Projects, and Project Milestones, the correct testing environment is Partial Copy because it includes metadata plus a selected sample of production data defined by the sandbox template. Developer, Developer Pro, and Scratch Orgs do not use sandbox templates for selected production data in this way.

===========

The correct answer is D. The Owner field on the Master record.

In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn’t available and is automatically set to the owner of the related master record.

Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.

A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

===========

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.