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

Flow Builder supports debugging a flow as another user, allowing an administrator to execute the flow under that user ' s profile, permission sets, object permissions, and field-level security. This is exactly what is needed to reproduce a permission-context failure. Salesforce documents the Run flow as another user option under Flow Builder ' s Debug functionality. However, Salesforce also specifies an important current-platform restriction: debugging as another user is supported only in a sandbox/non-production environment . Therefore, the intended solution is C, with the production flow first available in an appropriate sandbox for safe testing. Options A and D require involvement from the sales rep, while B analyzes an existing failure rather than actually reproducing it in the user ' s security context.

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

The correct action is to validate the inbound change set in Production before the deployment window. Salesforce states that an inbound change set can be validated without deploying changes, and validation shows the same success or failure messages that would occur during an actual deployment.

This helps the app builder confirm whether Apex tests, dependencies, and deployment requirements will pass while the developer is away.

Why not others:

A is wrong because removing Apex classes would remove required code.

B is wrong because deployment validation is done from the inbound change set in the target org.

C is not the standard change-set validation process.

The correct answer is B. Use a private sharing model granting record access using hierarchy; manage field access with field-level security.

Cloud Kicks needs two different layers of access control:

First, only the sales rep, their manager, and executives above the manager should view the scorecard record. That is a record-level access requirement. A private sharing model with access opened through the role hierarchy supports this because users above a record owner in the hierarchy can access subordinate-owned records. Salesforce states that the role hierarchy opens access vertically to users higher in the hierarchy.

Second, reps must not see the executive comment fields. That is a field-level access requirement, so it should be handled with field-level security. Salesforce separates record-level access from field-level permissions.

A and C are incorrect because custom settings are not used to grant record access. D includes record types, but record types do not secure individual fields; field-level security is required.

===========

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.

===========

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

The correct answers are A. Processes that update record owners do not transfer child records and C. Processes will fail on records owned by inactive users.

When Process Builder updates a record owner, Salesforce does not automatically transfer associated child records such as related Contacts or other child records. Salesforce documentation says processes that update owners do not automatically transfer associated items, so separate update actions are required for each related record type.

Also, Salesforce documentation states that processes can’t update records owned by inactive users. If records are still owned by inactive users, automation that tries to update them can fail.

B is not the correct consideration here.

D is not the best answer because the issue described is about ownership-based access to Accounts and Contacts, not simply whether a process version is active.

===========

The correct answer is D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.

Universal Containers needs to represent separate business entities because separate bills are sent to each customer and each dealer. In Salesforce, business accounts are used to represent companies or organizations, and contacts represent the people who work for those accounts. Salesforce account hierarchies are used to show relationships between related accounts through the Parent Account field.

So the best model is:

Customer = Account

Dealer = Account

Representative at each business = Contact on that Account

Customer/dealer relationship = Account Hierarchy

A is incorrect because Account Teams represent internal Salesforce users working on an account, not external dealer/customer representatives.

B and C are incorrect because they do not correctly represent separate billing entities as separate Accounts.

===========

A custom link or button that passes the current Account ID into a report filter provides direct access to a report showing only records associated with the Account being viewed. Salesforce ' s official documentation specifically describes creating an Account custom link that opens a report and automatically filters the results by the current Account ' s record ID. This precisely satisfies the requirement for Account owners to access the relevant Asset report from the Account record page. A dashboard filter requires dashboard-level filtering and does not inherently pass the current record context. Scheduled Reports deliver reports at scheduled times, while a Custom Report Type merely defines the objects and fields available for reporting. This corrects the PDF answer key, which lists A; current Salesforce documentation supports B for direct filtered-report access.

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

The correct answers are A. Create an object-specific action on Account and D. Create predefined values for most of the fields.

For this requirement, sales reps need to create a custom Feedback record related to an Account with minimal clicks on mobile. An object-specific quick action is the best solution because it runs in the context of a specific Account record and can create a related child record automatically. Salesforce Trailhead states that object-specific actions let users create records with automatic relationships to other records and provide a streamlined mobile and desktop experience.

Predefined field values reduce manual typing and save mobile users time. Salesforce mobile customization guidance explains that quick actions can include predefined fields, and Trailhead specifically shows predefined values being used to prepopulate fields on action layouts.

B. Create a feedback object as a parent of Account is incorrect because the Feedback record should be related to each Account, normally as a child record or lookup-related record. C. Create a global action on Account is incorrect because global actions create records without record context; Salesforce explains that global actions create records with no relationship to other records, while object-specific actions work in the context of a particular object.

===========

A scheduled path on an after-save record-triggered flow is specifically intended to execute automation at a dynamically calculated time after an individual record-triggering event. The flow should trigger when Project__c.Status transitions to On Hold and schedule the email seven days after that update. Salesforce states that scheduled paths are available for record-triggered flows optimized for Actions and Related Records and can use “When Record Is Created or Updated” as their time source. Using CreatedDate would calculate the delay from record creation rather than when the project became On Hold. A daily schedule-triggered flow could poll records, but it is less precise and unnecessary when Salesforce can queue a per-record scheduled action directly. Thus, C matches the required independent seven-day timer.

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