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

A custom link or button that passes the current Account ID into a report filter provides direct access to a report showing only records associated with the Account being viewed. Salesforce ' s official documentation specifically describes creating an Account custom link that opens a report and automatically filters the results by the current Account ' s record ID. This precisely satisfies the requirement for Account owners to access the relevant Asset report from the Account record page. A dashboard filter requires dashboard-level filtering and does not inherently pass the current record context. Scheduled Reports deliver reports at scheduled times, while a Custom Report Type merely defines the objects and fields available for reporting. This corrects the PDF answer key, which lists A; current Salesforce documentation supports B for direct filtered-report access.

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

The correct answers are B. Each object can have up to 25 custom external ID fields and D. An external ID field can be an auto-number field.

Salesforce documentation states that each object can have up to 25 custom external ID fields. It also confirms that supported external ID field types include custom auto-number, email, number, and text fields.

A is incorrect because the limit is per object, not per org.

C is incorrect because a URL field is not one of the supported external ID field types.

===========

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

===========

omprehensive and Detailed Explanation with all Platform App Builder documents: =

The correct answer is C. Validation Rule.

DreamHouse Realty needs to prevent an Opportunity from entering the Qualified stage unless Expected_Close_Date__c is populated. A validation rule is the correct feature because validation rules check whether record data meets defined requirements before the record can be saved. Salesforce also provides examples of validation rules used to control Opportunity stage changes.

Example formula:

AND(

ISPICKVAL(StageName, " Qualified " ),

ISBLANK(Expected_Close_Date__c)

)

A is incorrect because record types do not enforce this conditional requirement by themselves.

B is incorrect because page layouts cannot reliably enforce conditional required fields by stage.

D is incorrect because Activity History does not validate data entry.

===========

The correct answers are B. Upload the lead list using the Import Wizard and select a Matching Type to prevent duplicate lead creation and D. Utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads.

For 400 leads, the Data Import Wizard is appropriate because Salesforce supports importing leads and other common objects with the wizard, and it can handle up to 50,000 records.

Salesforce documentation for lead imports states that choosing a matching type sets criteria for avoiding duplicate leads when using the Data Import Wizard.

Duplicate Management also uses matching rules and duplicate rules to identify and control duplicates. Salesforce states that duplicate rules can block users from creating duplicate records, including lead duplicates.

Why others are incorrect:

A is incorrect because Data Loader’s update operation updates existing records and normally requires record IDs or proper matching/upsert configuration; it is not the best duplicate-prevention answer here.

C is not the correct Salesforce setup wording. The correct tools are Lead Matching Rules and Duplicate Rules.

===========

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.

===========

The correct answer is A. Build a global action to create Contacts.

Sales reps need a fast mobile-friendly way to create new Contact records and complete additional details later. A global quick action is the best fit because it lets users create records quickly without needing to navigate deeply into the app. Salesforce documentation states that global actions allow users to create or update records without leaving the page they are on. Salesforce also documents that Create a Record global actions let admins choose the object to create, such as Contact.

Salesforce mobile uses quick actions in the action bar/action menu, making them suitable for fast record creation on mobile.

B. Path is used for guided stages, not quick contact creation. C. Mobile menu customization improves navigation but does not simplify the create process enough. D. Compact layout controls key field display, not fast record creation.

===========

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.

===========

The correct answer is B. Apex unit test failures.

When installing a package that contains Apex in a production org, Salesforce runs Apex tests as part of the installation/deployment validation. Salesforce documentation states that package installs or upgrades can fail when Apex test requirements are not met.

Even though the unmanaged package was tested in a Full Copy sandbox, production installation can still fail if Apex tests fail during production validation.

Why others are incorrect:

A, C, and D are not the best answer because the package already installed successfully in a Full Copy sandbox that matched production. The most certification-relevant reason for production failure is Apex unit test failure.

===========

The correct answers are B. Flow Builder and D. Escalation rules.

Escalation rules are the most direct Salesforce Service feature for this requirement. They are designed to automate case escalation when cases are not resolved or not acted on within a defined time period. Salesforce documentation explains that escalation rule entries can use business hours, and escalation actions can send notification emails when the case escalates.

Flow Builder can also be used because record-triggered flows support scheduled paths, allowing automation to run after a defined time from a triggering record event. A flow can check whether the Case is still in New status and then send a notification. For strict business-hour calculation, the app builder must design the flow carefully around the correct time source/business-hour logic.

A is incorrect because validation rules only prevent invalid data from being saved; they do not wait four business hours and send notifications.

C is incorrect for the Platform App Builder context because Scheduled Apex is a programmatic approach, while declarative automation tools are available and preferred for this requirement.

===========

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. 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 requirement specifies detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields support:

Multiple lines of text

Inline images

Hyperlinks

Formatting (bold, italic, lists)

Salesforce documentation confirms that Rich Text Area fields are the standard choice when storing formatted content on a record. (Salesforce Help)

D. Long Text Area supports only plain text, not images or links.

C. URL is for a single web address only.

B. Lightning Web Component is for custom UI elements, not a field type.

===========

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.

===========

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 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 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 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 answers are A and B .

The requirement is to display a visual flag image based on Case Priority. Salesforce’s own sample image formula for Case Priority uses the IMAGE() function with CASE() to display green, yellow, or red flag images.

Both formulas are valid because:

A uses IMAGE() with nested IF() and ISPICKVAL() checks.

B uses IMAGE() with CASE() to return the correct image URL.

C and D are incorrect because they return only the image URL text, not the actual image. The formula must use IMAGE() to display a visual flag.

===========

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

===========

Permission Sets are the appropriate mechanism for granting additional object and field access to users who perform a particular function without changing their base profiles. The app builder can create a permission set for hiring managers that grants the required access to JobApplication__c and Read access to the sensitive salary fields through field-level security. Salesforce specifically recommends permission sets and permission set groups rather than profiles for extending field permissions. Sharing Rules and organization-wide defaults govern record-level access; they do not make fields visible when field-level security hides them. Page Layouts control which fields are placed in the interface but cannot override field-level security. Because salary information represents restricted field-level data that only a designated functional group should see, Permission Sets provide the precise least-privilege solution.

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

The correct answer is C. AppExchange package.

The key word is daily. Salesforce’s native Data Export Service supports manual and scheduled exports, but Salesforce documentation states that backup files can be generated manually once every 7 days for weekly export or 29 days for monthly export, depending on edition. That does not meet an automatic daily backup requirement.

For daily automated backups, the app builder should recommend a backup solution from AppExchange. Report export is not an org backup, and refreshing a full copy sandbox is not a backup automation tool.

===========

The verified current-platform answer is D. Salesforce Conditional Field Formatting in Lightning App Builder allows Dynamic Forms fields to display configurable icons and colors according to rules and criteria. Critically, Salesforce explicitly supports formula fields when the formula resolves to a supported data type, so the existing formula field can drive the formatting rules. The app builder can configure different icons and icon colors without embedding presentation logic into the formula itself. IMAGE() and CASE() can produce formula-based images, but they are an older technique and do not provide the native Dynamic Forms conditional-formatting capability described by the current platform. Field help is static, and Screen Flow is unnecessarily complex. This corrects the PDF answer key, which lists A; current Salesforce documentation supports D.

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

The correct answer is B. Use an AppExchange solution.

UC has a time-sensitive need and the developers are delayed for several months. AppExchange is the best recommendation because it provides ready-to-install apps, components, and solutions that can extend Salesforce without building everything from scratch. Salesforce describes AppExchange as the marketplace for ready-to-install solutions, including apps, components, and experts.

A and C still require building the solution internally. D. Bolt solution is more specific to prebuilt Experience Cloud/community templates and is not the best answer for a general custom component requirement. Salesforce describes Bolt Solutions as combinations of Lightning apps, business process flows, and Experience Builder templates/pages.

===========

Agentforce Service Agent is built for autonomous, conversational customer support. Salesforce states that Agentforce Service agents can process incoming customer requests, resolve common inquiries autonomously, use business data, and execute actions without requiring a service representative for every step. Agent actions can invoke Flow or Apex and perform operational tasks such as retrieving order status or updating fulfillment information. That matches Cloud Kicks ' requirement for dynamic support that can investigate missing packages, determine delays, and take appropriate customer-service actions. An approval flow introduces unnecessary human review, while scheduled email templates provide static rather than real-time assistance. A Screen Flow could collect issue information but would generally create a Case rather than independently reason about the customer ' s request and perform resolution actions.

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

The correct answer is A. Allow Salesforce to import Contacts from mobile device Contact lists.

Salesforce supports importing contacts from a mobile device contact list into Salesforce from the Salesforce mobile app using Import from Device. Salesforce also notes that users need the permission Allow Salesforce to import Contacts from mobile device Contact lists to use this feature.

Why others are incorrect:

B only notifies users; it does not move phone contacts into Salesforce.

C helps users create/edit records offline in Salesforce, but it does not import contacts already entered in the phone’s contact list.

D is for account-contact relationship modeling, not mobile contact capture.

===========

The correct component is the Highlights Panel. More precisely, Salesforce refers to the newer version as the Dynamic Highlights Panel, which displays up to 12 key record fields configured in Lightning App Builder. Since the option list only says Highlights Panel, option B is the exam match.

Path is for guiding users through stages. Accordion is for collapsible sections. A custom Lightning Web Component is not needed because Salesforce provides this functionality declaratively.

===========

The correct answer is C.

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

The correct answer is A because Case_Issue__c is described as a junction object. In Salesforce, a junction object is typically built with two master-detail relationships to model a many-to-many relationship.

Salesforce documentation states that sharing access to a junction object record is determined by the user’s sharing access to both associated master records and the sharing setting on the relationship fields.

So, for auditing users to view Case_Issue__c records, they need read access to both parent/master records: Case and Issue__c.

Why others are incorrect:

B misses access to Issue__c.

C includes only the junction object and misses both parent/master records.

D misses access to Case.

===========

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.

===========

A schedule-triggered flow is appropriate when Salesforce must periodically identify records approaching a date and perform an automated action. Salesforce documents schedule-triggered flows as automation that runs at a specified time and frequency for batches of records. A daily scheduled flow can use Get Records to identify Contracts whose End Date is five days away, obtain the related Account information, and invoke Send Email for the Account owner. Salesforce provides the same architectural pattern for expiration reminders, where a daily schedule-triggered flow checks records and sends notifications a specified number of days before expiration. Screen Flow requires user interaction, while an autolaunched flow does not independently provide the required recurring schedule.

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

The correct answer is A. TODAY().

The formula needs to calculate how many whole days have elapsed since a marketing communication was sent. The TODAY() function returns the current date as a Date value, which is appropriate for whole-day calculations. Salesforce documentation also shows that TODAY() can be used with addition and subtraction operators for date calculations.

NOW() returns a Date/Time value and can introduce fractional day/time calculations. DATEVALUE() converts a Date/Time or text value into a Date, but the question asks which function should return today’s date for calculating elapsed days. DATETIMEVALUE() returns a Date/Time value, not the desired whole-date calculation.

===========

The correct answer is B. Quick action.

Sales reps need to create Opportunity records directly from an Account, with several fields prepopulated. This is an object-specific Quick Action use case. Salesforce states that object-specific actions let users create or update records in the context of a particular object. Salesforce also supports predefined field values for quick actions, which can prepopulate fields and make record creation faster.

Default action is not the correct feature name for this requirement. Custom button and custom link are older navigation-style tools and are not the best Lightning/mobile-friendly option for creating related records with predefined values.

===========

The Full sandbox is the appropriate environment for final User Acceptance Testing when realistic production-scale data is required. Salesforce describes a Full sandbox as a replica of the production organization containing metadata and production data and identifies it as suitable for testing, staging, load testing, and UAT. The app builder should therefore move the developed components from the Developer sandbox to the Full sandbox, allow sales operations users to validate the commission calculations against representative Opportunity data, and deploy to production only after successful testing. Conducting UAT directly in production creates unnecessary operational risk. A Developer sandbox contains metadata but does not automatically contain production data at the required scale. Therefore, D follows the proper Salesforce application lifecycle and testing model.

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

omprehensive and Detailed Explanation with all Platform App Builder documents: =

The correct answer is A. The report type is already based on Opportunities with or without Shipments, so the app builder should not change the report type’s primary object. To expose Account Rating, the app builder should edit the custom report type layout and use Add fields related via lookup from the Opportunity view, because Opportunity has a relationship to Account. Salesforce documentation confirms that custom report types allow fields from objects not directly included in the report type structure by using Add fields related via lookup.

Why others are incorrect:

B is incorrect because the standard Account–Opportunity relationship cannot simply be changed to master-detail.

C is incorrect because changing the primary object to Account would change the report purpose.

D is incorrect because adding a field to a record page does not make it available in a report type.

===========

The verified answer is A. Applications is the detail object in a master-detail relationship, so its record access is inherited from the Internship master. Salesforce explicitly states that custom objects on the detail side cannot have independent sharing rules, manual sharing, or queues because they do not have an independent Owner field. To let recruiters edit Application records, the app builder must therefore grant the required Read/Write access to the related Internship master records, such as through a sharing rule. Option C is invalid because the detail object ' s sharing model cannot simply be independently configured as Public Read/Write. Option D is also invalid because a detail custom object cannot have its own sharing rule in this configuration. This corrects the PDF answer key, which identifies D.

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

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.

===========

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

===========

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. 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 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 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 B. This lookup relationship will need to be converted to a master-detail relationship before a roll-up summary field can be created.

A Salesforce roll-up summary field is created on the object that is on the master side of a master-detail relationship. Lookup relationships do not support standard roll-up summary fields. Salesforce documentation confirms that roll-up summary fields are defined on the master object in a master-detail relationship.

A and D are incorrect because formula fields cannot count related child records across a lookup relationship.

C is incorrect because the relationship is currently lookup, so a standard roll-up summary field cannot be created yet.

===========

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 answers are C. Currency, D. Date, and E. Percent.

Salesforce roll-up summary fields support different field types depending on the summary operation. For SUM, Salesforce supports number, currency, and percent fields. For MIN and MAX, Salesforce supports number, currency, percent, date, and date/time fields. Therefore, from the options given, Currency, Date, and Percent are valid field types for roll-up summary calculations.

Checkbox is not a supported field type for roll-up summary aggregation. Time is not the intended supported option in this exam context.

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. 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 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 answer is C. Checkbox.

Universal Containers needs to track whether a contract was sent or not sent before an Opportunity is marked Closed Won. This is a simple Yes/No reporting requirement, so a Checkbox field is the best field type. Salesforce checkbox fields are represented as True/False values and can be used in reports and list view filters.

Picklist is unnecessary for a two-state value. Text and Text Area would create inconsistent reporting because users could type different values.

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 correct answers are A. Use a master-detail relationship between the Park and Trail objects and C. Use a roll-up summary field on the Park record to show the total number of trails .

To show the total number of child Trail records on the parent Park record without code, the app builder should use a roll-up summary field . Salesforce documentation states that roll-up summary fields display values on a master record based on related detail records.

That means Park should be the master object and Trail should be the detail object. Then a roll-up summary field on Park can count the related Trail records.

B is incorrect because standard lookup relationships do not support roll-up summary fields.

D is incorrect because a formula field cannot count multiple child records.

===========

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.

Agentforce is Salesforce ' s platform for autonomous AI agents that can understand requests, reason over context, retrieve business information, determine appropriate next steps, and execute actions. Salesforce describes Agentforce agents as autonomous and proactive applications capable of taking action with or without continuous human intervention. Agents can use Salesforce CRM data and invoke flows, Apex, APIs, prompts, and other configured actions to complete business tasks. This directly matches the requirement for end-to-end customer service handling. Case Assignment Rules only route Cases. Experience Cloud with Live Chat provides customer interaction channels but does not independently reason and execute complete workflows. Einstein Bots provide conversational automation but do not represent the current autonomous agent architecture described in the scenario. Agentforce is therefore the verified answer.

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

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

In Lightning App Builder, Salesforce provides a standard Chatter component. 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 custom Chatter feed component is not needed.

C is incorrect because this does not come from the AppExchange/App College.

D is incorrect because Chatter feed is not added by using the standard related list component.

===========

The correct formula is:

IF(

NOT(ISBLANK(Nickname__c)),

Nickname__c,

FirstName

)

Salesforce recommends ISBLANK() to check whether a field has no value, including text fields. Since Nickname__c is optional, the formula first checks whether it is not blank. If it has a value, Salesforce uses the nickname. If it is blank, Salesforce uses FirstName .

A is incorrect because BLANKVALUE() is not used this way inside NOT() .

B is incorrect because the logic is reversed and ISNULL() is not preferred for text fields.

D is incorrect because TEXT() is not needed for a text field and does not perform a blank check.

===========

The correct answers are B. AppExchange and D. Lightning Components.

Salesforce Trailhead states that custom Lightning components can be created with Lightning Web Components or Aura, and existing Lightning components can also be installed from the AppExchange. Custom components configured for Lightning App Builder appear in the Lightning Components pane and can be added to Lightning pages.

Why others are incorrect:

A. Import Wizard is a data import tool, not a source of UI components.

C. Apex Code provides server-side logic, but Apex itself is not a Lightning page component resource.

===========

The correct answer is C. Internal profiles.

When an app builder creates a custom field using Schema Builder, Salesforce sets field-level security for custom fields to visible and editable for internal profiles by default.

That is why B. All profiles is not the best answer. Salesforce’s documented default is specifically internal profiles, not every possible profile type.

===========

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 answers are A. Data loss may occur when changing custom field types and D. Field History Tracking records value changes of 255 characters or less.

A is correct because Salesforce warns that changing the data type of an existing custom field can cause data loss in certain situations. This is a key consideration before converting Text Area (Long) fields to Rich Text Area fields.

D is correct because Salesforce field history tracking has a character limitation. Salesforce tracks changes to fields with more than 255 characters as edited, but it does not record the old and new values. That means long/rich text changes beyond that limit do not provide full before-and-after history values.

Why others are incorrect:

B is not the relevant consideration for this field conversion requirement.

C is incorrect because Salesforce reports do not display rich text field values of all lengths fully; Salesforce documentation notes report display limits for long text and rich text area fields.

===========

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.

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.

===========

To embed a chart on the Account detail page showing related Opportunities by Stage, the report must summarize Opportunities, not just list them. Salesforce documentation specifies that summary reports allow grouping by fields (e.g., Stage) and can be used in Report Chart components. (Salesforce Help)

Tabular reports cannot be grouped and therefore cannot provide the aggregated chart needed.

The report must be built on the Opportunity object because the records being summarized are Opportunities, not Accounts.

===========

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 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 answers are A. Processes that update record owners do not transfer child records and C. Processes will fail on records owned by inactive users.

When Process Builder updates a record owner, Salesforce does not automatically transfer associated child records such as related Contacts or other child records. Salesforce documentation says processes that update owners do not automatically transfer associated items, so separate update actions are required for each related record type.

Also, Salesforce documentation states that processes can’t update records owned by inactive users. If records are still owned by inactive users, automation that tries to update them can fail.

B is not the correct consideration here.

D is not the best answer because the issue described is about ownership-based access to Accounts and Contacts, not simply whether a process version is active.

===========

A Partial Copy sandbox is specifically intended for testing scenarios that need representative production data without requiring an entire production dataset. Salesforce states that Partial Copy sandboxes contain production metadata plus a selected sample of production data defined through a sandbox template and explicitly identifies User Acceptance Testing, integration testing, and training as appropriate uses. The template also lets administrators select the objects required for testing and exclude sensitive or irrelevant data sets when necessary. Developer and Developer Pro sandboxes primarily copy metadata and do not automatically provide representative production data. A Scratch Org is a temporary source-driven development environment rather than the preferred UAT environment for actual business users and realistic production-derived data. Therefore, A is the appropriate sandbox type.

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

To optimize Salesforce Mobile experience:

B. Minimize formula fields and lookup fields improves page load performance on mobile devices.

C. Put key fields in the compact layout ensures important information is visible immediately.

E. Use Global Actions simplifies creating or updating records from mobile quickly.

Salesforce documentation on mobile best practices recommends limiting complex fields, prioritizing compact layouts, and using quick actions for essential functionality. (Salesforce Help)

A is incorrect because default values improve speed and reduce user errors, not eliminate them.

D is unnecessary; Lightning layouts are responsive and do not require separate OS-specific layouts.

===========

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 solutions are D. Create a custom app page and assign it to the mobile menu and B. Include Today as a navigation item in the app.

Salesforce supports creating a mobile app page with Lightning App Builder for the Salesforce mobile app. This allows an app builder to design a mobile-focused experience and make it available through mobile navigation.

Salesforce also provides Today in the mobile app to help users manage their day, prepare for meetings, and access relevant mobile productivity information. Salesforce documentation states that users access Today from the Salesforce mobile app navigation menu, and admins can add Today to Lightning app navigation and the Mobile Only app.

C is not the best verified exam answer for the standard version of this question. While mobile navigation can be customized, the stronger Platform App Builder mobile UX recommendations here are adding a custom mobile app page and adding Today as a navigation item.

===========

The correct solution is to configure validation rules with help text/error messaging.

Validation rules are the right tool because they evaluate record data before save and stop the save when the record does not meet the defined conditions. They can enforce that a Case status is not changed back to an earlier value by using formula logic such as PRIORVALUE() and picklist checks. They can also require certain fields only when specific Case criteria are met by checking whether those fields are blank under those conditions.

Why the other options are wrong:

Dependent picklists control valid picklist values, but they do not enforce status progression or conditional required fields across all save paths. Approval processes are not the best fit for real-time save validation. Page layout required fields are UI-level requirements and are not flexible enough for criteria-based enforcement.

The correct solution is component visibility with advanced filters. Lightning App Builder allows components on Lightning pages to be shown or hidden dynamically based on filter criteria. Salesforce Admin guidance also explains that App Builder filters can customize which components display on record pages and can use field values from related records, running user, and permissions.

Because the component must display dynamically based on criteria about the related Contact, the app builder should use an advanced visibility filter using the Contact field criteria.

Why not others:

A. Related Record component displays related record data but does not solve dynamic visibility by itself.

B. Hiding behind a tab does not dynamically control visibility.

C. Custom permission controls visibility by user permission, not by related Contact field criteria.

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.

===========

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

===========

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.

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

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 B. Edit a record page using Lightning App Builder > Drag the component onto the page.

A custom Lightning component installed from AppExchange is configured on a Lightning record page through Lightning App Builder. Salesforce documentation states that Lightning App Builder supports custom Lightning components, including Aura and Lightning web components, and record pages are edited as Lightning pages.

The Page Layout editor is used for fields, buttons, related lists, and layout behavior, not for placing Lightning components on a Lightning record page. App Manager manages apps and utility bars, but the page canvas configuration is done in Lightning App Builder.

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.

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

AW Computing wants to grant access to all users in the Service Manager role for Opportunities of type Service Agreement in a private sharing model.

Criteria-based sharing rules allow sharing records automatically based on field values (e.g., Type = Service Agreement) to roles, public groups, or users.

Salesforce documentation confirms that when the org-wide default is private, sharing rules are the declarative way to grant access to specific users based on criteria. (Salesforce Help)

Owner-based sharing rules share based on the record owner, not a field criterion.

Apex sharing rules are needed only if declarative sharing is insufficient.

Manual sharing requires user action and is not scalable.

===========

The correct answer is A. Highlights panel.

In Lightning Experience, record actions such as New Task appear in the Highlights Panel area of the Lightning record page. Salesforce documentation explains that the actions in the highlights panel come from the object’s page layout, specifically the Salesforce Mobile and Lightning Experience Actions section, unless dynamic actions are enabled.

Since the custom action was already added to the Mobile & Lightning Actions section on the page layouts, the app builder must add the Highlights Panel component to display those actions on the Lightning record page.

Activities shows activity timeline/composer-related functionality, but it is not where page-layout actions are generally displayed. Related Lists and Related Record do not display the main action bar.

===========

The intended answer is D , because the validation must check two error conditions before allowing the Opportunity to be saved as Closed Won :

Scheduled_Ship_Date__c is blank.

Scheduled_Ship_Date__c is more than 14 days after CloseDate .

Salesforce validation rules fire when the formula evaluates to True . Salesforce’s formula documentation confirms that ISPICKVAL(picklist_field, text_literal) is the correct syntax for comparing a picklist field such as StageName . Salesforce validation examples also show date arithmetic such as subtracting one date from another to check whether a date exceeds a required range.

The option text appears corrupted, but the correct exam concept is a validation rule that blocks Closed Won if the Scheduled Ship Date is blank or more than 14 days after the Close Date.

===========

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.

===========

Text Area (Rich), commonly called a Rich Text Area field, is the appropriate Salesforce field type when users need formatted content rather than plain text. Salesforce ' s rich text editor supports formatting such as bold and italics, numbered and bulleted lists, hyperlinks, alignment, indentation, and embedded images. This makes it suitable for white-paper-style material containing structured text, lists, links, and graphics. A standard Text Area provides only limited plain-text content. Text Area (Long) increases the amount of text that can be stored but does not provide the rich formatting and image capabilities required here. An encrypted text area is intended to protect sensitive information and is unrelated to formatted document presentation. Therefore, Rich Text Area is the correct declarative field type.

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

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

This requirement is a many-to-many relationship: one Contact can relate to many Solar Projects, and one Solar Project can relate to many Contacts. Salesforce models this with a junction object, which is a custom object with two master-detail relationships.

A simple lookup on one object would not properly support the many-to-many data model.

===========

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 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 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 answer is B. Cross-object formula.

Opportunity has a standard relationship to Account, so an app builder can create a formula field on Opportunity that references the parent Account field. Salesforce defines a cross-object formula as a formula that spans related objects and references fields on those related objects.

Because Account_Region__c is a picklist on Account, the Opportunity formula would commonly be a text formula like:

TEXT(Account.Account_Region__c)

Field history tracking only tracks changes, a lookup field would create a relationship rather than display the Account field value, and field-level security controls visibility but does not copy or display the parent field on Opportunity.

===========

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.

===========