Pass the Salesforce App Builder Platform-App-Builder Questions and answers with CertsForce

Opportunities are in a master-detail-like relationship with Accounts (standard lookup behaves with special roll-up capabilities). Salesforce provides a standard roll-up summary feature on the Account object to count related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why not A:Formula fields cannot count related records.

Why not C:AppExchange is not required; Salesforce provides native functionality.

Why not D:A lookup only links records—it does not perform aggregation.

Guided Action Flows (Screen Flows embedded in Lightning record pages) can walk agents through required steps — such as verifying identity — before proceeding.

Why A (Guided Action Flows) is correct:Exact Extract:“Use Guided Action Flows in Lightning App Builder to help agents complete processes in a step-by-step format directly on a record page.” — Salesforce Help | Guided Action FlowsThe app builder can embed a Screen Flow that prompts the agent to verify identity (e.g., asking security questions), then allows access or marks verification complete.

Why A (Guided Action Flows) is correct:Exact Extract:“Use Guided Action Flows in Lightning App Builder to help agents complete processes in a step-by-step format directly on a record page.” — Salesforce Help | Guided Action FlowsThe app builder can embed a Screen Flow that prompts the agent to verify identity (e.g., asking security questions), then allows access or marks verification complete.

Why not B:Path helps users track record stages, not enforce procedural steps.

Why not C:Surveys are used for feedback collection after cases, not real-time identity verification.

Why not D:Validation Rules enforce data quality on record save, not process guidance.

The solution that an app builder should use to meet this requirement is creating a custom report type with converted leads as the primary object. A custom report type is a template that defines the objects and fields that are available for a report. The app builder can create a custom report type that has converted leads as the primary object and includes fields from related objects, such as accounts, contacts, and opportunities. This way, sales reps can create reports on converted leads and see their related information. Option A is incorrect because enabling preserve lead status in the lead conversion settings does not affect the reporting on converted leads, but rather allows users to retain the original lead status after conversion. Option B is incorrect because assigning the representative view and edit converted leads permission does not affect the reporting on converted leads, but rather allows users to view and edit converted lead records. Option C is incorrect because ensuring the representative has read access to the original lead records does not affect the reporting on converted leads, but rather allows users to view the original lead records.

An AppExchange solution is a pre-built application or component that can be installed from the Salesforce AppExchange, which is an online marketplace for Salesforce products. AppExchange solutions can help you meet your business needs quickly and efficiently, without requiring much development effort or expertise. You can browse and search for AppExchange solutions by category, industry, rating, price, and more.

Lookup is the type of relationship that would be set up to meet the specification of pairing experienced Realtors with new Realtors. According to the Salesforce documentation, “A lookup relationship creates a loose association between objects. The lookup field allows users to select a record from another object.” Indirect lookup is used for junction objects on different platforms. Many-to-many is not a type of relationship, but a result of using junction objects. Master-detail is used for creating parent-child relationships.

 The recommended solution to grant the customer service agent access to the field is creating a permission set that allows read-only access to the field via Field Level Security and assigning it to the agent. A permission set is a collection of settings and permissions that give users access to various tools and functions. Field Level Security (FLS) is a setting that controls the access level of fields for different profiles or permission sets. The app builder can create a permission set that grants read-only access to the custom field on the account object via FLS and assign it to the agent. Option B is incorrect because creating a new profile to allow for read-only access to the field via FLS and assigning it to the agent is not recommended, as profiles are used to define the baseline permissions and settings for a group of users, and creating multiple profiles for individual users can be hard to maintain. Option C is incorrect because updating the Customer Service Profile already assigned to the agent to allow for read-only access to the field via FLS is not recommended, as this will affect all users who have the same profile, which may violate the security policy. Option D is incorrect because updating the custom field’s FLS in setup to allow the agent read-only access to the field is not possible, as FLS can only be set at the profile or permission set level, not at the user level.

Send an email alert, update a related record, and create a child record are three capabilities of Process Builder that can improve productivity for the sales team. Process Builder can automate these actions based on criteria or events that occur on records or objects. Send an outbound message and delete a related record are not capabilities of Process Builder, but of other tools such as Workflow Rules or Apex.

The requirement is to automatically grant record visibility to all users in a specific role (Service Manager) based on record criteria (“Opportunity Type = Service Agreement”).

This is a textbook case for a criteria-based sharing rule.

Why C (Criteria-Based Sharing Rule) is correct:Exact Extract:“A criteria-based sharing rule determines which records to share based on field values, rather than who owns the record.” — Salesforce Help | Sharing Rules OverviewYou can define the rule to share all Opportunities where Type = 'Service Agreement' with all users in the Service Manager role.Exact Extract:“Use criteria-based sharing rules to share records based on record field values with roles, roles and subordinates, or public groups.” — Salesforce Help | Criteria-Based Sharing Rules

Why C (Criteria-Based Sharing Rule) is correct:Exact Extract:“A criteria-based sharing rule determines which records to share based on field values, rather than who owns the record.” — Salesforce Help | Sharing Rules OverviewYou can define the rule to share all Opportunities where Type = 'Service Agreement' with all users in the Service Manager role.Exact Extract:“Use criteria-based sharing rules to share records based on record field values with roles, roles and subordinates, or public groups.” — Salesforce Help | Criteria-Based Sharing Rules

Why not A (Manual Sharing):Manual sharing requires a user to share each record individually — it is not automated.

Why not B (Owner-Based Sharing Rule):Owner-based rules share records based on who owns them, not on a record field value.

Why not D (Apex Sharing Rule):Apex sharing is used only when declarative sharing rules cannot meet the requirement. In this case, a standard criteria-based rule is sufficient.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Sharing Rules Overview

Salesforce Help | Criteria-Based Sharing Rules

Salesforce Platform App Builder Exam Guide | Security

To allow quick editing of a record's status and entering a due date from the record's feed in the Salesforce Mobile App:

A. Custom action. This option enables users to perform specific tasks directly from the record page in the Salesforce Mobile App, such as editing fields.

Steps to create a custom action:

Navigate to Setup → Object Manager → select the relevant object.

Click Buttons, Links, and Actions → New Action.

Set Action Type to 'Update a Record'.

Configure the action layout to include the Status and Custom Due Date fields.

Add the action to the Salesforce Mobile layout.

This setup provides an efficient way for users to update key fields without navigating away from the record feed.

For detailed setup instructions, see Salesforce's documentation on Creating Quick Actions.