Free Practice Questions for Salesforce Platform-App-Builder Exam

 Partial Copy is the type of testing environment that the app builder should create to use a sandbox template for Accounts, Projects, and Project Milestones. According to the Salesforce documentation, “Partial Copy sandboxes copy your production org’s configuration (metadata) and some of your production org’s data as defined by a sandbox template.” Developer, Developer Pro, and Scratch Org are not types of testing environments that support sandbox templates.

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 two reasons that could be preventing this relationship conversion are that there are already two master-detail relationships on the Invoice Line Item and that Invoice Line Item records exist without having the Invoice lookup field populated. A custom object can have up to two master-detail relationships, so adding another one would exceed the limit. Also, a master-detail relationship requires that the detail records have a value in the master lookup field, so any records with a blank Invoice lookup field would prevent the conversion.

An Approval Process is the appropriate feature to manage and enforce that new vendors accept terms on agreements before an opportunity can be closed. This process can be configured to require approvals from designated approvers when certain conditions are met, ensuring that all necessary agreements are in place and validated before proceeding.

A: Email Alert cannot enforce acceptance of terms.

B: Dynamic Action primarily adjusts the user interface based on field values, not process management.

When multiple objects require the same picklist values, the correct approach is to create a Global Picklist Value Set (also called a Global Value Set). This allows an organization to maintain one centralized list of picklist values that can be reused across multiple picklist fields on different objects.

Why C is correct:Exact Extract:“Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields.” — Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.

Why C is correct:Exact Extract:“Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields.” — Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.

Why not A (Related Picklist):“Related Picklist” is not a valid Salesforce feature.

Why not B (Shared Custom Field):Salesforce does not provide a “Shared Custom Field” functionality. Each field belongs to a specific object.

Why not D (Dependent Picklist):Dependent picklists control available values based on another field’s value. They do not allow reuse of a single value list across multiple objects.

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

Salesforce Help | Global Value Sets

Salesforce Help | Picklist Fields

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

The best solution to create a report to compare the number of support cases in each status and by priority is to use grouping. Grouping allows the app builder to summarize data by one or more fields, such as status and priority, and display them in rows and columns. Grouping also enables the app builder to use different chart types, such as stacked bar charts or matrix charts, to visualize the data. Bucket columns are not a suitable solution, as they are used to categorize data into predefined groups, such as high, medium, or low. Custom report types are not a suitable solution, as they are used to define the objects and fields available for a report, not how to display them. Filters are not a suitable solution, as they are used to limit the data shown in a report based on certain criteria, not how to compare them

The three reasons user A has access but user B is unable to access the record are:

User A is on the same account team as user C. Account teams are groups of users who work together on an account. Users who are on an account team can have access to the account and related records owned by other team members.

User C has manually shared the record with user A. Manual sharing is a way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy.

User A is in a public group that has access via a sharing rule. Public groups are groups of users who can be used to share data or assign permissions. Sharing rules are automatic rules that grant access to groups of users based on certain criteria. Option B and D are not reasons for user A’s access.

 The app builder wants to create a formula field on an Account to include data from related Contacts but cannot find the relationship in the formula editor. This limitation occurs because formula fields in Salesforce cannot reference child records directly.

Option A (Unable to reference the child records): In Salesforce, formula fields can reference parent objects but not child objects. In this case, Contacts are child records of Accounts in a lookup relationship, and Account is the parent. This is why the formula editor does not provide access to the child records (Contacts) from the Account.

Formula Field Considerations

Option B (A master-detail relationship should be created): While master-detail relationships allow for roll-up summaries, creating a master-detail relationship is not applicable here since the standard Account-Contact relationship is a lookup, and changing it to master-detail is not possible.

Option C (Formula field limit reached on the Account object): This would limit the number of formulas but is not the root cause of the issue described.

Option D (More than 5,000 characters in the formula): This limit refers to formula field complexity, but it does not explain the inability to reference child records.

In summary, the limitation is due to Salesforce not allowing formula fields to reference child records.

If an employee attempts to edit the description field after submitting an opportunity for approval, they will be presented with a ‘Record Lock’ notification. This means that the record is locked for editing while it is in the approval process and only users with the “Modify All” permission or users above them in the role hierarchy can edit it. [Source]