Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Questions and Answers

The correct design is to create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact.

The Account relationship must be master-detail because Salesforce deletes related detail records when the master record is deleted. That matches the requirement that if the Account is deleted, the related Testimonial__c records are also deleted. The Contact relationship must be lookup because the Testimonial__c record must remain when the Contact is deleted. Salesforce lookup relationships can keep the child record and clear the lookup value when the referenced record is deleted.

Why the other options are wrong:

A reverses the required behavior. B would delete the testimonial if either master side caused deletion behavior, which does not fit the Contact requirement. D uses lookup for Account, so it does not guarantee Account deletion will also delete Testimonial__c record

The correct answer is B. Field-level security.

Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.

Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.

===========

The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

The correct answer is D. Rich text area.

The requirement says users need to write detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields are designed for formatted text and support images and hyperlinks.

Long text area supports longer plain text but not rich formatting with images. URL stores a single web address. Multi-select picklist stores selected values, not detailed formatted descriptions.

===========

The correct answer is B. Data is unable to be deployed with change sets.

Change sets deploy metadata/configuration, not business data. Salesforce documentation states that change sets can contain setup modifications, but they cannot be used to upload a list of records such as contacts.

So the report itself can be deployed, but the underlying records needed for the report results are not deployed through the change set. If the Partial Copy sandbox does not contain matching sample data, the report returns no data.

Why others are incorrect:

Data is not deployed just because it is added to a change set.

Reports do not have to be manually recreated if they are deployed properly.

“Salesforce OK” is not a deployment requirement.

===========

The correct answers are B. Roles and Subordinates, C. Public Groups, and D. Users / Individual Users.

Salesforce manual sharing allows record owners or users with proper access to share individual records with users, public groups, and roles. Salesforce documentation specifically states that manual sharing is used to share individual records with other users, public groups, and roles.

For Lightning manual sharing, Salesforce also describes entering groups, users, roles, or territories in the sharing search box.

So, based on your option wording:

B appears to mean Roles and Subordinates.

C is Public Groups.

D appears to mean Users / Individual Users.

A. Permission Set Groups is incorrect because permission set groups grant object, field, app, and system permissions, not case-by-case record sharing.

E. Private Groups is not the standard answer for this Platform App Builder manual-sharing question.

===========

The correct answer is B. Lookup.

This is a one-to-many mentorship relationship: one experienced Realtor can mentor many new Realtors, but each new Realtor works with only one experienced Realtor. A lookup relationship is appropriate for connecting one record to another in this type of flexible parent-child model. Salesforce relationship documentation confirms that lookup relationships are used to relate objects without the strict ownership, sharing, and deletion behavior of master-detail relationships.

Master-detail is too restrictive because the new Realtor record should not necessarily inherit ownership and deletion behavior from the mentor. Many-to-many is incorrect because each new Realtor has only one mentor. Indirect lookup is used for external objects, not this internal Salesforce relationship.

===========

The correct answer is C. A record-triggered flow can run automatically when an Opportunity is updated to Closed Won, create a renewal Opportunity, and notify the contracts team. Salesforce Trailhead explains that record-triggered flows are built around trigger, criteria, and action; for example, when an Opportunity is created or updated and meets criteria, the flow can create another record.

Salesforce Flow can also create records and send emails, which fits both requirements: create the renewal Opportunity and notify an external contracts team.

Why others are incorrect:

A Approval Process is for review/approval routing.

B Outbound Message may notify an external system, but it does not handle the full renewal Opportunity creation requirement by itself.

D Validation Rule only prevents bad data; it does not create records or send notifications.

===========

The correct answers are A. Unique and D. External ID.

The legacy ID should be marked as an External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce REST API documentation states that records can be inserted or updated using a specified external ID field.

The field should also be marked Unique so that the legacy system ID identifies one Salesforce Account record only. Salesforce documentation explains that an external ID can represent an ID from another external system, and uniqueness helps prevent duplicate matching values.

B is incorrect because encrypted text is not appropriate for a matching/upsert key.

C is incorrect because Required only forces a value; it does not make the field usable for upsert matching or prevent duplicate legacy IDs.

===========

The correct next steps are A. Add the fields to the page layout on the object and C. Create a permission set for access to the object and fields .

This is a two-part access problem in Salesforce: users need both security access and user-interface exposure . Creating a custom object and fields in Schema Builder only creates the metadata. It does not automatically guarantee that end users can see, create, edit, or use those records and fields.

C is required because object permissions define the base-level access users have to records for an object, such as create, read, edit, and delete. Salesforce also uses field permissions / field-level security to control whether users can view or edit individual fields. Permission sets are the correct modern mechanism to grant object and field permissions to selected users without changing their base profile.

A is also required because page layouts control the organization of fields on record detail and edit pages. Even if a user has field-level access, the field must be placed on the relevant page layout for normal record-page visibility and editing in the UI. Salesforce specifically separates field-level security as the access-control layer and page layouts as the UI organization layer.

B is incorrect because “Allow Reports” only makes the object available for report creation; it does not grant users object CRUD access or field-level visibility. D is incorrect because data types are assigned during field creation, not after, and choosing a data type does not grant user access.

The correct answer is A. Configure Campaign Interactions and Campaign statistics.

The option text appears to contain an OCR/wording issue. The intended Salesforce feature is Campaign Hierarchies and Campaign statistics. For advertising ROI, Salesforce Campaigns are the correct feature because Campaign ROI reports calculate return on investment using campaign cost and won opportunity value. Salesforce also states that campaign hierarchy metrics roll up from child campaigns to parent campaigns, which helps analyze campaign performance across related marketing efforts.

B is incorrect because Account interactions and roll-up summary fields are not the standard marketing ROI solution.

C is incorrect because changing the whole org to a public security model is unnecessary.

D is incorrect because an opportunity pipeline report alone does not provide campaign ROI analysis.

The correct answer is C. Apex unit test failures.

Because the unmanaged package was successfully installed in a Full Copy sandbox that matches production, issues like feature incompatibility, license mismatch, or object limits would normally have appeared during sandbox testing. The remaining Salesforce-specific production blocker is Apex test execution.

Salesforce deployment documentation states that if any Apex test fails, the deployment is rolled back. Salesforce Apex testing guidance also states that Apex unit tests must meet coverage requirements and complete successfully for deployment or packaging scenarios.

So the package failed in production because the required Apex tests did not complete successfully.

===========

The correct answers are B. External ID and C. Unique.

The legacy ID field should be marked as External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce documentation confirms that external IDs can be used to create or update records through upsert.

The field should also be marked Unique so Salesforce prevents duplicate legacy ID values. Salesforce custom field attribute documentation states that the Unique option prevents duplicate field values.

Why others are incorrect:

A is incorrect because encrypted text is not the right choice for a matching legacy ID used in upserts.

D is not the best answer because making the field required does not enable upsert matching or prevent duplicate external IDs.

===========

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.

===========

Based on the exact options provided, the correct answer is A. Create a master-detail relationship field on Open Position to Application.

The requirement says one applicant must be able to apply for multiple open positions using a single application. In Salesforce, the relationship field is created on the detail/child object. Therefore, to allow one Application__c record to relate to multiple Open_Position__c records, the master-detail field would be created on Open_Position__c and point to Application__c . Salesforce Trailhead confirms that in a master-detail relationship, the relationship field is created on the detail object.

Salesforce also uses master-detail relationships and junction objects to model many-to-many relationships.

Important note: In a fully normalized recruiting data model, a separate junction object between Application and Open Position is usually cleaner. But from the provided answer choices, A is the only option that supports one Application being connected to multiple Open Positions.

===========

Users need Read access to both master objects.

Request Inventory is a junction object with two master-detail relationships: Inventory and Order. For junction objects, access is based on the associated master records and the sharing behavior of the master-detail relationships. Salesforce documentation for object relationship considerations explains that sharing access to a junction object record is determined by access to both associated master records.

Why not the others? Sharing rules are not created directly on a master-detail detail object in the same way, because it is controlled by parent. Apex-based sharing is not needed. Read access to only the first master object is not enough because the junction record connects two master records.

===========

To display a weather map component only when a house is scheduled for a listing, the app builder should use Component Visibility in the Lightning App Builder.

Component visibility allows setting filters so components appear conditionally based on field values or other conditions.

Salesforce documentation states that conditional visibility rules control when a component is displayed dynamically on a Lightning page. (Salesforce Help)

B. Field-level security controls access to fields, not component visibility.

C. Formula field only calculates values but does not control component display directly.

D. Sharing rules control record access, not UI components.

===========

The correct answer is B. Data Import Wizard.

The list contains only approximately 800 leads, which is well within the Salesforce Data Import Wizard limit. Salesforce documentation states that Data Import Wizard can import leads and supports up to 50,000 records at a time. It is also the best standard tool here because the requirement includes preventing duplicate lead records during import.

Data Loader is better for large-volume or scheduled technical loads, but it does not provide the same simple duplicate-prevention import experience for this small daily lead list. Manual entry is inefficient, and DataLoader.io is not the standard Platform App Builder exam answer.

===========

The correct answers are A. The NOW() function in the formula field and D. A cross-object field referenced in the formula field.

Salesforce allows roll-up summary fields to summarize formula fields only when the formula does not contain unsupported dynamic or cross-object references. Salesforce documentation states that roll-up summaries can calculate formula fields only if the formula does not contain cross-object field references or functions that derive values dynamically, such as NOW() or TODAY().

A is correct because NOW() changes dynamically based on current date/time.

D is correct because cross-object field references prevent the formula from being used in the roll-up summary.

C is incorrect because CASE() itself is allowed.

B is incorrect because the issue is not simply a field update; the restriction is specifically cross-object references or dynamic formula functions inside the formula being summarized.

===========

The correct answer is C. Flow.

The requirement is to automatically delete rejected Quote records. Salesforce Flow is the correct declarative automation tool because Flow can identify records and delete them using the Delete Records element.

Why not the others:

Approval Process routes records for approval. Einstein Next Best Action recommends actions. Validation Rule prevents bad saves. None of those tools is designed to delete rejected child records automatically.

===========

The best option is a managed package from AppExchange.

Managed packages are designed for distributed apps where the provider can deliver upgrades. Salesforce documentation states that upgrades are supported for managed packages only. This reduces manual maintenance compared with unmanaged packages or custom open-source development, where updates typically require more manual replacement, deployment, or rework.

Why not the others? Unmanaged packages and open-source custom development can be useful, but they do not provide the same upgrade path and vendor-managed maintenance model as a managed AppExchange package.

===========

The correct answers are A. Create a custom-based sharing rule and B. Update the organization-wide defaults.

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

D is incorrect because owner-based sharing rules share records based on record owner, not record type.

===========

The correct answers are B. Use a roll-up summary field on the Park record and C. Use a master-detail relationship between the Park and Trail objects.

Northern Trail Outfitters wants the total number of Trails displayed on the Park record without code. In Salesforce, a standard roll-up summary field can count related child records, but it requires a master-detail relationship between the parent and child objects. Salesforce documentation confirms that roll-up summary fields calculate values from related records, and this is the correct declarative feature for this requirement.

A is incorrect because a formula field cannot count child records. D is incorrect because standard roll-up summary fields do not work on ordinary lookup relationships.

===========

The correct answers are A. Enable Feed Tracking on Opportunities and D. Use a record-triggered flow on Opportunity and a Chatter post action.

Feed Tracking is the correct configuration to track field changes on the Opportunity record feed. Salesforce states that feed tracking detects changes to tracked record fields and posts updates to the feed for users who follow the record. Salesforce also allows admins to enable feed tracking for an object and select tracked fields.

A record-triggered flow with a Chatter post action handles the automatic notification requirement. The flow can detect when the Opportunity Close Date changes and post to Chatter, such as mentioning the sales manager or a manager group. Salesforce supports posting to a record’s Chatter feed through automation when feed tracking is enabled.

B is incorrect because an outbound message sends data to an external endpoint, not a manager notification on the Opportunity. C is incorrect because Historical Trending is mainly for reporting on changes over time, not automatic manager notification on the record.

The correct answer is D. Set the Organization-Wide Default to Private for accounts. Create criteria-based sharing rules for each marketing team, and create an Inside Sales Team profile with the “View All” setting for Accounts.

The field sales team should only see Accounts they own, so Account OWD must be Private. Salesforce OWDs define users’ default access to records they do not own.

North American and European marketing teams need access by region, so use criteria-based sharing rules based on the Account region. Salesforce criteria-based sharing rules share records when records match field criteria.

Inside sales needs access to all Account records, so give that group View All Records on Account. Salesforce object permissions define that View All Records lets users view all records for that object regardless of sharing settings.

===========

A Global Picklist Value Set is used when the same picklist values must be reused across multiple objects and fields. Salesforce states that global picklist value sets let admins share values across objects and custom picklist fields.

Why not others:

A. Shared Custom Field is not a Salesforce feature for this requirement.

C. Dependent Picklist controls values based on another field.

D. Related Picklist is not the correct Salesforce feature.

===========

The correct answers are A. Set up new public Chatter groups and D. Use post action on the Account object.

Public Chatter groups support open collaboration where company users can share information in a group feed. Salesforce Chatter groups are designed for teams to share information, files, and discussions.

Post action on the Account object allows users to discuss customer accounts directly from the Account record feed. Salesforce Chatter feeds appear on record pages and allow users to follow records and see updates about them.

Why others are incorrect:

Private Chatter groups are not suitable because CK wants all company employees to see the conversations.

Chatter actions to create tasks help assign work, but they do not primarily solve open company-wide collaboration around accounts.

===========

The correct answer is A. A custom detail page link on the Contract object.

Users need access to the pricing guidelines document while viewing a Contract record. A custom detail page link can be added to an object’s page layout and used from the record detail page to open an internal document, external URL, intranet page, or other resource. Salesforce documen tation confirms that custom buttons and links can be added to object and record detail pages to give users quick access to needed resources.

Since the document is needed while viewing the Contract, the link belongs on the Contract object, not the Account object.

===========

The correct answers are B. Cross-object field updates between Training and Student records are not supported and C. On Training record, the Student Lookup field can be made optional.

This question is about creating a Student lookup field on the Training object. A lookup relationship is a looser relationship than master-detail. Salesforce documentation explains that lookup relationships do not support roll-up summary fields, unlike master-detail relationships.

Because this is a lookup relationship, the Student lookup field on Training can be optional unless the app builder marks it required. Cross-object field updates are also not supported in this lookup relationship scenario; Salesforce documents that cross-object field updates work for master-detail relationship scenarios, not normal lookup relationships.

A is incorrect because roll-up summary fields require a master-detail relationship.

D is incorrect because deleting Student records is controlled by object permissions and relationship delete behavior, not simply by access from the Training record.

===========

The correct answers are C. Unique and D. External ID.

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

The correct answer is A because the requirement is to keep one specific field, the Comment field, private from users outside HR. Salesforce field-level security is the correct security layer for controlling whether users can view or edit a field. Salesforce documentation states that field-level security restricts user access to fields and overrides page-layout visibility.

A page layout alone is not enough because page layouts control UI presentation, not full field security. Salesforce also notes that to ensure users cannot access a field, field permissions should be used because other settings do not provide the same field-level protection.

Why others are incorrect:

B and D are wrong because sharing rules and Apex sharing control record access, not individual field access.

C is wrong because removing a field from a page layout only hides it from that layout; it does not securely prevent access through reports, API, related lists, or other interfaces.

===========

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

The correct answer is D. Sum.

Cloud Kicks wants the total value of all won Opportunities displayed on the Account record. In a roll-up summary field, SUM totals the values in a selected numeric/currency field, such as Opportunity Amount. Salesforce documentation identifies SUM as the roll-up summary type used to total values in the selected field.

The app builder would create a roll-up summary field on Account, summarize Opportunities, use SUM on the Amount field, and apply filter criteria for won Opportunities, such as Stage equals Closed Won.

A. Count would only count the number of Opportunities.

B. Total is not the Salesforce roll-up summary type name.

C. Aggregate is not the specific roll-up summary option used here.

===========

Use a Record-Triggered Flow optimized for Actions and Related Records.

Submitting a record for approval is an action in Flow. Salesforce provides a Submit for Approval action, and after-save record-triggered flows are used when the automation needs to perform actions or work with related records after Salesforce saves the triggering record.

Option A is wrong because Fast Field Updates is the before-save path, mainly for updating fields on the triggering record. It is not the right optimization for submitting an approval request. Option B still requires a custom button and manual user action. Option C is unrelated because this requirement is based on an Opportunity record change, not a platform event.

===========

The correct answer is B. Queue.

The approval request must go to department members who can approve overnight shipments. In Salesforce approval processes, routing an approval to a queue is appropriate when a group of users can own or act on the approval request and any one of the queue members can handle it. Salesforce approval documentation describes approval processes as automation that specifies each approval step, including who receives the approval request.

A queue is better than a role or hierarchy field when the request needs to be handled by a department group rather than a single manager or a specific user from a hierarchy field.

A. Role is less appropriate because roles are for hierarchy-based access and routing.

C. Hierarchy field is used when routing to a user identified through a manager-style field.

D. Public group is used for sharing and grouping users, but approval queues are the standard routing choice for a group of approvers in this scenario.

===========

The correct answer is C. A Galaxy__c with Star__c report type will be automatically created.

When a master-detail relationship is created between a parent custom object and a child custom object, Salesforce can automatically generate a standard report type for the parent object with the child object, such as Galaxy__c with Star__c, assuming reporting is enabled for the objects. Salesforce documentation confirms that standard report types are created in certain object relationship scenarios, including lookup and master-detail relationships.

Why the other options are incorrect:

A is incorrect because the report type is based on the parent with child, not the child object with the parent merely as a field.

B is incorrect because a custom report type is not required for this basic master-detail reporting scenario.

D is incorrect because the report type is not created as Star__c with lookup fields from Galaxy__c.

===========

The correct sandbox type is Partial Copy.

A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.

Why the other options are wrong:

Developer and Developer Pro sandboxes are mainly for development and do not copy a produc tion data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

===========

The correct answers are A. Recent items, B. Filter list/List View, and C. Rich text.

Lightning App Builder includes standard components built by Salesforce. Salesforce documentation identifies standard Lightning page components and references components such as Recent Items, Rich Text, and List View for Lightning App Builder pages.

D. Report details is incorrect because the standard component is Report Chart, not Report Details. E. Plain text is incorrect because the standard component is Rich Text, not plain text.

===========

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

Customers and dealers are both separate business entities, and separate bills are sent to each. In Salesforce, business entities are best represented as Accounts, while the single individual at each business should be stored as a Contact under the correct Account. Salesforce account hierarchy is used to show parent-child relationships between related accounts.

Why not D? Account Teams represent internal Salesforce users working on an account, not external customer/dealer representation.

Existing data will be truncated to the first 255 characters.

Salesforce documentation on changing custom field types states that when a Long Text Area field is converted to Email, Phone, Text, Text Area, or URL, the record data is truncated to the first 255 characters. Since the target is a standard Text Area with a 255-character limit, longer Manager Notes values would not remain intact.

Why not the others? Salesforce does not preserve values beyond the new limit in this conversion. The data is not completely lost, but anything after the first 255 characters is removed.

The correct answer is A. Add the field to the custom report type field layout.

The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce’s documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.

B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.

C is incorrect because the report type already exists and is being used.

D is incorrect because the field data type was already assigned when the field was created.

===========

The correct answers are A. Tabular format and B. Summary format.

Salesforce reporting snapshots can use custom tabular or summary reports as the source report. Salesforce documentation specifically states that a reporting snapshot source report can be tabular or summary.

Why others are incorrect:

C. Joined format is not supported as a reporting snapshot source report.

D. Matrix format is not supported because matrix reports group by rows and columns, and Salesforce troubleshooting guidance states that matrix reports can’t be used with reporting snapshots.

===========

The correct answer is A. Web-to-Case is the Salesforce feature designed to let visitors submit case information from a public-facing website. Salesforce documentation states that Web-to-Case is set up by enabling the feature, creating and customizing a web form, and adding that form to a website.

Why others are incorrect:

B. Outbound message sends data out of Salesforce; it does not create cases from a website.

C. Screen flow could require extra site/guest-user setup and is not the standard feature for this requirement.

D. Email-to-case creates cases from inbound email, not directly from a public web form.

The correct answer is D. Flow.

The requirement is to automatically clear the Phone field on Contact when the Do Not Call checkbox is checked. A record-triggered Flow can run when a Contact is created or updated, check whether Do_Not_Call is true, and then update the triggering Contact record by setting the Phone field to blank. Salesforce Flow supports updating records, including directly updating the record that triggered the flow.

B. Validation rule is incorrect because it can block a save but cannot delete or clear the Phone field automatically.

C. Quick action is manual, not automatic.

A. If-then rule is not the best current Salesforce automation tool for this requirement.

===========

The correct answers are B. Assign the page to a combination of apps and profiles, C. Make the page the default homepage for specific apps, and E. Make the page the org default.

When activating Lightning pages, Salesforce supports assigning a page as an org default, assigning it to specific Lightning apps, and assigning it to combinations such as app and profile. Salesforce Trailhead also confirms that Lightning record page activation supports org default, app default, and app/record type/profile assignments.

A is incorrect because Lightning page activation uses profiles, not permission sets, for this assignment model.

D is incorrect because Lightning pages are not activated by role as a standard activation option.

===========

The correct answer is D. Custom Report Type.

A custom report type defines which records and fields are available in a report based on relationships between a primary object and related objects. Salesforce also references custom WITH or WITHOUT report types for reporting on related records.

Because DreamHouse Realty needs “with” or “without” reports involving a custom object and related lookup data, the app builder must create a Custom Report Type and define the object relationships.

Why others are incorrect:

A. Report Filters filter report results but do not define the reportable object relationship.

B. Row-Level Formula calculates values per row; it does not create with/without relationship reporting.

C. Report Bucket Field groups report values; it does not define related-object report structure.

===========

The correct answer is A. Flow.

The requirement is to automatically update a field on the Asset record when a related maintenance Work Order is closed. This is a record-change automation requirement. A record-triggered Flow can run when a Work Order is updated, check whether it is a maintenance work order and closed, and then update the related Asset’s last maintenance date.

Salesforce Flow supports updating related records through the Update Records element in record-triggered flows.

C. Roll-up Summary is not the best answer because Salesforce roll-up summary fields require a master-detail relationship, and the Work Order’s Asset field is a lookup relationship to Asset.

B is incorrect because Einstein Next Best Action recommends actions; it does not maintain roll-up style data.

D is incorrect because Apex Trigger is unnecessary when Flow can meet the requirement declaratively.

===========

The correct answer is D. The Owner field on the Master record.

In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn’t available and is automatically set to the owner of the related master record.

Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.

A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

===========

The correct answer is D. Create a new text field and import the formula field values in it.

The existing Specialty__c field is a formula field, so users cannot manually edit it. Formula fields calculate their value automatically from other fields. Since Cloud Kicks now wants Opportunity Specialty__c values to be different from the related Account value, the app builder should create a new editable field, such as a Text field, and then load the existing calculated formula values into that new field for existing Opportunity records.

This preserves historical Opportunity values while allowing sales reps to enter or update Specialty values going forward. Salesforce documentation explains that roll-up/formula-style calculated values are system-derived, while changing custom field types has limitations and requires care when data must be preserved.

A and B are incorrect because a formula field cannot simply become an editable text field while safely preserving all existing calculated values.

C is incomplete because creating a new text field without importing the existing formula values does not preserve the current values on existing Opportunities.

===========

The correct answer is D. Patch.

In application lifecycle management, patch releases are used for bug fixes and simple, low-impact changes. Salesforce packaging documentation also describes patch versions as minor upgrades used for fixing bugs or errors.

Major releases are for large changes or significant new functionality. Minor releases are usually for limited-impact enhancements. Roll is not the correct ALM release category here.

===========

This question is testing the classic Salesforce Process Builder automation best practice , not a generic Flow-only rule. Salesforce’s official process design guidance states that an org should have only one record-change process per object . The reason is simple: every time a record is created or updated, Salesforce evaluates the record-change processes for that object. If an object has multiple record-change processes, the automation becomes harder to predict, harder to troubleshoot, and more likely to hit governor limits. Salesforce specifically explains that consolidating automation into one record-change process gives admins a single view of all criteria and actions for that object, reduces duplicated automation overhead, and allows the app builder to control the order of criteria evaluation.

A is not the best exam answer here. In modern Flow architecture, “one Flow per object” is often discussed as a design pattern, but it is not the exact best-practice wording being tested by this Platform App Builder-style question. Salesforce Flow design is more nuanced today because record-triggered flows can vary by trigger timing and event. B is wrong because validation rules should be separated by validation requirement, not forced into one rule per object. C is wrong because invocable processes are reusable modular processes, not the main record-change automation container.

The correct answer is A. Path.

Salesforce Path is designed to guide users through different stages of a business process. It can show key fields and provide Guidance for Success at each step, which matches the manager’s requirement to give new sales reps help during different sales processes.

B. Chatter Publisher is for collaboration posts, not guided sales-process help.

C. Journey Builder is a Marketing Cloud tool, not the standard Sales Cloud guidance feature.

D. Flow can automate steps, but Path is the best UI guidance tool for this requirement.

===========

The correct answer is B. User will be presented with a “Record Lock” notification.

When a record is submitted for approval, Salesforce locks the record to prevent users from editing it during the approval process. Salesforce documentation states that records submitted for approval are locked, and by default only admins can edit locked records unless editability settings allow otherwise.

The employee submitted the Opportunity for approval, so the employee cannot simply edit the Description field after submission. The expected user experience is a locked-record message.

===========

The correct answers are A. Build an approval process that requires unanimous approval from the manager and VP of Sales and D. Create a flow that submits the record for an approval process.

The requirement is not just to notify users or block the change. The manager and VP of Sales must review the close-date delay. Salesforce approval processes are designed to automate how records are approved, including approval steps, approvers, and approval/rejection actions.

A is correct because an approval process can route the Opportunity to the manager and VP of Sales for approval. Requiring unanimous approval ensures both reviewers must approve the delayed close date.

D is correct because a record-triggered flow can detect when the Opportunity Close Date changes and is delayed by more than 60 days, then use the Submit for Approval action. Salesforce Flow supports prior-value/change logic in record-triggered flows, and Salesforce documents the Flow Submit for Approval action.

Why others are incorrect:

B is incorrect because a validation rule blocks saving the record. It does not allow manager/VP review.

C is incorrect because a formula field and email alert do not create an approval review process, and the stated logic does not satisfy the approval requirement.

===========

The correct answers are A. Navigation Menu and C. In-App Notification.

Salesforce documentation states that users can receive and act on approval requests in the Salesforce mobile app by tapping the notification or by going to Approval Requests in the navigation menu. Salesforce also describes the Approval Requests navigation item as showing pending approvals where users can approve or reject items from within Salesforce.

Why others are incorrect:

B. Home Screen is not the documented approval-response delivery method in this context.

D. Record Detail is not the best answer here because the documented mobile approval response paths are the notification and the Approval Requests navigation item.

===========

The correct answer is B. Create a unique External ID field and use Data Loader.

Cloud Kicks is receiving shipment data from an external shipping system on a regular basis. To prevent duplicate Delivery records and update the correct existing records, the app builder should create a field such as Tracking Number on Delivery__c , mark it as External ID and Unique, then use Data Loader Upsert.

Salesforce documentation states that external IDs can be used when importing custom objects to prevent duplicate records. Salesforce Data Loader documentation also states that upsert combines insert and update: if a matching record exists, it updates it; otherwise, it creates a new record.

A is less appropriate because this is a recurring system migration/update scenario, and Data Loader with External ID is the stronger tool.

C is incomplete because matching only on Salesforce ID requires the external system to already store Salesforce record IDs.

D may help detect duplicates, but duplicate/matching rules do not provide the clean upsert mechanism needed to update the correct existing record.

===========

The correct answer is D. Record-triggered flow.

The requirement is automatic: when an Account Type changes to Past-Customer, all directly related Contacts must have their Status updated to Re-Market. A record-triggered flow is the correct declarative automation because it can run when an Account record is updated and then update related Contact records. Salesforce describes record-triggered flows as automation that runs automatically when records are created, updated, or deleted. Salesforce also documents that Flow can update records related to the record that triggered the flow.

Validation rules only prevent invalid saves. Lightning components are UI elements. Screen flows require user interaction, while this requirement needs background automation.

===========

The correct answer is A.

When custom tabs are deployed through change sets without profile settings or permission sets, the deployed custom tabs are hidden by default for all users. Salesforce Help states that deployed custom tabs are hidden by default unless the change set also includes profiles that set the tab visibility.

Tab visibility is controlled through profile or permission set tab settings such as Default On, Default Off, and Tab Hidden.

Why others are incorrect:

B and C are incorrect because the tabs are not automatically default off or default on for all users.

D is incorrect because the custom tabs are deployed; they are just not visible until access is configured.

===========

The correct answer is C. Data Export Service.

Salesforce Data Export Service is the native tool used to export backup data from a Salesforce org. It allows admins to create export files of Salesforce data and schedule exports. Salesforce documentation describes Data Export as the feature for exporting backup data from Salesforce.

Important exam note: the question says “daily backup,” but standard Salesforce Data Export scheduling is commonly weekly or monthly depending on edition and settings. Among the listed options, Data Export Service is still the correct Platform App Builder answer.

A is incorrect because refreshing a Full Copy sandbox is not a backup strategy.

B is incorrect because packages move metadata, not org data backup.

D is incorrect because “Support expert” is not the Salesforce backup/export tool.

===========

The correct answer is C. Custom object with Master-detail field to Opportunity.

AW Computing needs many help requests related to one Opportunity, so the help request should be a custom child object under Opportunity. Because the Opportunity page must show the most recent request date, the app builder needs a Roll-Up Summary field on Opportunity using MAX on the request date field.

Salesforce roll-up summary fields work on the master side of a master-detail relationship, and MAX can be used for date/date-time fields.

A is backward because the master-detail field belongs on the child object, not Opportunity.

B and D use lookup relationships, which do not support standard roll-up summary fields.

===========

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.

The correct answer is C. Configure Campaign Hierarchies and Campaign statistics.

To understand return on investment for an advertising buy, Universal Containers should use Salesforce Campaigns, especially Campaign Hierarchies and campaign reporting/statistics. Salesforce campaign hierarchy documentation explains that child campaign metrics roll up to the parent campaign, and Salesforce campaign reports can include campaign-hierarchy statistics for aggregate values.

The private security model does not require changing the whole org to public. The business need is marketing ROI tracking, so Campaigns are the correct feature.

A is incorrect because an opportunity pipeline report does not directly track advertising campaign ROI.

B is incorrect because Account Hierarchies and roll-up summaries are not the standard solution for campaign ROI.

D is incorrect because changing to a public security model is unnecessary and weakens data security.

===========

The correct answer is C. Create a validation rule that uses the PRIORVALUE function.

The requirement is: once Estimated Hours is set, users can decrease the value but cannot increase it. A validation rule can compare the new value with the old value by using PRIORVALUE() .

Example logic:

Estimated_Hours__c > PRIORVALUE(Estimated_Hours__c)

Salesforce documents PRIORVALUE() as the function used to return the previous value of a field, and Salesforce examples use it in validation rules to compare a changed value against the prior value.

A is incomplete because ISCHANGED() only detects that the field changed; it does not determine whether the value increased or decreased.

B is incorrect because a default value does not control later edits.

D is incorrect because PREVGROUPVAL() is used in reports, not validation rules.

===========

The correct answer is B. Master-detail relationship.

Cloud Kicks needs two things: count Gift Card records on the Account and prevent Gift Cards from being moved to another Account after creation. A master-detail relationship supports both requirements.

First, master-detail enables a roll-up summary field on Account to count related Gift Card records. Salesforce documentation confirms that roll-up summaries work from detail records up to the master record.

Second, master-detail relationships prevent reparenting by default. Salesforce documentation states that records cannot be reparented in master-detail relationships by default, although admins can allow reparenting if they choose.

A is incorrect because a lookup relationship does not support standard roll-up summary fields and does not permanently lock the parent Account by default.

C is incorrect because roll-up summary is a field on the parent Account, not the relationship field type on Gift Card.

D is incorrect because a formula cannot count related child records or enforce parent locking.

The correct answer is D. Flow.

A call center representative needs to collect customer information through a series of question prompts. This is a classic use case for a Screen Flow. Salesforce describes screen flows as interactive automation that asks users questions, presents information, and uses user responses to update records or show more prompts.

Approval Process is for approvals, Path guides users through stages, and Validation Rule enforces data quality. None of those tools provide a guided question-and-answer experience.

===========

The correct answers are A. Detail page layout, B. Custom actions, and D. Custom fields.

To deploy a new Account detail page layout successfully and make it look the same in production, the change set must include the actual page layout plus the components used on that layout.

Salesforce page layouts control the arrangement of fields, actions, buttons, and related lists on record detail pages. Therefore, if the layout uses new custom fields or custom actions, those components must also exist in production or be included in the change set. Salesforce change set guidance also notes that custom fields must be added individually when deploying customizations.

C. System administrator profile is not required just to deploy the visual layout. Profiles are only relevant if deploying access settings or layout assignments.

E. Lightning App Builder is not the component needed for a standard detail page layout; a Lightning Record Page would be a different metadata component.

===========

The correct answers are A. Streams and D. Out of Office.

Streams allow users to combine multiple Chatter feeds into one custom feed, making it easier to monitor updates from important people, records, and groups. This directly solves the issue of gathering feed updates from core team members. Salesforce documentation describes Chatter streams as custom feeds created by combining multiple related feeds into one feed.

Out of Office helps team members understand who is available to respond. Salesforce documentation explains that users can schedule and customize an out-of-office message and display it next to their name in Chatter.

Why the other options are incorrect:

Topics help categorize Chatter content but do not directly gather core-team feeds or show availability.

Polls are useful for collecting opinions, but they do not solve feed monitoring or availability visibility.

===========

The correct answer is C. Two Master-detail relationships on a new custom object.

This is a many-to-many relationship: one Contact can be related to many Solar Projects, and one Solar Project can be related to many Contacts. Salesforce’s standard declarative design for many-to-many relationships is a junction object. A junction object is a custom object with two master-detail relationships connecting the two related objects.

A is incorrect because the two master-detail relationships belong on the new junction object, not directly on Contact and Solar Project.

B can technically relate records, but it is not the standard Salesforce many-to-many model tested here.

D does not correctly create a scalable many-to-many model.

===========

The correct answer is B. Approval Process.

An Approval Process is used when a record must be reviewed and approved before moving forward. Salesforce Trailhead gives a very similar example: opportunities with high discounts requiring approval before proceeding.

Here, Cloud Kicks needs CFO sign-off when a major shoe retail deal has a discount greater than 30% before it can be closed. This is exactly what an approval process is designed to handle.

Why others are incorrect:

Slack message only sends communication.

Email alert only notifies someone.

Field update changes a field value but does not collect formal approval.

===========

The correct answer is B. Verify there is an Apex test that provides test coverage for the flow.

For deploying an active autolaunched flow to production, Salesforce requires flow test coverage. Salesforce documentation states that before deploying a process or autolaunched flow as active, the org must meet flow test coverage requirements, and Apex tests must cover active processes and active autolaunched flows.

A is not the main deployment consideration for making the flow active in production.

C is incorrect because Salesforce does not require 100% flow test coverage.

D is incorrect for this scenario because the requirement is to deploy it already active, not manually activate it after deployment.

===========

The correct answer is D. Unable to reference the child records.

Formula fields can reference fields from related parent records using cross-object formulas, but they cannot directly pull values from multiple child records onto a parent record. Salesforce describes cross-object formulas as formulas that can reference fields from a parent object when the formula is created on the child/detail side of the relationship.

In this case, Account is the parent and Contacts are child records. Since the formula is being created on Account and trying to reference related Contacts, the relationship does not appear in the formula editor.

Correct design alternatives: use a roll-up summary where supported, Flow, Apex, or reporting.

===========

The correct answer is C.

A Partial Copy sandbox uses a sandbox template to determine which objects and data are copied from production. Salesforce states that sandbox templates let admins select specific objects and data to copy to a Full or Partial Copy sandbox. If the custom object Shipping was not included in the sandbox template, its production records would not be copied into the refreshed partial sandbox.

Why others are incorrect:

A is not the likely issue; refresh timing does not explain one object having no data.

B is less likely as the scenario points to template selection.

D is not the best answer because capacity may limit copied data, but missing all data for a specific object usually indicates the object was not selected in the sandbox template.

===========

The correct answer is B. Clone the change set and re-deploy.

After a change set has been uploaded, Salesforce does not allow its contents to be changed. Salesforce documentation states that after upload, the change set contents cannot be changed; to redeploy the same set of components, the app builder should clone the change set, and the cloned change set includes the latest changes to its components from the source org.

A is incorrect because renaming does not update uploaded components. C is unnecessary. D is incorrect because an uploaded change set cannot simply be updated and redeployed.

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========