Free Practice Questions for the Salesforce App Builder Platform-App-Builder Exam (2026 Updated)

The correct answers are C. Custom object, D. Apex class, and E. Custom field.

Change sets are used to move metadata between related Salesforce environments, such as sandbox and production. Salesforce documentation confirms that change sets can migrate components such as custom objects, custom fields, and Apex classes. Salesforce also notes that custom fields can be migrated individually in a change set.

A. Web-to-lead is not one of the common metadata components normally selected as an item in this exam context. B. Standard fields are standard Salesforce metadata and are not moved like custom fields in change sets.

===========

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.

===========

For an unmanaged package, Salesforce documentation states that the developer who created and uploaded the package has no control over installed components and can’t change or upgrade them after installation.

Therefore, an unmanaged package does not follow the normal managed-package upgrade path. To get a newer version, the practical process is to remove the installed unmanaged package and install the newer version.

Why others are incorrect:

B and D describe managed/update-style behavior, not unmanaged package behavior.

C is not the package upgrade process itself; it describes a deployment workaround, not upgrading the installed unmanaged package.

===========

The correct answer is C. Record-triggered flow.

To track the number of times a Case is reopened, the app builder can create a record-triggered flow on the Case object that runs when the Case is updated. The flow can check when the Status changes from Closed to an open/reopened status and increment a custom number field such as Number_of_Reopens__c . Salesforce Trailhead explains that record-triggered flows run when records are created, updated, created or updated, or deleted.

Why not Apex Trigger? Apex could work, but the Platform App Builder best answer is the declarative option: Flow before code.

A custom field type change can substantially increase change-set deployment time because Salesforce may need to transform existing stored data to conform to the new field representation. Salesforce ' s official Change Sets Best Practices documentation specifically warns administrators to consider possible deployment delays when a change set includes custom field type changes. The documentation explains that these changes can require modifications across a large number of existing records and therefore can extend deployment for a significant period. Salesforce even recommends considering a manual field-type modification after deployment when avoiding the delay is important. Profiles may increase deployment complexity because they contain access metadata, but they are not the specific documented cause identified here. Dependent fields and roles likewise do not inherently produce the extended data-conversion processing associated with changing a field ' s underlying data type.

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

The correct answer is C. Use Dynamic Forms to display the Years of Previous Experience field if Previous Experience is checked.

This is a conditional field-visibility requirement. Salesforce Dynamic Forms lets app builders manage fields and sections directly in Lightning App Builder and use visibility rules to show users only the fields they need, when they need them.

So the app builder can place the Years of Previous Experience field on the Dynamic Forms-enabled record page and set visibility so it displays only when Previous Experience = True.

A is unnecessary and overcomplicated.

B is incorrect because field dependencies apply to picklists, not checkbox-to-number visibility.

D is incorrect because Visualforce is unnecessary when Dynamic Forms provides a declarative solution.

===========

Current Salesforce functionality makes D. Dynamic Forms the appropriate declarative answer. Lightning App Builder supports visibility rules on Dynamic Forms Field and Field Section components, and Salesforce specifically documents device-based visibility through the Device context. An app builder can therefore configure a section to appear for the required form factor, such as phone or desktop, without developing a custom Lightning Web Component. Record Types determine business processes, picklist availability, and layout assignments; they are not device-detection mechanisms. Traditional Page Layouts likewise do not provide device-specific section visibility. A custom LWC could implement custom form-factor behavior programmatically, but it is unnecessary when Dynamic Forms provides native declarative visibility controls.

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

The correct answer is A. Make the Opportunity Type a required field on the initial Opportunity page layout and use automation to update the record type based on the Opportunity Type.

The requirement has two phases: first, show users only the fields needed to create the Opportunity; after save, show the full record page based on the Opportunity type. This can be handled by using a required Opportunity Type field first, then automation can update the Opportunity record type. Salesforce page layouts can be assigned by profile and record type, which allows different Opportunity types to show different layouts after the record type is set.

B is incomplete because it only mentions page layouts based on profile, not dynamically changing the layout based on Opportunity Type after creation. C is incorrect because sharing rules control record access, not field display. D relies on users manually expanding sections and does not meet the streamlined requirement.

Salesforce requires installation records to be directly associated with Opportunities, and sales reps need visibility of all installations tied to their Opportunities. A Master-Detail relationship is the correct solution because:

The Installation object (detail) inherits sharing and security from the Opportunity (master), ensuring sales reps see only their related installations.

Enables roll-up summaries on Opportunity if needed.

Salesforce documentation confirms that Master-Detail relationships provide parent-controlled ownership and access, making them ideal for enforcing related record visibility. (Salesforce Help)

B. Hierarchical is only available for User object.

C. Many-to-Many requires a junction object; not needed here.

D. Lookup allows optional, independent access; would not automatically enforce visibility.

===========

The correct answer is D. Approval process.

The marketing director wants all free parts to receive sign-off before they are allowed. Salesforce Approval Processes are used to automate how records are approved, define who approves at each step, and specify actions after approval or rejection. Trailhead describes approval processes as automation for record approval and explains that approval steps assign approval requests to specific users.

Chatter approval is not the standard feature for formal record sign-off. Slack post and automated email message can notify people, but they do not enforce approval. An Approval Process is the correct declarative feature for required business sign-off.

===========

The correct answer is D. Choose an unmanaged package from AppExchange that closely meets the requirements of the project and allows programmatic development.

The requirement has two key parts: the app builder has very little time, and the solution must be fully customizable. Salesforce documentation describes unmanaged packages as suitable for one-time drops of applications that require customization after installation. That fits this scenario better than building everything from scratch.

C is incorrect because managed packages are better for distributed, upgradeable AppExchange apps, but they can restrict subscriber changes to packaged components. The question specifically says the solution still needs full customization, which points to an unmanaged package.

Lightning Object Creator, represented in current Salesforce Setup as creating a custom object from a spreadsheet, is specifically designed for this scenario. Salesforce states that administrators can upload an XLSX, CSV, or Google Sheet and use the wizard to create a custom object, derive its fields from the spreadsheet columns, and populate the new object ' s records as part of the same process. This directly meets all three requirements: create the object, create the fields, and load the spreadsheet data. Schema Builder can create objects and fields but does not simultaneously import the spreadsheet ' s record data. Data Loader imports large volumes into existing objects but does not automatically construct an object and its schema. Data Import Wizard similarly assumes supported target objects already exist.

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

Limitations when changing custom field data types include:

A. It is not possible to change the data type of a formula field – formula fields cannot be converted to other field types because they are calculated dynamically.

D. It is not possible to change a Text Area (Long) field to Text – Salesforce prevents reducing the field length because data loss could occur.

Salesforce documentation highlights these restrictions: (Salesforce Help)

B is partially true; changing fields referenced in Apex requires careful handling, but Apex references can sometimes be updated automatically.

C is allowed with some limitations if the External ID type is compatible.

===========

A permission set is the appropriate way to selectively grant the Salary record type to the hiring manager and VP of HR while other HR users retain ordinary access to applicant records. Salesforce explicitly supports assigning custom record types through permission sets. The base profile can provide the common Applicant object permissions and Hourly record type, while the additional permission set expands Salary record-type availability only for authorized users. This separates record creation capability from record-level visibility. Changing organization-wide defaults would unnecessarily affect who can view applicant records and does not control record-type selection. Simply making Hourly the default also does not prevent users from choosing another record type if they have access to it. Object-level Create permission cannot distinguish between two record types of the same object. Therefore, D provides the required granular access.

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

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 answer is B. Validation Rule.

DreamHouse Realty wants to prevent an Opportunity from entering the Qualified stage unless Expected_Close_Date__c is populated. A validation rule is the correct tool because Salesforce validation rules check whether record data meets specified criteria before the user can save the record.

A validation rule could check:

Stage = Qualified

AND

Expected_Close_Date__c is blank

If both are true, Salesforce blocks the save and displays an error message.

A. Page Layout can make a field visible or required on a layout, but it cannot conditionally require the field only when Stage equals Qualified.

C. Activity History is unrelated.

D. Record Type controls business processes and layouts but does not enforce this condition by itself.

===========

A Flow Approval Process provides Salesforce ' s declarative framework for structured approval routing. It uses stages and approval steps, can assign approval work to specific users, groups, or queues, tracks approval state, and supports conditional execution. Salesforce states that stages execute sequentially and that individual approval steps can also be configured to start after another step is completed. Universal Containers can therefore configure the manager approval first and use conditions so the CFO step is required only when the expense exceeds $5,000. Associated background steps or flows can update the Expense Report Status when approval completes. A regular record-triggered flow does not by itself provide the complete approval work-item lifecycle, while validation rules and screen flows are not substitutes for managed asynchronous approvals. Salesforce

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

The correct answers are A. Flow Launcher and D. Quick Action.

A flow can be exposed to users through a page-based launcher/component. Salesforce Trailhead explains that users can access a flow by adding it to a Lightning page through Lightning App Builder. The Flow component can be dragged onto the Lightning page so users can run the flow from that page.

A Quick Action can also launch a flow. Salesforce documentation states that quick actions help users launch and navigate through workflows, and Trailhead confirms that custom actions can invoke flows.

Why others are incorrect:

B. Apex can invoke automation programmatically, but it is not the best user-facing access feature in this question.

C. Approval Process routes records for approval; it is not a general method for users to access flows.

===========

The correct answer is C. Formula Field.

The Service Manager wants a visual color indicator based on the age of an open Case: green for new, yellow for one day old, and red for three days old. This can be implemented with a formula field using conditional logic and the Salesforce IMAGE() function to display different colored indicators based on Case age. Salesforce documentation confirms that the IMAGE function is available in formula fields and can display an image based on field values.

A formula field can evaluate the case age using fields such as CreatedDate , TODAY() , and IsClosed , then return the correct colored image.

A. Custom Button is incorrect because this is not a user action.

B. Quick Action is incorrect because the requirement is display-based, not action-based.

D. Lightning Web Component could do this with code, but a formula field is the simplest declarative Platform App Builder solution.

===========

With Account organization-wide defaults set to Private, users cannot automatically see records owned by peers at the same role-hierarchy level. Salesforce sharing rules provide an exception to restrictive organization-wide defaults and can grant additional record access to selected users, roles, or public groups. If User A belongs to a public group targeted by an Account sharing rule, User A can receive access to User C ' s Account while User B does not. Being at the same role level as User C does not provide upward hierarchy access. “View All Fields” concerns field visibility and does not grant access to otherwise inaccessible records. Login access policies concern when or where users can authenticate, not access to one particular Account. Therefore, membership in a public group used by a sharing rule explains the different record visibility.

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

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.

===========

Dynamic Forms Field and Field Section components historically required special mobile handling. Salesforce now provides the Dynamic Forms and Dynamic Highlights Panel on Mobile setting in Salesforce Mobile App Setup so mobile users can receive the Dynamic Forms experience used on desktop record pages. Salesforce specifically states that when users cannot receive Dynamic Forms Field and Field Section behavior on mobile, administrators should enable this setting from Setup → Salesforce Mobile App. Adding more Field Sections does not solve the underlying mobile-support setting. Visibility rules control when already-supported components appear, but they do not substitute for enabling Dynamic Forms on Mobile. Reverting mobile users to traditional page layouts is also unnecessary when Salesforce provides native Dynamic Forms mobile support. Therefore, C addresses the underlying configuration issue directly. Salesforce

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

A Screen Flow is specifically designed for interactive processes that display information, ask users questions, and capture user input across one or more screens. Salesforce states that Screen elements can collect text, choices, dates, lookup values, and other inputs, and multiple Screen elements can create a guided multi-page experience. Screen flows can also be embedded directly on Lightning record pages, which precisely matches the requirement to guide customer care agents from the Case page. A record-triggered flow runs automatically when record data changes and does not provide an interactive wizard. An autolaunched flow normally runs without screens, while a schedule-triggered flow executes at defined times for batches of records. Because agents must actively provide information at several stages of the return process, Screen Flow is the correct declarative solution.

The correct answers are C. The report is in the manager’s Private reports folder and D. The report does not have a chart.

The Report Chart component is used to display a chart from a report on a Lightning page. If the report has no chart, it cannot be used as a Report Chart component source. Salesforce documentation describes the Report Chart component as a way to include a chart from a report in a Lightning page.

The app builder also must have access to the report through report folder sharing. Reports saved in a user’s private report folder are not visible to other users unless moved/shared appropriately. Salesforce explains that reports are saved by default into private reports or dashboards folders unless a public/custom folder is selected.

A is incorrect because a report having no returned data does not stop the report from being selectable. B is incorrect because the app builder does not need to be the report creator; they need access to the report folder and the report must contain a chart.

===========

The correct answer is B. Create a new roll-up summary field called First Order Date, using type MIN on the Opportunity Close Date with a filter where IsWon = TRUE.

Cloud Kicks wants to track the first purchase date for each customer. The first purchase is the earliest won Opportunity Close Date. A roll-up summary field can calculate values from related records and supports summary types such as COUNT, SUM, MIN, and MAX. Salesforce Trailhead states that MIN displays the lowest value from the selected field and supports date/date-time fields.

So the app builder should create a roll-up summary field on the Account, summarize related Opportunities, choose MIN on CloseDate , and filter to only include won Opportunities, such as IsWon = TRUE .

A and C are incorrect because the field should be a roll-up summary field itself, not a regular date field updated by a roll-up.

D is incorrect because SUM is for number, currency, and percent fields, not date fields. Salesforce documentation confirms that MIN/MAX support date fields, while SUM is for numeric-style fields.

===========

The Automation Lightning App ' s Monitor tab is Salesforce ' s centralized interface for examining failed and paused flow interviews. Salesforce states that the Monitor tab displays failed interviews, their error information, and details needed to determine why execution failed. From the failed interview details, an administrator can open the run in debug mode and inspect the execution information without requiring the user to reproduce the issue. This directly satisfies the requirement to troubleshoot intermittent production failures from historical flow runs. Option A focuses primarily on paused interviews and is not the current comprehensive monitoring experience. Apex Replay Debugger is intended for Apex debugging rather than declarative Flow execution. Running the flow manually as another user creates a new test execution rather than analyzing the specific production failures that already occurred.

The correct answers are A. Task, B. Email Alert, and D. Outbound Message.

In a Salesforce approval process, automated actions can be configured when a record is submitted, approved, rejected, or recalled. Salesforce approval process setup supports workflow action types such as tasks, email alerts, field updates, and outbound messages.

C. Invocable Flow is not one of the classic approval-process action types in this exam context. E. Decision Element is a Flow element, not an approval-process action.

===========

When deploying from sandbox to production using Change Sets, the following are critical considerations:

A. Transactions will revert if the deployment errors – Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.

D. Change sets do not include all components and may require manual configuration – Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.

Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)

B. Users being logged out is not required; deployments can occur while users are logged in.

C. Salesforce Connect does not automatically link environments; it is unrelated to change sets.

===========

The correct answer is B. Flow.

The requirement is to show the number of open Cases for both the Account and the Parent Account. This is not a simple native roll-up summary scenario because standard roll-up summary fields are mainly for master-detail relationships, while lookup relationships do not support standard roll-up summary fields.

Salesforce specifically documents Flow examples where a flow looks up the parent account, checks how many open cases it has, and evaluates that count. Salesforce also has guidance for creating roll-up-style summaries using Flow, including a use case to count Cases related to an Account.

Why others are incorrect:

A. Approval Process is for approvals, not counting open Cases.

C. Custom object is unnecessary.

D. Roll-up summary is not the best fit for counting Cases across Account and Parent Account relationships.

===========

Use a Roll-Up Summary field on Account to count the related Opportunity records. Salesforce roll-up summary fields can calculate values from related records, and the COUNT summary type totals the number of related records. Trailhead also gives the Account and Opportunity example for roll-up summaries.

A formula field cannot count child records by itself. A lookup field only creates a relationship. AppExchange is unnecessary for this standard use case.

===========

The primary object of a custom report type is a fundamental design choice and cannot be changed after the report type is saved. Salesforce explicitly states in both the Enhanced and Legacy Custom Report Type Builder documentation that after saving a custom report type, the selected primary object cannot be changed. The primary object determines the base set of records represented by the report type and controls how additional related objects can subsequently be included. Consequently, the app builder must choose the Job Application object deliberately before saving the report type. Deployment does not permanently prevent a custom report type from being deleted, and the other options do not describe the core configuration limitation being tested. Therefore, B is the documented Platform App Builder consideration.

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

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

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

The correct answer is C. Flow.

This requirement needs automation that can do multiple things: update the To Be Installed checkbox when a Lift is sold, then notify an external system the next day using an outbound message. Salesforce states that Flow Builder is the optimal tool for triggered automation because it combines workflow and process automation capabilities in one point-and-click tool. Record-triggered flows can run when records are created, updated, or deleted, and can update records, send notifications, initiate processes, and maintain data consistency.

The “next day” timing points to a scheduled path in a record-triggered flow. Salesforce explains that scheduled paths delay automation for minutes, hours, days, or months after the triggering record change. Salesforce also documents outbound messages as a Flow Builder core action for record-triggered flows, used to send a SOAP message to a designated endpoint.

Approval Process is for approvals, Validation Rule only prevents invalid data, and Assignment Rule is for assigning records such as leads or cases. None of those tools can meet the full requirement.

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.

===========

Salesforce states that to make a custom object ' s records searchable, an administrator can create a custom tab set to Default On or Default Off ; creating the tab enables the object ' s search capability. Salesforce also warns that a custom object ' s tab must be visible for the user ' s profile and specifically says not to set the tab to Tab Hidden. A Search Layout controls which fields users see in search results but does not by itself enable object searchability. A search filter similarly refines results rather than enabling the custom object in Global Search. Therefore, among the available options, creating the custom tab with Default Off is the correct configuration.

The correct answer is C. To make a Contact’s Twitter profile available in the Salesforce mobile app, the app builder should add the Twitter component to the mobile Lightning record page. Salesforce guidance states that to make Twitter accessible on Account or Contact record pages and in the Salesforce mobile app, add the Twitter component in Lightning App Builder.

Why others are incorrect:

A is wrong because mobile navigation is for navigation items, not displaying a Contact Twitter profile.

B is unnecessary because Salesforce provides the component declaratively.

D may show a link, but it does not provide the standard Twitter profile component experience.

===========

The verified answer is B because Salesforce explicitly states that Formula fields are read-only and cannot be converted to another data type . Consequently, the existing formula field cannot simply be converted into an editable Text field, which eliminates A and D. The app builder should create a new Text field on Opportunity, extract or otherwise capture the current calculated Specialty__c values, and load those values into the new field. Sales representatives can then independently edit the new Opportunity value without changes to Account automatically recalculating it. Option C creates the editable field but fails to preserve the existing calculated values unless they are migrated.

Developer Pro satisfies both requirements. Salesforce ' s current sandbox reference states that a Developer Pro sandbox can be refreshed every one day and provides 1 GB of data storage by default, comfortably exceeding the required 250 MB. A standard Developer sandbox also has a one-day refresh interval, but its standard data-storage allocation is only 200 MB, so it does not satisfy the stated storage requirement without an additional storage upgrade. Partial Copy provides significantly more storage but can only be refreshed every five days. A Full sandbox mirrors production-scale data and storage but has a 29-day refresh interval. Therefore, Developer Pro is the only standard sandbox type among the choices that simultaneously supports at least 250 MB and daily refresh capability.

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

The correct answers are A. Assign app to profiles and B. Build a Custom Tab for the app.

Your option A appears corrupted as “Asking new options,” but the known Salesforce wording for this question is Assign app to profiles.

To make a custom Lightning app available to internal users, users must have access to the app through profile/app assignment. Salesforce documentation explains that assigned app settings specify which apps users can select from the Lightning Platform app menu.

A Custom Tab is also needed when exposing the custom app/component as something users can access from the Salesforce UI. Salesforce documentation states that custom tabs can appear in the app navigation bar and App Launcher.

Adding the app to a Visualforce page is not required, and uploading it to Static Resources is not how Lightning apps are made available to users.

===========

A record-triggered flow is the preferred declarative automation. Salesforce supports record-triggered automation when records are created, updated, or deleted, and its current Flow architecture includes after-delete processing for actions that must occur because a record was removed. The flow can trigger from Task deletion, use information from the triggering Task to identify the related Case, obtain the Case owner, and execute the email notification action. Assignment rules are designed primarily for assigning records such as Cases or Leads and do not respond to Task deletion. Escalation rules manage Case escalation timing, not deletion events. An Apex trigger could technically implement the requirement, but Platform App Builder principles favor native declarative automation when Flow supports the event and required action.

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

The validation rule must fire when two things are true:

Job_Accepted__c is already populated

Hire_Date__c is being changed

Salesforce’s ISCHANGED() function returns true when a field’s value changes from its previous value, and formula functions can be used in validation rules.

So this formula prevents users from changing the hire date after the candidate has accepted the offer:

NOT(ISBLANK(Job_Accepted__c)) & & ISCHANGED(Hire_Date__c)

Why others are incorrect:

The other options either use the wrong logical operator or validate the opposite condition. A validation rule must return TRUE only when Salesforce should block the save.

===========

A before-save record-triggered flow is Salesforce ' s most efficient declarative architecture when the only requirement is to update fields on the record that triggered the flow. Salesforce recommends before-save flows for these updates because changes are applied before the record is committed and do not require a second database save. The flow can reference the related Account ' s Industry and use an Assignment element to place the required default value in the triggering Opportunity ' s Stage field. Salesforce notes that changes made directly to $Record are persisted automatically, so a separate Update Records element is unnecessary. An after-save flow would work but introduce an additional database operation. Therefore, B provides the optimal Fast Field Updates pattern for this requirement.

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

The correct answer is C. Compact layout.

Compact layouts control the key fields shown in the record highlights area at the top of a record, including in the Salesforce mobile app. Salesforce documentation states that compact layout fields populate the record highlights section at the top of record views in the Salesforce mobile app.

Why others are incorrect:

A. Mobile navigation controls navigation menu items, not fields on a record.

B. Record Detail component shows record fields but does not specifically place key fields at the top.

D. Object specific action is used for actions, not at-a-glance field display.

===========

Flow Trigger Explorer is specifically designed to manage the execution sequence of record-triggered flows for the same object and trigger category. Salesforce documents that changing a flow ' s order in Flow Trigger Explorer changes its Trigger Order value, and that this value determines the sequence in which applicable flows execute. Therefore, the discount calculation flow should receive the earlier/lower trigger order and the notification flow the later order. This preserves separate flows while guaranteeing deterministic sequencing. An asynchronous path does not provide the same explicit ordering contract. A zero-minute scheduled path unnecessarily changes transaction timing. Combining both flows violates the stated ownership requirement and is not necessary because Salesforce provides native trigger-order controls. The correct Platform App Builder solution is therefore Flow Trigger Explorer.

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

The correct answer is B. Feed Tracking.

DreamHouse Realty wants changes to selected fields, such as Asking_Price__c and Real_Estate_Agent__c , to appear prominently in Chatter. This is exactly what Chatter Feed Tracking is used for.

Salesforce documentation states that feed tracking is available for record fields and can be configured for custom objects. Salesforce guidance also says admins can enable feed tracking from Setup, select an object, enable feed tracking, and choose fields to track.

A. Topics is used for categorizing Chatter posts, not automatically tracking field changes.

C. Pin Field is not the Chatter feature for tracking field updates.

D. Publisher Actions are actions users can take from the publisher, not automatic field-change tracking.

===========

The correct answer is C. Salesforce Schema Builder can create fields, including relationship fields, formula fields, and normal fields, and it also helps visualize existing object relationships. However, a field created in Schema Builder is not automatically added to the object’s page layout. Salesforce documentation states that after using Schema Builder, the field must be added through the Page Layout Editor.

Why others are incorrect:

A is incorrect because Schema Builder can create formula fields.

B is incorrect because Schema Builder can create relationship fields.

D is incorrect because Schema Builder is specifically used to view and understand object relationships.

===========

A roll-up summary field requires a master-detail relationship. Since Galaxy__c and Star__c currently have a lookup relationship, the app builder cannot create a standard roll-up summary field to count related Star__c records. The lookup must be converted to master-detail first, with Galaxy__c as the master and Star__c as the detail. Salesforce Trailhead confirms that roll-up summary fields display values on the master record based on directly related detail records in a master-detail relationship.

===========

Record type availability determines which record types a user can select when creating records. Salesforce allows record types to be assigned through profiles, permission sets, and permission set groups. Therefore, if the support team ' s profile currently provides access to Bronze, removing Bronze from that profile prevents users from selecting that record type, assuming it is not granted through another permission set. Organization-wide defaults and sharing rules regulate access to records after they exist; they do not control which record types a user can select during creation. A permission set group containing Platinum and Diamond could grant additional access but does not inherently revoke Bronze access already provided by the profile. The direct solution described by the options is therefore to remove the Bronze record type assignment from the support team ' s profile.

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

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

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

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

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

===========

The correct answer is C. Research and evaluate data enrichment products on the AppExchange to automate data entry.

The sales manager wants reps to spend less time manually entering business-card information while maintaining data quality. Salesforce AppExchange is the correct place to evaluate packaged solutions that extend Salesforce functionality. Trailhead describes AppExchange as a place to find solutions for business needs, and AppExchange contains business-card scanning apps that can create or match Salesforce Leads, Contacts, and Accounts with reduced manual entry.

A does not automate data entry.

B is not the best fit because Flow cannot read business cards by itself.

D is incorrect because formula fields calculate values from existing data; they do not capture business-card information.

===========

Resource is specifically intended for approvers that must be resolved dynamically at runtime. Salesforce ' s Flow Approval Process documentation defines Resource as an approver type that references a variable containing a user ' s username, a public group ' s API name, or a queue ' s API name. At runtime, the associated orchestration resolves the value and determines the appropriate assignee. Therefore, the app builder should store the dynamically determined username in a text variable and select that resource in the approval step. Selecting User would require choosing a predetermined user while designing the approval process, which does not satisfy the runtime requirement. Queue similarly identifies a configured queue rather than dynamically resolving an individual user. A Formula cannot directly substitute for the Approver Type configuration specified by Salesforce ' s Flow Approval Process model.

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

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

The correct answer is C.

The app builder needs to display only the first five digits from the parent Account’s ZIP+4 custom text field. Salesforce’s LEFT() function returns a specified number of characters from the beginning of a text string, so the correct formula is:

LEFT(Account.Zip_Code__c, 5)

Salesforce formula documentation confirms that LEFT returns characters from the beginning of a text string.

BEGINS() checks whether text starts with specific characters. LPAD() pads text to a specified length. TEXT() converts certain data types to text, but it does not extract the first five characters.

===========

Actions and Related Records identifies an after-save record-triggered flow . Salesforce states that this optimization should be selected when automation must perform actions after the triggering record has been saved, including updating related records, creating records, and sending notifications or email. The flow can trigger when an Opportunity changes to Closed Won, reference the related Account and Account owner, perform any required related-record operation, and invoke the appropriate email action. Fast Field Updates is a before-save configuration optimized only for changing fields on the triggering record itself. A validation rule cannot invoke an autolaunched flow, and a Screen Flow requires user interaction. Because this automation requires post-save related-record processing and an email notification, D is the Salesforce-supported architecture.

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

For an Accounts with Opportunities parent-child report type, Salesforce ' s current documentation confirms that the default report record count is based on the child Opportunity rows , not the number of unique parent Accounts. For example, if one Account has five Opportunities, Salesforce returns five report rows and a record count of five even though only one Account is represented. This occurs because the report output is driven by the child records. Therefore, D most precisely describes the current Salesforce behavior. Option A would incorrectly count unique Accounts, while B suggests both parent and child objects are separately included in the total.

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

Collection Sort is designed to reorder a collection and optionally reduce the number of records retained after sorting. Salesforce documents that the Collection Sort element can sort a record collection by a selected field in ascending or descending order and can specify the maximum number of items to keep afterward. The flow should therefore sort the Opportunity collection by Amount in descending order and retain only five records. A Collection Filter selects records based on Boolean-style criteria, but it does not identify the top N records based on ranking. A Decision controls execution paths rather than restructuring a collection. Transform maps data between structures but is not intended to rank and limit records. Collection Sort directly implements both requirements—highest Amount first and only five records retained.

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

The correct answers are B. Set organization-wide default to Private, D. Disable Grant Access Using Hierarchies, and E. Create a criteria-based Sharing Rule for the HR Department.

Set the Review object’s OWD to Private so review records are not visible to all employees by default. Organization-wide defaults define the baseline record access users have to records they do not own.

Disable Grant Access Using Hierarchies because this is a custom object and the requirement says only HR and the submitting employee should see the review. Salesforce allows this setting to be disabled for custom objects so managers higher in the role hierarchy do not automatically inherit access.

Create a criteria-based sharing rule for the HR department so HR can see the Review records even though the default access is private. Salesforce sharing rules are used to grant wider access beyond OWD.

Why others are incorrect:

A is not needed and a Master-Detail relationship to User is not the right access-control design.

C is incorrect because removing Review Read permission from non-HR users would also prevent the submitting employee from viewing their own submitted review.

===========

The correct answer is D. Approval process with a record-triggered flow.

Salesforce does not provide a simple “approval before delete” button behavior by default. The practical declarative pattern is to use an Approval Process for manager permission and a record-triggered Flow to automate the submit/delete logic. Flow includes a Submit for Approval action for Classic Approval Processes and also supports deleting records through the Delete Records element.

Why not the others:

A two-step approval process only handles approval routing; it does not complete the deletion automation by itself. A scheduled path or schedule-triggered flow is not appropriate because this is based on a user’s delete request, not a time-based batch process.

===========

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 A because Salesforce provides the Establish upper bound on existing picklists option to protect picklist performance by limiting inactive picklist values. Salesforce documentation states that this setting runs a query to identify picklists with fewer than 4,000 inactive values and enforce the limit.

Why others are incorrect:

B is for reusing picklist values across fields, not reducing inactive picklist performance impact.

C would worsen the issue because it removes limits on inactive values.

D is too drastic and not the recommended Salesforce feature for this issue.

===========

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 required metric is the total monetary value of won Opportunities for each Account. Salesforce supports roll-up summary fields on Account that aggregate Opportunity Amount and apply filtering criteria so that only qualifying child records are included. The appropriate configuration therefore uses SUM on Opportunity Amount with a filter restricting the calculation to Opportunities whose Stage represents Closed Won. Option C would incorrectly include open and lost Opportunities. COUNT-based options calculate the number of records rather than total sales value, and the roll-up belongs on the Account because that is where the summarized result must appear. Salesforce ' s current documentation specifically gives the example of an Account roll-up displaying total Opportunity amount and filtering the aggregation to only won Opportunities.

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

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.

===========

A Screen Flow is required because the process must interact directly with a user and collect input. Salesforce defines screen flows as interactive automation that uses Screen elements and screen components to gather information from running users. After the required information is captured, an Update Records element can locate the related Account and write the supplied values to that existing record. Salesforce ' s Screen Flow documentation specifically describes adding an Update Records element and identifying an Account by its record ID when existing data must be changed. An autolaunched flow cannot contain normal interactive Screen elements. Record-triggered and schedule-triggered flows execute from record or time-based events rather than interactive user input. Create Records is also incorrect because the requirement is to update an existing related Account, not create a new one.

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

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 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.

===========

The correct answer is A. Flow.

The requirement says the Opportunity should store the Account Billing State value, but the value must remain static after the Opportunity is created. A record-triggered Flow is the recommended declarative automation because it can run when an Opportunity is created and populate a custom field with the related Account’s Billing State. Salesforce Trailhead describes record-triggered flows as automation that can run when a record is created or updated, and can update the triggering record or related records depending on configuration.

D. Formula field is incorrect because formula fields are automatically calculated and read-only. A formula would continue to reflect the current Account Billing State, so it would not preserve the original value after creation.

B. Apex is not the recommended first choice because Flow handles this requirement declaratively.

C. Roll-up summary field is incorrect because roll-ups aggregate child records; they do not copy a parent Account field value onto an Opportunity.

The correct answer is D. Approval process.

The requirement is to automate travel request form submission and enforce an internal approval policy. Salesforce approval processes are specifically designed to automate how records are submitted, reviewed, approved, rejected, recalled, and acted upon. Salesforce Trailhead explains that an approval process defines the criteria a record must meet before submission, the approval steps, approvers, and the actions taken when the record is approved or rejected.

This exact scenario also aligns with Salesforce’s travel approval training example, where a Travel Approval object uses an approval process to route travel requests to the employee’s manager and, when needed, to another approver.

A is incorrect because assignment rules route leads or cases, not approval requests.

B is incorrect because validation rules prevent invalid saves but do not manage approval routing.

C is incorrect because Apex is unnecessary when a standard declarative approval process fits the requirement.

===========

The correct answer is B.

This is a one-user exception. Salesforce recommends using permission sets to extend access without changing the user’s base profile. A permission set can grant read-only field access through field-level security to just the selected customer service agent. Salesforce documentation explains that permission sets extend user access, and field permissions control whether users can view or edit individual fields.

Why others are incorrect:

A creates a new profile for one user, which is not the recommended scalable solution.

C is not accurate because field-level security is assigned through profiles or permission sets, not directly to one user from the field alone.

D would give all users with the Customer Service profile read-only access, not only the single agent.

===========

The correct answer is B. Universal Containers has internal Account OWD set to Public Read/Write, which lets internal users broadly access Account records. However, Experience Cloud / customer community users can have a separate external sharing model. Salesforce documentation explains that External Organization-Wide Defaults provide separate default access for external authenticated users so companies can better secure data for community users.

Setting the Account external OWD to Private prevents customer community users from seeing all company Account records by default.

Why others are incorrect:

A record types do not control record visibility.

C an owner-based sharing rule would grant more access, not restrict default access.

D permission sets grant object/field permissions; they do not replace OWD record-sharing control.

===========

The correct answer is C. Add the standard Chatter feed component.

To add Chatter feed functionality to a custom object Lightning record page, the app builder should use the standard Chatter component in Lightning App Builder. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed combination on a record page.

A is incorrect because no custom Chatter feed component is required. B is incorrect because related lists do not add the Chatter feed. D is incorrect because the standard Chatter component is already available; an AppExchange component is unnecessary.

===========

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

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

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

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

===========

The correct answer is A.

UC has three Lead sources: web, trade shows, and partners. Some Lead information is common to all, while other fields are unique to each source. The best configuration is to use Lead record types with separate page layouts so each type of Lead shows the fields relevant to that process. Salesforce documentation states that record types allow different business processes, picklist values, and page layouts for different users or record categories.

B is not ideal because it leaves irrelevant fields visible and relies on users to collapse sections. C unnecessarily creates a different Lead object for the partner community. D is incorrect because separate custom objects would fragment Lead management and prevent standard Lead functionality from being used consistently.

===========

A standard custom Picklist field is the correct data model because each Loyalty Member must have exactly one value from a controlled set: Standard, Plus, or Elite. Salesforce defines a Picklist as a field that lets users select a single value from a predefined list. The value set can be restricted so users cannot introduce inconsistent values outside the administrator-approved choices. Picklists also work naturally with Salesforce reporting, including filtering and grouping by the selected value. A multi-select picklist would incorrectly allow one member to belong to multiple tiers simultaneously. A free-form Text field would permit spelling and capitalization variations that undermine data consistency and reporting. A formula field derives its value from other data rather than allowing users to select one of the defined tier classifications.

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

The correct answer is C. App Manager.

To add components to the Utility Bar of an existing Lightning app, the app builder edits the app from Setup → App Manager, then uses the app’s Utility Items configuration. Salesforce Help specifically states that to edit or add a utility bar to an existing app, use App Manager and click Edit for the app.

Why others are incorrect:

A is close, but the entry point for editing an existing app’s utility bar is App Manager, not directly Lightning App Builder.

B is wrong because a Lightning Record Page is for record page layout/components, not app-level utility bar configuration.

D is wrong because App Menu is for launching apps, not configuring them.

===========

The correct answer is C. Create a Partial Copy Sandbox and use a sandbox template.

A Partial Copy Sandbox includes metadata plus selected production data and supports the use of a sandbox template to control which objects and data are copied. This allows the app builder to exclude confidential custom objects. It also meets the weekly refresh requirement because Salesforce allows Partial Copy sandboxes to be refreshed every 5 days.

B. Full Copy Sandbox can use a sandbox template, but it does not meet the weekly refresh requirement.

A and D are incorrect because Developer and Developer Pro sandboxes are not the correct choice when the sandbox must include selected production data records through a sandbox template.

===========

Salesforce exposes pending scheduled-path actions on the Time-Based Automations Setup page. Salesforce ' s Scheduled Paths documentation explicitly instructs administrators to enter Time-Based Automations in Setup ' s Quick Find and select that page to view pending scheduled paths. This unified monitoring page supports queued and scheduled Salesforce automation, including scheduled paths. Flow Trigger Explorer is used to inspect and manage the ordering of record-triggered flows on an object; it is not the queue for future scheduled executions. Apex Flex Queue monitors queued Apex batch jobs, which are unrelated to Flow scheduled paths. Paused and Failed Flow Interviews is intended for paused or faulted flow interviews rather than normally scheduled future actions. Therefore, Time-Based Automations is the correct monitoring location for verifying that the Case email action is queued.

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

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 C. Internal profiles.

When a new custom field is created using Schema Builder, Salesforce sets field-level security by default as visible and editable for internal profiles. This does not mean every possible profile, such as external/community profiles, automatically gets access. Salesforce Help specifically notes this default behavior for fields created in Schema Builder.

===========

The correct answer is C.

Universal Containers wants to accept clean data and verify that important fields are entered. The best solution is a validation rule, because validation rules verify that data entered by users meets defined standards before the record can be saved. This is stronger than making a field required only on a page layout, because validation rules can enforce requirements based on conditions such as record type.

A is weaker because page-layout required fields apply mainly to that UI layout and do not provide the same conditional data-quality enforcement. B is reactive cleanup after bad data exists. D can calculate or display a value, but it does not enforce user data entry by itself.

===========

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 C. Unable to reference the child records.

A formula field on Account cannot directly pull data from multiple related Contact records because Contacts are child records of Account. Cross-object formulas work by referencing fields through supported parent relationships, not by traversing from a parent record down to multiple child records. Salesforce documentation describes cross-object formulas as formulas that reference fields on related objects, especially parent records through relationships.

Because an Account can have many Contacts, Salesforce does not expose that child relationship in the formula editor as a single field reference. For summarized child data, the app builder would normally use a roll-up-style solution where supported, or automation such as Flow.

A is unrelated unless the formula has already exceeded character limits.

B is misleading because the core issue is not simply that Account and Contact lack master-detail; it is that formulas cannot directly reference child records.

D is not supported by the scenario.

===========

A Screen Flow is Salesforce ' s interactive flow type and is specifically intended to guide users through a business process while collecting input. The app builder can create multiple Screen elements representing troubleshooting steps, display instructions and questions, store the representative ' s responses, and then use Create Records to generate the follow-up Case at the end of the process. Salesforce explicitly distinguishes Screen Flows from background automation because Screen Flows require user interaction and support screens, choices, and other interactive components. Schedule-triggered, record-triggered, and platform event-triggered flows execute automatically in the background and therefore do not provide the required multi-step wizard interface. The combination of guided navigation, data capture, and record creation makes Screen Flow the appropriate declarative solution.

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

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.

===========

Path is the best solution because it provides users with a structured, stage-oriented experience based on a picklist field. For each Path step, an app builder can highlight key fields and provide Guidance for Success so users know which information should be captured and how to handle the record consistently. Salesforce officially documents that Path steps are based on selected picklist values and can display up to five key fields plus guidance, tips, links, and company policy information. This makes Path appropriate for helping service users consistently address Case Priority within a defined process. In-App Guidance provides contextual prompts but does not structure the record process in the same way. Flow is unnecessarily complex for simple user guidance, while Next Best Action is intended for recommendations rather than standardized field-entry guidance.

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

The correct answer is D. For use on the utility bar.

For a custom Lightning web component to appear as an available component in the utility bar, it must be exposed in its metadata configuration with the lightning__UtilityBar target. Salesforce developer documentation states that lightning__UtilityBar enables a component to be used as a utility item in an app’s utility bar, and the component must be exposed with the appropriate target.

B. For use in Lightning App Builder is broader and not enough by itself for utility-bar availability. C. For use on record pages exposes the component for record pages, not the utility bar. A. For use in App Manager is not the correct component target wording.

===========

A Template-Triggered Prompt Flow is specifically designed to provide dynamically retrieved Salesforce data and additional logic to Prompt Builder templates. Salesforce states that these flows perform logic and actions that generate output text merged into the associated prompt template. The app builder can retrieve the Contact ' s related Order records, construct appropriate prompt instructions, and pass that grounded context back to the Field Generation prompt template. Salesforce also documents the Add Prompt Instructions element as available specifically in template-triggered prompt flows. A record-triggered flow responds to database changes, while a schedule-triggered flow runs at predefined intervals. A generic autolaunched flow does not provide the dedicated Prompt Builder integration required by the scenario. Therefore, A is the correct flow type for grounding this prompt template.

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

Dynamic Related List - Single provides the advanced declarative customization required in this scenario. Salesforce documents that this component allows an app builder to select and reorder displayed columns, define the record sort order, filter related records, determine how many records appear, and show or hide list actions. These capabilities go beyond the standard Related Lists and Related List - Single components, which are more dependent on traditional page-layout configuration. Related List Quick Links provides compact navigation to related lists rather than detailed control of list behavior. Because the requirement specifically combines configurable sorting with action visibility, Dynamic Related List - Single is the precise Salesforce component designed for the use case. It can be configured directly through Lightning App Builder on a supported record page.

A Platform Event-Triggered Flow is specifically designed to subscribe to a platform event and execute automatically when an event message is received. External applications can publish platform-event messages into Salesforce, allowing loosely coupled, event-driven integration. Once the out-of-stock event arrives, the flow can evaluate its payload and use Create Records to generate the procurement Task immediately. A record-triggered flow requires a Salesforce record create, update, or delete operation and therefore is not triggered directly by an external message. An autolaunched flow without a trigger must be invoked by another process, while a Screen Flow requires interactive user execution. Salesforce explicitly defines Platform Event-Triggered Flow as a background flow that launches when a platform event occurs or when its event message is received. Salesforce

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

The correct answer is D. Create an Apex Trigger on the Account object.

The requirement is conditional: allow Account deletion generally, but block deletion when the Account has open Opportunities. A validation rule is not the correct tool because validation rules evaluate record data during save operations, while this requirement is specifically about preventing a delete operation.

An Apex before delete trigger can query related open Opportunities and call addError() on the Account record to stop the delete. Salesforce Apex documentation confirms that triggers can run before or after delete events, and trigger errors can prevent DML operations from completing.

A is incorrect because removing Delete permission blocks all Account deletion.

B is incorrect because removing the Delete button is not security and does not stop deletion through other channels.

C is incorrect because validation rules are not the right mechanism to block conditional deletes.

===========

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 answer is D. Apex unit test failures.

The option text says “Apps unit test failures,” but the intended Salesforce answer is Apex unit test failures. When a package containing Apex is installed or deployed to production, Salesforce runs Apex tests. If the required tests fail, the package installation can fail. Salesforce documentation states that package installation involving Apex runs unit tests, and production deployments with Apex require tests to pass.

A, B, and C are not the best answers because the package already installed successfully in a Full Copy sandbox matching production. The most certification-relevant production failure reason is Apex test failure.

===========

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 C. Add the standard Chatter feed component.

In Lightning App Builder, Salesforce provides a standard Chatter component for record pages. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a related list component does not add the Chatter feed.

B is incorrect because the standard Chatter component is available in Lightning App Builder; it does not need to come from AppExchange.

D is incorrect because a custom component is unnecessary when Salesforce provides the standard Chatter component.

===========

The correct answer is C. Developer sandbox.

For small, individual projects where teams need separate environments before moving work into a larger shared testing sandbox, a Developer sandbox should be considered first. It is intended for development and testing of configuration changes in an isolated environment and is the lowest-cost sandbox option compared with Developer Pro, Partial, and Full sandboxes. Salesforce describes sandbox types for different testing and development needs, with Developer and Developer Pro sandboxes copying configuration/metadata rather than full production data.

Developer Pro provides more storage, but the question emphasizes small projects and keeping costs down. Partial and Full sandboxes are better for broader testing with data, but they are not the first choice for many small isolated development efforts.

===========

The correct answer is D. Accordion.

For an object with 100+ fields, the app builder should avoid one large monolithic Record Detail area. Salesforce Trailhead explains that Dynamic Forms breaks the Record Detail component into individual field and section components, which can be placed in separate tabs and accordion sections.

Salesforce also states that moving lower-priority fields into tabs or accordion sections can improve page performance because the content is not visible when the page first loads.

A. Highlights panel is for key record fields and actions at the top of the page. B. Record detail would keep fields together in one large block. C. Field section groups fields, but the better component for breaking a large page into collapsible organized areas is Accordion.

===========

The correct answer is D.

Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object’s master-detail relationship can’t be converted into a lookup relationship.

In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.

A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.

===========

The correct answer is C. Record Detail.

The Record Detail component on a Lightning Record Page displays the fields and sections from the object’s assigned page layout. After using Lightning Object Creator to create the object, fields, and data, the app builder must add the Record Detail component if users need to see the fields from the page layout on the Lightning Record Page. Salesforce documentation states that the Record Detail component displays fields and sections from the page layout associated with the object.

Why the other options are incorrect:

Highlights Panel shows key record actions and compact-layout information.

Recommendations displays recommendation records.

Path shows guided stage/status progression, not all page-layout fields.

===========

The correct answer is A. Quick Action on the Account object.

Universal Containers wants users to create Opportunity records related to an Account, with many Opportunity fields automatically populated from the Account and some fields entered by the user. The best solution is an object-specific Quick Action on Account that creates an Opportunity. Object-specific actions run in the context of the parent record, and predefined field values can automatically populate fields to make record creation faster and more consistent.

C is incorrect because a Quick Action on Opportunity would not naturally start from the Account context. B and D are incorrect because assignment rules are not used for creating related Opportunities or prepopulating fields.

===========

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.

===========