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

The Custom Error element allows a record-triggered flow to prevent the triggering database change and present a targeted error directly to the user. Salesforce supports displaying the message either at the record-page level or as an inline error on a specific field, which exactly meets the requirement to place the error on the Opportunity Stage field. When the Custom Error element executes, Salesforce rolls back the record change until the user corrects the problem. A Screen element is not valid for providing this experience inside a background record-triggered flow. An Assignment on a fault path merely stores values and does not automatically surface a validation-style error. Ending the flow also does not prevent the record from being saved. Therefore, the Custom Error element is the correct declarative equivalent to validation-style feedback. Salesforce

================

The formula must evaluate true when:

Stage = Negotiation/Review

Close Date < 1 week from today

Salesforce formula functions used:

ISPICKVAL() for picklist equality checks

AND() to combine multiple conditions

CloseDate < TODAY() + 7 to check the Close Date is within one week

Correct formula:

AND(

ISPICKVAL(StageName, " Negotiation/Review " ),

CloseDate < TODAY() + 7

)

Options A, C, D use invalid syntax (missing quotation marks, incorrect function structure).

Salesforce Help confirms correct syntax for picklist comparison and date arithmetic in formula fields. (Salesforce Help)

This formula evaluates true only when both conditions are simultaneously met.

===========

The correct answer is C. Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field.

A roll-up summary field is the recommended declarative solution when Salesforce needs to summarize child-record data on a parent record. Salesforce documentation states that roll-up summary fields calculate values from related records and are defined on the master side of a master-detail relationship.

In this scenario, Opportunity is the parent and Detailed_Sales__c is the child. The roll-up summary field can summarize sales metrics and use filter criteria so only child records where Status = Active are included.

Why others are incorrect:

A is incorrect because a third-party AppExchange app is unnecessary when native roll-up summary functionality meets the requirement.

B is incorrect because Apex is not recommended when a declarative feature can solve the requirement.

D is incorrect because lookup relationships do not support standard roll-up summary fields. Salesforce documentation states that lookup relationships are similar to master-detail relationships, except they do not support roll-up summary fields.

===========

When deploying from a sandbox on a newer Salesforce version to production on a current version, any components that rely on features not yet available in production will fail.

Change sets do not automatically upgrade production.

All features must be supported in the target org at deployment time.

Salesforce documentation notes that compatibility issues may occur if components use version-specific features, and deployments must be tested against the target org’s current version. (Salesforce Help)

A is incorrect because deployments do not automatically wait for production upgrades.

B is partially true, but deployments are possible if features are supported.

C is incorrect; components are not automatically upgraded.

===========

The correct solution is component visibility with advanced filters. Lightning App Builder allows components on Lightning pages to be shown or hidden dynamically based on filter criteria. Salesforce Admin guidance also explains that App Builder filters can customize which components display on record pages and can use field values from related records, running user, and permissions.

Because the component must display dynamically based on criteria about the related Contact, the app builder should use an advanced visibility filter using the Contact field criteria.

Why not others:

A. Related Record component displays related record data but does not solve dynamic visibility by itself.

B. Hiding behind a tab does not dynamically control visibility.

C. Custom permission controls visibility by user permission, not by related Contact field criteria.

When deploying from sandbox to production using Change Sets, the following are critical considerations:

A. Transactions will revert if the deployment errors – Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.

D. Change sets do not include all components and may require manual configuration – Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.

Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)

B. Users being logged out is not required; deployments can occur while users are logged in.

C. Salesforce Connect does not automatically link environments; it is unrelated to change sets.

===========

The correct answer is B. Quick action.

Sales reps need to create Opportunity records directly from an Account, with several fields prepopulated. This is an object-specific Quick Action use case. Salesforce states that object-specific actions let users create or update records in the context of a particular object. Salesforce also supports predefined field values for quick actions, which can prepopulate fields and make record creation faster.

Default action is not the correct feature name for this requirement. Custom button and custom link are older navigation-style tools and are not the best Lightning/mobile-friendly option for creating related records with predefined values.

===========

The correct answer is B. Master-detail relationship.

Cloud Kicks needs two things: count Gift Card records on the Account and prevent Gift Cards from being moved to another Account after creation. A master-detail relationship supports both requirements.

First, master-detail enables a roll-up summary field on Account to count related Gift Card records. Salesforce documentation confirms that roll-up summaries work from detail records up to the master record.

Second, master-detail relationships prevent reparenting by default. Salesforce documentation states that records cannot be reparented in master-detail relationships by default, although admins can allow reparenting if they choose.

A is incorrect because a lookup relationship does not support standard roll-up summary fields and does not permanently lock the parent Account by default.

C is incorrect because roll-up summary is a field on the parent Account, not the relationship field type on Gift Card.

D is incorrect because a formula cannot count related child records or enforce parent locking.