Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Free Practice Exam Questions (2025 Updated)

 A summary report on the opportunity object should be created to add to the account page layout. A summary report groups rows of data by common values and allows users to create charts based on aggregate values. A summary report on the opportunity object can group opportunities by stage and display a chart of all related opportunities on the account detail page.

When a master-detail relationship is created between two objects, Salesforce automatically creates a standard report type that allows users to report on the parent and child together.

Why A (Galaxy__c with Star__c) is correct:Exact Extract:“When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail.” — Salesforce Help | Standard Report TypesTherefore, a “Galaxy__c with Star__c” report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).

Why A (Galaxy__c with Star__c) is correct:Exact Extract:“When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail.” — Salesforce Help | Standard Report TypesTherefore, a “Galaxy__c with Star__c” report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).

Why not B:The parent-to-child relationship drives the report type. A “Star__c with Galaxy__c” type is not automatically created.

Why not C or D:Custom report types are only needed if you want to include additional related objects or modify relationships; Salesforce automatically provides one for master-detail pairs.

The requirement is to copy the parent Account’s Billing State onto a custom field on Opportunity at the moment the Opportunity is created, and keep that value static thereafter.

Why not Formula (B): A formula would always recalculate, so the value would change if the Account’s Billing State later changes.Exact Extract: “Formula fields are read-only fields that automatically recalculate their values when any referenced fields change.” — Salesforce Help | Formula Fields

Why not Roll-Up Summary (A): Roll-up summary fields only summarize child records onto a master (parent) record; they do not copy values from a parent (Account) down to a child (Opportunity), and they can’t summarize a text/state value.Exact Extract: “A roll-up summary field calculates values from related records, such as those in a related list, on a master record.” — Salesforce Help | Roll-Up Summary Fields

Why Flow (C) is correct: A Record-Triggered Flow on Opportunity (when a record is created) can set a field value by referencing the related Account (e.g., Opportunity.Account.BillingState) and writing it into a dedicated “snapshot” field (e.g., Billing State at Create__c). Because this is a one-time assignment on create, the value remains static unless intentionally updated by further automation.Exact Extract 1: “Use Flow Builder to automate business processes by collecting data and performing actions in your Salesforce org.” — Salesforce Help | Flow BuilderExact Extract 2: “Record-triggered flows launch when a record is created, updated, or deleted, and can update fields on the triggering record.” — Salesforce Help | Record-Triggered Flows

Why Apex (D) is not preferred: While Apex could do the same copy-on-create, Salesforce’s recommended approach is to use declarative automation (Flow) when possible.Exact Extract: “Before considering Apex, evaluate whether your solution can be implemented with declarative tools such as Flow.” — Salesforce Architect Guidance | Clicks, Not Code

Implementation note (for clarity): Create a custom text field on Opportunity, e.g., Billing State at Create (Billing_State_at_Create__c). Build a Record-Triggered Flow:

Trigger: Opportunity — “A record is created”

Get or use the related Account from the $Record.AccountId relationship

Update the new Opportunity field with Account.BillingState

Do not run the flow on updates

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

Salesforce Help — Formula Fields

Salesforce Help — Roll-Up Summary Fields

Salesforce Help — Flow Builder

Salesforce Help — Record-Triggered Flows

Salesforce Architect Guidance — Clicks, Not Code

Salesforce Platform App Builder Exam Guide — Business Logic and Process Automation

 Marking stage dependent fields as required on the Opportunity page layout is a good solution to improve efficiency and data quality, as it ensures that users enter the necessary information for each stage of the sales process. Adding a Path component with fields and instructions aligning to stages on the Opportunity is another good solution to improve efficiency and collaboration, as it provides guidance and best practices for users to move the Opportunity along the sales cycle. Using two Tabs components to separate record information from activities may not be an optimal solution, as it may reduce the visibility and accessibility of important data. Setting up an approval process requiring manager consent at each stage of the Opportunity may not be a feasible solution, as it may introduce unnecessary delays and complexity in the sales process

The solution that an app builder should use to meet this requirement is master-detail relationship. A master-detail relationship is a type of relationship that creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a master-detail relationship between Supplier__c and SupplierItem__c objects, where Supplier__c is the parent object and SupplierItem__c is the child object. This way, when a Supplier__c record is deleted, all related SupplierItem__c records are also deleted automatically. Option A is incorrect because many-to-many relationship is not suitable for this requirement, as many-to-many relationship allows two objects to be linked in both directions through a junction object, but does not support cascading delete. Option B is incorrect because indirect lookup relationship is not suitable for this requirement, as indirect lookup relationship allows an external object to link with another object using an external ID field, but does not support cascading delete. Option C is incorrect because hierarchical relationship is not suitable for this requirement, as hierarchical relationship allows users to use a lookup field that links an object with itself, but does not support cascading delete.

 Sales rep B has implicit access to the Account because of the manual sharing of the Opportunity. Implicit sharing grants access to parent records when a user has access to a child record. Sales rep B was not added to the Account team, sharing set is not applicable for private sharing model, and Account was not manually shared.

For Universal Containers to understand the return on investment (ROI) for their latest advertising buy while using a private security model, the best recommendation is to use Campaign Hierarchies and Campaign statistics.

Campaign Hierarchies and Campaign Statistics: Campaign hierarchies allow Universal Containers to track the effectiveness and ROI of marketing efforts by grouping related campaigns (e.g., advertising buys) under a parent campaign and rolling up key metrics like responses, converted leads, and won opportunities. Campaign statistics provide detailed insights into individual and aggregate campaign performance, helping calculate ROI.

This method works well within a private security model since it respects existing sharing rules and access controls, ensuring that only authorized users can see the campaign data.

Campaign Management Overview

Option A (Account Hierarchies and Roll-Up Summary fields): Account hierarchies and roll-up summary fields focus on aggregating account-level data, which doesn’t directly support measuring the ROI of advertising campaigns.

Option B (Opportunities Pipeline Report): While an opportunities pipeline report can provide insights into sales, it doesn’t track campaign-related data or advertising ROI directly.

Option C (Change to a Public Security Model): Changing to a public security model isn’t necessary and could expose sensitive data. Campaign hierarchies and statistics work well with a private security model.

In summary, Campaign Hierarchies and Campaign Statistics are the recommended approach to track the ROI of advertising buys.

The requirement is time-based (Case in New status > 4 business hours) and requires a notification.

Escalation Rules can monitor case age and trigger escalation or notifications after a specified period.

Flow Builder (Scheduled Path or Scheduled Trigger Flow) can be used to evaluate business hours and send alerts.

Why B (Escalation Rules) is correct:Exact Extract:“Escalation rules automatically escalate cases when they meet certain criteria, such as the age of the case, and can notify users or change ownership.” — Salesforce Help | Case Escalation RulesEscalation rules are ideal for service teams and time-based escalation scenarios.

Why B (Escalation Rules) is correct:Exact Extract:“Escalation rules automatically escalate cases when they meet certain criteria, such as the age of the case, and can notify users or change ownership.” — Salesforce Help | Case Escalation RulesEscalation rules are ideal for service teams and time-based escalation scenarios.

Why D (Flow Builder) is correct:Exact Extract:“Use scheduled paths in record-triggered flows to perform actions after a certain amount of time has passed since the record was created or updated.” — Salesforce Help | Scheduled Paths in Flow BuilderA Scheduled Path in a record-triggered flow can evaluate the Case’s age in hours and send an email alert if the Status remains “New.”

Why D (Flow Builder) is correct:Exact Extract:“Use scheduled paths in record-triggered flows to perform actions after a certain amount of time has passed since the record was created or updated.” — Salesforce Help | Scheduled Paths in Flow BuilderA Scheduled Path in a record-triggered flow can evaluate the Case’s age in hours and send an email alert if the Status remains “New.”

Why not A:Validation Rules prevent saving invalid data but cannot evaluate elapsed time.

Why not C:Scheduled Apex would work technically but is a code-based solution; declarative automation (Flow or Escalation) is preferred for App Builder certification.

When a field is added to an object, it doesn’t automatically appear in custom report types — even if the field is visible and reportable. The app builder must manually add the field to the custom report type layout to make it available in reports.

Why D (Add the field to the custom report type field layout) is correct:Exact Extract:“If a new custom field isn’t available in your report builder, edit the custom report type layout and add the field. Fields created after the report type was built must be added manually.” — Salesforce Help | Custom Report Types

Why not A:Field-level security controls visibility but not inclusion in the report type layout.

Why not B:“Allow Reports” affects whether the entire object is reportable, not individual fields.

Why not C:The “Manage Public Reports” permission allows editing public reports but doesn’t influence field visibility.

A text-only Visualforce page can be used to show a text notification on a case record page based on a condition. The Visualforce component can be dragged into the Case Lightning page and its visibility can be set to show when the account support level is platinum. This is the simplest and most flexible way to meet the requirement

A master-detail relationship between two objects automatically creates a report type that includes both objects. The app builder does not need to create a custom report type for this scenario. The report type will have the format of Parent object with Child object

The Highlights Panel in the Lightning Record Page displays key fields and record actions prominently at the top of the page, exactly as described in the requirement.

Why A (Highlights Panel) is correct:Exact Extract:“The highlights panel displays important fields and key record actions at the top of the record page in Lightning Experience.” — Salesforce Help | Highlights Panel

Why not B:Path is used to visualize progress through stages (e.g., Opportunity Stage), not display multiple fields.

Why not C:A custom component is unnecessary since the standard Highlights Panel fulfills the requirement.

Why not D:Accordion is used to organize information in collapsible sections, not display key fields at the top.

To meet the requirement of summarizing the number of open and closed cases on an Account, two potential automation solutions can be used:

Option A (AppExchange): Salesforce AppExchange offers various pre-built apps and components, including those for case management, which could provide the functionality to summarize cases and categorize customer support utilization. Many apps can handle complex business requirements like case summary roll-ups and could meet the needs without custom development.

Salesforce AppExchange

Option D (Apex): Apex is Salesforce’s programming language that allows developers to implement custom logic. In this scenario, Apex could be used to create a trigger or scheduled job that calculates the number of open and closed cases and updates the Account record accordingly. Apex would allow full customization of how the open/closed case numbers are calculated and how customer support utilization (high, medium, low) is determined.

To track the total number of trails associated with a park without writing code, the correct actions to take are:

Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.

Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.

A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.

For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:

Master-Detail Relationship: https://help.salesforce.com/articleView?id=relationships_considerations.htm &type=5

Roll-Up Summary Fields: https://help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm &type=5

 To manually share individual records with specific people or group of people on a case by case basis, users can use public groups, roles, or users. Public groups are collections of users, roles, or other groups that can be used to share access to records. Roles define the level of access that users have to their organization’s data based on their position in the hierarchy. Users are individual people who log in to Salesforce and have access to records based on their profile, role, and sharing settings. 

The category that handles bug fixes and simple changes is minor. A minor release is a type of release that introduces small enhancements or fixes to existing functionality, such as correcting spelling errors or improving performance. A minor release usually has a low impact on users and does not require extensive testing or training. A patch release is a type of release that addresses critical issues or defects that affect the functionality or security of an application, such as fixing broken links or resolving vulnerabilities. A patch release usually has a high impact on users and requires immediate deployment. A major release is a type of release that introduces new functionality or features to an application, such as adding new objects or components or changing business processes. A major release usually has a high impact on users and requires extensive testing and training. A rollback is not a type of release, but an action that reverses a release that has been deployed to an environment, such as undoing changes or restoring previous versions. A rollback may be necessary if a release causes errors or issues that affect the functionality or performance of an application.

 Setting email deliverability to no access would prevent outbound email sends during testing in a sandbox. This would ensure that no emails are sent to any users or external email addresses from the sandbox. Setting email deliverability to system email only would still allow some emails to be sent, such as password reset emails or new user emails. Configuring SMTP authentication or email relay would not affect email deliverability in a sandbox

For reporting snapshots, the source report must be capable of grouping data, which is necessary for summarizing information at specific intervals. The acceptable formats for a source report in reporting snapshots are:

Summary format (B). This format groups rows of data by one or more criteria and can perform calculations such as sum, average, etc., on another column at each group level.

Matrix format (D). Similar to the summary format but arranges data in a grid format, allowing summarization by both rows and columns.

Tabular (A) and joined (C) formats are not suitable for reporting snapshots. Tabular reports do not include grouped or summarized data, and joined reports involve combining multiple report types, which are not compatible with how reporting snapshots need to structure data.

Reference for more information on reporting snapshots and report formats:

Reporting Snapshots: https://help.salesforce.com/articleView?id=reports_snapshots.htm &type=5

Report Formats: https://help.salesforce.com/articleView?id=reports_understanding_formats.htm &type=5