Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 3

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.

===========

In-App Guidance is Salesforce ' s native capability for contextual onboarding, feature adoption, prompts, and guided walkthroughs directly inside Lightning Experience. Salesforce documents that administrators can create prompts and walkthroughs, determine the target audience, and specify where and when that guidance appears. Targeted prompts can highlight a specific page element, while walkthroughs connect multiple prompts into a step-by-step guided experience. This aligns directly with Universal Containers ' goals of increasing adoption and guiding users through a newly launched application. A Screen Flow is appropriate when collecting information or executing an interactive business process, but it is not the dedicated adoption feature. Dynamic Actions control which actions appear, while Dynamic Forms controls field and section presentation. Neither provides structured onboarding walkthroughs.

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

A roll-up summary field requires a master-detail relationship. Since Galaxy__c and Star__c currently have a lookup relationship, the app builder cannot create a standard roll-up summary field to count related Star__c records. The lookup must be converted to master-detail first, with Galaxy__c as the master and Star__c as the detail. Salesforce Trailhead confirms that roll-up summary fields display values on the master record based on directly related detail records in a master-detail relationship.

===========

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 correct answer is A. Existing reports created under the Sun__c with Planet__c report type made by Salesforce will be unusable, but not deleted.

When a relationship is changed from master-detail to lookup, the available standard report types can change. Salesforce documentation notes that converting a lookup relationship to master-detail or vice versa can make existing custom reports unusable because of differences in available standard report types.

B is incorrect because roll-up summary fields are not automatically deleted from reports as part of the conversion. In fact, Salesforce states that a master-detail relationship cannot be converted to lookup while roll-up summary fields exist on the master object.

C is incorrect because roll-up summary fields do not remain and simply stop updating.

D is incorrect because the reports are not deleted; they become unusable.

===========

The correct answer is C.

To show Component records as a related list on Product, the app builder should create a relationship field on the child object, Component, pointing to the parent object, Product. Salesforce documentation explains that when a lookup relationship is defined, the lookup field is added on one object and a related list can be shown on the associated object’s page layout.

A is unnecessary unless the requirement is many-to-many. B is incorrect because a roll-up summary does not create a related list. D is incorrect because the relationship field direction is wrong; the field should be on Component, not Product.

===========

The correct answers are A and B .

The requirement is to display a visual flag image based on Case Priority. Salesforce’s own sample image formula for Case Priority uses the IMAGE() function with CASE() to display green, yellow, or red flag images.

Both formulas are valid because:

A uses IMAGE() with nested IF() and ISPICKVAL() checks.

B uses IMAGE() with CASE() to return the correct image URL.

C and D are incorrect because they return only the image URL text, not the actual image. The formula must use IMAGE() to display a visual flag.

===========

The correct answer is D.

Service agents need a guided process to confirm a user’s identity before sharing support information. Salesforce Flow for Service supports guided action flows through the Actions & Recommendations component on a record page. This lets agents follow step-by-step prompts, such as identity verification questions, directly from the Case record. Salesforce Trailhead explains that Flow for Service shows users a to-do list on a record page, and selecting a step can launch a flow that guides the rep through the task.

A. Path is for guiding users through stages, not collecting identity-verification prompts. B. Validation Rules only block invalid saves. C. Surveys collect feedback, not identity confirmation during a support call.

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.

Flow Orchestration is designed for sophisticated, long-running business processes that coordinate multiple flows, users, teams, and stages. Salesforce distinguishes ordinary Flow from Orchestration by describing flows as primarily record-centric, whereas orchestrations are user-centric and coordinate processes involving different people and different parts of an organization. Interactive orchestration steps can create work items and assign them to individual users, groups, or queues, making them suitable for onboarding activities distributed across multiple participants and days. A Screen Flow can guide one interactive session but is not the strongest choice for coordinating long-running work across multiple users. Entitlement processes are primarily service-management mechanisms, and a custom LWC would introduce unnecessary development. The multi-user, multi-stage nature of the requirement therefore directly aligns with Flow Orchestration. Salesforce

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