Salesforce Platform-App-Builder Dumps

The correct answer is B. Data Import Wizard.

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

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

===========

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 C. Enhanced List.

Salesforce documentation states that the Enhanced List related list type shows up to 10 fields and allows users to resize columns, sort columns, perform mass actions, and wrap text. This exactly matches the requirement: users need to see ten fields and need the ability to sort and wrap text on related lists.

D. Basic List is incorrect because the Basic List type shows fewer fields and does not provide the enhanced related-list behavior required here. A. List View and B. List Class are not the correct Related List Lightning component type for this requirement.

===========

The correct answer is D. Flow.

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

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

C. Quick action is manual, not automatic.

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

===========

A Record-Triggered Flow is the best tool because the automation must run automatically when a client is won. Salesforce Trailhead explains that record-triggered flows run when a record is created, updated, or deleted, and can update records, send notifications, create related records, call actions, and handle criteria-based logic.

Here, the flow can:

Detect when the client is won.

Send an email notification to the finance manager.

Use a decision element to check whether the client is top-tier.

Create an onboarding task for the sales manager only when the client is not top-tier.

Why not others:

A. Approval Process is for approval routing, not general client-won automation.

C. Apex is unnecessary because Flow can meet the requirement declaratively.

D. Screen Flow requires user interaction, but this must happen automatically.

===========

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.

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

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

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

Global actions are designed to be available broadly, not only from one object’s record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.

This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.

Why others are incorrect:

A is incorrect because a global action layout does not automatically clone the default page layout.

B is incorrect because the Lightning Component Library is not the reason to use global actions.

C is incorrect because global actions are not record-specific; object-specific actions are record-specific.

===========

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.

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.

===========

Lightning App Builder supports visibility rules based on Device/Form Factor , allowing components to appear specifically on desktop or phone experiences. This lets the app builder streamline the mobile record page by displaying only the components and information mobile sales reps actually require while leaving the desktop experience unchanged. Salesforce explicitly documents that a visibility filter using the Device context can restrict a component to a particular experience, such as phone or desktop. Reordering all fields would modify the experience broadly without providing device-specific optimization. Disabling the phone assignment would remove the page from the required mobile experience rather than improve it. Better training documentation also cannot solve excessive UI complexity. Therefore, device-based visibility using Form Factor provides the required declarative, low-impact solution. Salesforce

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

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.

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

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.

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

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.

===========

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. Configure Campaign Interactions and Campaign statistics.

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

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

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

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

The correct answer is 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 solution is to add a Rich Text component to the Case Lightning record page and then use component visibility so it only appears when the related Account’s support level is Platinum.

Salesforce Lightning App Builder supports visibility rules that show or hide components based on field criteria. Salesforce documentation confirms that visibility filters on record pages rely on field data associated with the page’s object, and related lookup fields can be used in visibility-rule considerations.

This is the best declarative solution because the requirement is only to display a text notification. A custom Lightning Web Component or cloned Lightning page is unnecessary.

Why others are incorrect:

A is incorrect because assigning a Case page to “platinum accounts” is not the correct assignment model.

C and D are incorrect because custom Lightning Web Components add unnecessary development effort for a simple text notification.

===========

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 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 validation belongs on the Opportunity Product because the discount being restricted is a value associated with each individual product line. A validation rule evaluates the record being saved and prevents the transaction when its formula evaluates to TRUE. Therefore, the rule can evaluate the Opportunity Product discount and generate an error whenever it exceeds 15%. Putting the validation on Opportunity would target the parent record rather than the specific line item where the invalid value occurs. An approval process is unnecessary because the requirement is to prevent the save, not route an exception for managerial approval. A Big Deal Alert applies to large Opportunities and is unrelated to product-level discount enforcement. Salesforce recommends validation rules for enforcing record-level business data requirements before save.

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

The correct answer is C. Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field.

A roll-up summary field is the recommended declarative solution when Salesforce needs to summarize child-record data on a parent record. Salesforce documentation states that roll-up summary fields calculate values from related records and are defined on the master side of a master-detail relationship.

In this scenario, Opportunity is the parent and Detailed_Sales__c is the child. The roll-up summary field can summarize sales metrics and use filter criteria so only child records where Status = Active are included.

Why others are incorrect:

A is incorrect because a third-party AppExchange app is unnecessary when native roll-up summary functionality meets the requirement.

B is incorrect because Apex is not recommended when a declarative feature can solve the requirement.

D is incorrect because lookup relationships do not support standard roll-up summary fields. Salesforce documentation states that lookup relationships are similar to master-detail relationships, except they do not support roll-up summary fields.

===========

The correct answer is D. Component visibility filter.

In Lightning App Builder, component visibility rules can control whether a component appears based on context, including the device/form factor. Salesforce Trailhead specifically describes creating a visibility rule so a component appears only when the page is viewed on a phone, which matches restricting a Lightning component to mobile users.

A is incorrect because form factor settings are generally used for page/device availability or preview behavior, not the best feature for hiding or showing one specific component on a single Lightning record page.

B and C are incorrect because the Highlights Panel and Related List Quick Links are page components, not conditional visibility tools.

===========

Schema Builder can create custom objects, relationship fields, formula fields, and normal fields, but a key limitation is that fields created through Schema Builder are not automatically added to the object’s page layout. The app builder must go to the page layout separately and place the fields where users need to see them. Salesforce Trailhead confirms Schema Builder supports relationship fields, formula fields, and normal fields, so option B is incorrect. Salesforce Help also notes that fields added through Schema Builder are not automatically added to the page layout.

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.

===========

Executing Get Records inside a Loop generates another SOQL query for every iteration. In bulk processing, that pattern can quickly exceed Salesforce ' s per-transaction SOQL governor limit. Salesforce explicitly documents that a Flow retrieving records from inside a Loop can consume one SOQL query per iteration and fail after exceeding the transaction limit. The correct bulkification pattern is to retrieve the needed records once outside the Loop, store them in a collection, and then iterate over the already-retrieved data. Changing from after-save to before-save does not eliminate repeated queries. A Fault Path can handle an error but does not prevent the governor limit from being reached. Replacing the Loop with Assignment is not appropriate when multiple items still require iteration. Moving Get Records outside the Loop resolves the root architectural problem. Salesforce

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

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

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

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

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

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

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

===========

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.

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

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. There are already two master-detail relationships on the Invoice Line Item and C. Invoice Line Item records exist without having the Invoice lookup field populated.

Salesforce allows a lookup relationship to be converted to a master-detail relationship only when the lookup field has a value on all existing records. Therefore, if any Invoice_Line_Item__c records do not have the Invoice lookup populated, Salesforce prevents the conversion.

Salesforce also limits each custom object to up to two master-detail relationships. If Invoice Line Item already has two master-detail relationships, it cannot have another master-detail relationship added or converted.

B is incorrect because custom objects can be on the detail side of master-detail relationships. D is incorrect because a roll-up summary field on Invoice is not the reason this lookup-to-master-detail conversion would be blocked.

===========

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 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 correct answer is B. Actions & Recommendations component.

The Actions & Recommendations component is used to give agents a guided to-do list/checklist on a record page. Salesforce documentation describes it as a component that can show flows, quick actions, and recommendations so agents can complete required steps consistently. This matches the requirement to provide service agents with checklist items when servicing a Case.

Why others are incorrect:

A “Business component” is not the standard Salesforce feature for this.

Activity Timeline shows activities, not a required checklist.

Highlights Panel shows key fields and actions, not guided service steps.

===========

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

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

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

So, based on your option wording:

B appears to mean Roles and Subordinates.

C is Public Groups.

D appears to mean Users / Individual Users.

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

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

===========

The correct answer is A. Schema Builder.

Schema Builder lets an app builder quickly create and view custom objects, fields, and relationships from one visual interface. Salesforce Trailhead states that Schema Builder is used to visualize and edit the data model, including objects, fields, and relationships.

Lightning Object Creator is mainly used to create objects and fields from a spreadsheet. Manage Field Permissions controls access, not object creation. Developer Console is not the recommended point-and-click tool for this requirement.

===========

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

===========

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 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 answer is A. Record-triggered flow.

The app builder needs automation to run when a child record is deleted and then update a field on the related parent record. Salesforce states that a record-triggered flow can automatically perform actions when a record is created, updated, or deleted, without user interaction.

Autolaunched flow can perform logic, but it does not run automatically on record deletion unless invoked by another automation. Validation rule only prevents invalid data entry. Quick action requires user interaction and is not suitable for automatic updates after deletion.

===========

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.

===========

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. Deselect auto add to custom report type.

When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.

Why the other options are incorrect:

Removing the field from page layouts only affects record-page visibility, not report type availability.

Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.

===========

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.

===========

Dynamic Forms allows an app builder to place individual fields and Field Sections directly on Lightning record pages and apply visibility rules to them. Salesforce documents that field visibility can respond dynamically to record field values, allowing fields to appear or disappear as users modify data. This produces a more contextual record experience without maintaining numerous page layouts. Multiple page layouts are generally tied to profiles and record types rather than reacting dynamically to field input. A Filtered Related List controls related records, not the visibility of primary record fields. Screen Flows provide guided interaction but are unnecessary when the requirement concerns dynamic presentation of normal record-page fields. Therefore, Dynamic Forms combined with visibility rules provides the most direct declarative solution for adapting record pages according to field values. Salesforce

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

The correct answer is D.

Managers need to create child Accounts directly from a parent Account and auto-populate fields from that parent record. This is an object-specific custom action use case. Salesforce Trailhead states that object-specific actions can create records that have automatic relationships to other records and provide a streamlined experience across desktop and mobile. Salesforce also documents that predefined field values can be used with quick actions to set field values automatically, improving consistency and speed.

A. Global Quick Action is not ideal because it does not run in the specific parent Account context. B. Path does not create child records. C. Custom link is not the recommended Lightning approach for creating related records with predefined values.

===========

The correct answer is A. Path.

Sales managers want reps to see recommendations, sales strategies, and key fields at each step of the Opportunity sales process. Salesforce Path is designed for exactly this. Path can highlight key fields and provide customized Guidance for Success for each stage of a process.

For Opportunities, Path can show reps which fields matter at each sales stage and provide stage-specific guidance such as qualification tips, sales strategy, or next-step recommendations.

C. Approval Process is for record approval routing.

D. Global Action is for creating or updating records quickly, not guiding users through sales stages.

B is not the correct Salesforce feature for this requirement.

===========

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 tool is Data Loader.

Cloud Kicks needs to insert over 1 million net new Account records. Salesforce Data Loader is the correct tool for large-volume imports because it supports bulk insert, update, delete, and export operations. Salesforce’s Data Loader documentation describes it as a client application for bulk data import and export, including inserting Salesforce records. Salesforce also distinguishes it from the Data Import Wizard, which is limited to smaller imports.

Why the other options are wrong:

Data Import Wizard is not suitable for over 1 million records because it is intended for much smaller imports. Schema Builder is for viewing and creating data model components, not loading a million records. Lightning Object Creator creates objects from spreadsheets, not mass-inserting large Account datasets into an existing model.

The correct answers are C. External objects and D. Big objects.

External objects are suitable because they represent data stored outside Salesforce while still being accessible in Salesforce. Salesforce documentation explains that external objects behave similarly to custom objects, but the record data is stored outside the Salesforce org. External objects can also participate in lookup-style relationships, including external and indirect lookup relationships, and Salesforce Connect supports reports that include external objects.

Big objects are also suitable for archiving very large volumes of historical data on the Salesforce platform. Salesforce describes big objects as a way to store and manage massive amounts of data, including archived data from other objects. Big objects support querying through SOQL/API patterns, and Salesforce documentation also covers viewing big object data in reports and dashboards, commonly by using a working dataset for reportable subsets.

A is incorrect because “related objects” does not reduce Salesforce data storage.

B is incorrect because moving data into custom objects still consumes Salesforce data storage, so it does not solve the storage-limit issue.

===========

Inspection__c must be the detail object and Building__c the master. Salesforce master-detail relationships create strong dependency between parent and child records: when a master record is deleted, its related detail records are cascade-deleted. Detail records also inherit record access from the master through the Controlled by Parent sharing model. Salesforce additionally specifies that the master-detail relationship field is created on the detail object. Therefore, the relationship field belongs on Inspection__c and references Building__c . A lookup relationship would leave Inspection records independently owned and would not provide the required cascade-delete and inherited-sharing behavior. Option B reverses the relationship direction and would incorrectly make Building the detail. Thus, D satisfies both lifecycle dependency and security inheritance requirements with the standard declarative Salesforce data model.

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

A scheduled path on an after-save record-triggered flow is specifically intended to execute automation at a dynamically calculated time after an individual record-triggering event. The flow should trigger when Project__c.Status transitions to On Hold and schedule the email seven days after that update. Salesforce states that scheduled paths are available for record-triggered flows optimized for Actions and Related Records and can use “When Record Is Created or Updated” as their time source. Using CreatedDate would calculate the delay from record creation rather than when the project became On Hold. A daily schedule-triggered flow could poll records, but it is less precise and unnecessary when Salesforce can queue a per-record scheduled action directly. Thus, C matches the required independent seven-day timer.

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

Current Salesforce documentation makes C the correct answer. Salesforce Help states that to enforce validation rules during Lead conversion, the Require Validation for Converted Leads setting must be enabled under Lead Settings. If it is disabled, validation automation that would otherwise protect the resulting Account, Contact, or Opportunity can be bypassed during conversion. Therefore, missing information on Accounts created through Lead conversion indicates that this Lead setting has not been enabled.

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

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

===========

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.

===========

The correct answers are A. Review the Contact record and ensure it is linked to an Account, C. Verify the users with the issue have access to the Contact object, and E. Confirm whether Default Organization-Wide Sharing Settings provide access to the Account.

A Contact that is not linked to an Account is treated as a private contact. Salesforce states that contacts without an account are private regardless of the sharing model, so checking whether the Contact is associated with an Account is a valid troubleshooting step.

Users also need object-level access to the Contact object. Object permissions control whether users have base-level access such as read, create, edit, and delete for an object.

Finally, Contact visibility is often affected by Account access, especially when Contact sharing is controlled by the parent Account. Organization-Wide Defaults define the default record access users have for records they do not own, so checking the Account OWD is also correct.

B is incorrect because creating a new Contact does not troubleshoot the actual sharing/security issue.

D is incorrect because creating a broad Account Sharing Rule for all records is not the first troubleshooting step and may overexpose data.

===========

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

===========

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 D. Partial Copy sandbox.

A Partial Copy sandbox is designed for testing and UAT when users need a subset of production data. Salesforce states that Partial Copy sandboxes include metadata plus a subset of production data via sandbox template, support 5 GB data storage, and have a 5-day refresh interval, which satisfies a weekly refresh requirement.

A. Full sandbox is incorrect because it copies all production data and has a longer refresh interval.

B/C. Developer or Developer Pro are incorrect because they do not copy production data through a template in the same way required for this UAT scenario.

========

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

Salesforce geolocation fields are used to identify locations using latitude and longitude and can support distance calculations.

Because Universal Containers delivers containers to remote construction sites and customers provide crossroads or location markers, the app builder should use a Geolocation field to capture location-based information rather than a number, reference, or external lookup field.

Why others are incorrect:

A. Number stores numeric values only.

C. Reference is not the correct field type for capturing physical location.

D. External Lookup is used to relate Salesforce records to external object records, not to store site location details.

===========

The Full Copy sandbox is acting as Universal Containers ' final regression and staging environment. It should therefore be refreshed after a major release reaches production so the environment again represents the current production baseline before development for the next release cycle proceeds. Salesforce states that refreshing a sandbox replaces it with a current copy of its source production organization, updating metadata and, for Full sandboxes, production data. Salesforce ' s current sandbox strategy guidance also recommends refreshing staging and deployment sandboxes after production upgrades to keep environments aligned. Refreshing after every Partial Copy deployment would unnecessarily destroy the staging environment ' s current testing work, while adding a single production user does not justify a Full sandbox refresh. Refreshing only after UAT also occurs too late in the stated lifecycle. Salesforce

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

The Custom Error element allows a record-triggered flow to prevent the triggering database change and present a targeted error directly to the user. Salesforce supports displaying the message either at the record-page level or as an inline error on a specific field, which exactly meets the requirement to place the error on the Opportunity Stage field. When the Custom Error element executes, Salesforce rolls back the record change until the user corrects the problem. A Screen element is not valid for providing this experience inside a background record-triggered flow. An Assignment on a fault path merely stores values and does not automatically surface a validation-style error. Ending the flow also does not prevent the record from being saved. Therefore, the Custom Error element is the correct declarative equivalent to validation-style feedback. Salesforce

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

Change sets can be exchanged only between deployment-connected organizations, such as a production org and its own sandboxes. UMS Logistics is a separate production organization and has no deployment relationship with the UMS source environment, so an outbound change set cannot be sent there. Salesforce documents unmanaged packages as a mechanism for packaging metadata components in a source org, uploading the package, obtaining an installation URL, and installing those components into another Salesforce organization. A managed package is intended primarily for distributed applications requiring namespace and provider-controlled versioning, such as commercial AppExchange solutions, and is unnecessary for this evaluation transfer. A sandbox likewise cannot be refreshed from an unrelated organization ' s Developer sandbox. Therefore, the appropriate deployment vehicle is an unmanaged package installed through its generated URL.

Salesforce imposes a daily limit on mass and list email sent to external recipients. Current Salesforce documentation specifies a limit of 5,000 external email addresses per day per licensed org , meaning a recurring campaign to 7,000 contacts cannot be completed using standard Salesforce mass-email functionality in one day. Salesforce recommends considering a third-party mass-email solution from its marketplace when higher-volume sending is required. This corresponds to option B in the question. Requesting an arbitrary increase does not remove the standard product limitation. Exporting contacts to an external email client creates additional data-management and compliance concerns, while developing Apex and an LWC does not bypass Salesforce ' s applicable email limits. A purpose-built marketplace solution is therefore the appropriate scalable approach. Salesforce

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

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.

===========

A lookup relationship is required because the Time Entry records must retain independent ownership and a sharing model that is more restrictive than the related Project records. In a master-detail relationship, the detail record ' s ownership and access are controlled by its master. Salesforce states that custom objects on the detail side lose their independent Owner field, and record access can be Controlled by Parent. That would conflict with the requirement for Time_Entry__c to remain Private even though Project__c is Public Read/Write. A lookup relationship keeps the records related while allowing Time_Entry__c to maintain its own owner and organization-wide default. A hierarchical relationship is specific to the User object, while an external lookup relationship is intended for relationships involving external objects.

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.

===========

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

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

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

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

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

===========

The correct 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 D.

Validation rules are the right declarative tool to enforce data compliance before a record is saved. They can prevent a Case from moving backward to an earlier Status and can require specific fields when Case criteria are met. Salesforce formula functions such as ISCHANGED() compare whether a field value changed, and validation rules can use formula logic to stop invalid saves.

Why others are incorrect:

Approval Process is for routing records for approval.

Dependent picklists control picklist value availability, not status regression.

Case Flow can automate case processes, but validation rules are the best tool for enforcing save-time compliance.

===========

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

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

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

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

C is incorrect because CASE() itself is allowed.

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

===========

The best option is a managed package from AppExchange.

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

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

===========

The correct answers are A. Roll-up summaries are limited to master-detail relationships and C. An object can have 25 roll-up summaries.

Roll-up summary fields summarize data from related child records onto the parent record, but standard Salesforce roll-up summaries are available only when the child records are directly related through a master-detail relationship. In this scenario, only one of the three custom objects has a master-detail relationship to Account, so native roll-up summaries cannot be used for the other two lookup/non-master-detail objects.

Salesforce also lists 25 roll-up summary fields per object as the standard allocation, so summarizing 15 fields from three objects would require 45 summaries, which exceeds the normal Account object limit.

B is incorrect because native roll-up summary calculations support COUNT, SUM, MIN, and MAX, not AVG.

D is incorrect because “20 object references” is not the key roll-up summary consideration in this proposal.

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

To show Chatter on a custom object Lightning record page, the app builder should use the standard Chatter Feed / Chatter component in Lightning App Builder. Salesforce documentation describes adding Chatter components such as Chatter Feed, Chatter Publisher, and Chatter to Lightning record pages, usually after feed tracking is enabled for the object.

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

C and D are incorrect because a custom component or AppExchange component is not required for standard Chatter feed functionality.

===========

A managed package provides important intellectual-property protection when an application is distributed to other Salesforce organizations. Salesforce ' s packaging documentation states that Apex classes and triggers contained in a managed package are obfuscated and cannot normally be viewed in the installing subscriber organization, apart from exposed global method signatures and specific support-access scenarios. Managed packages are therefore the appropriate model when a publisher wants to distribute an application while protecting proprietary Apex implementation details. A package does not need to be sold on a per-user basis simply because it is managed; free managed packages can be distributed. Unmanaged packages expose components for subscriber modification and aren ' t designed to provide the same provider-controlled upgrade and IP-protection model. Therefore, A is the relevant consideration for publishing this application. Developer

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

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.

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

A record-triggered flow can contain both its immediate execution path and one or more Scheduled Paths . The immediate path can create the welcome Task as soon as the Employee record is created. A Scheduled Path can then be configured relative to the Employee ' s Start Date to execute five days beforehand. At that time, the flow can determine whether Onboarding Status remains Pending and send the reminder email when appropriate. Salesforce explicitly states that Scheduled Paths run part of a record-triggered flow at a dynamically scheduled time and can use a date field on the triggering record as the time source. A schedule-triggered flow would poll records on a general schedule rather than establish a per-Employee timeline. Screen Flow Pause and an asynchronous path inside a Loop do not match the requirement.

The correct answer is A. Account Object .

Roll-up summary fields are created on the parent object , because the summary value is displayed on the parent record. Here, the KPI values need to appear for each Account , and they summarize related Opportunity records. Therefore, the app builder should go to the Account object in Object Manager and create roll-up summary fields there.

For this requirement, the app builder would create separate roll-up summary fields on Account, such as:

Count of open Opportunities

Count of won Opportunities

Salesforce documentation describes roll-up summary fields as fields that calculate values from related records, such as records in a related list.

C. Opportunity Object is incorrect because Opportunity is the child/related record being counted.

D. Lightning App Builder is incorrect because Lightning App Builder controls page layout/components, not the creation of roll-up fields.

B. Lightning Object Creator is used to create objects from spreadsheets, not build rollups.

===========

The correct answer is B. Field-level security.

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

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

===========

The correct answer is D.

Universal Containers wants the Account Region value to appear on related Contact records and stay in sync whenever the Account value changes. A cross-object formula field on Contact is the best declarative solution because it dynamically references the parent Account field. Salesforce Trailhead explains that a cross-object formula can pull information from a parent object through a lookup relationship, such as showing Account information on Contact.

Because Account Region is a picklist, the formula must convert the picklist value to text using the TEXT() function. Trailhead gives the same pattern with Account Industry on Contact: TEXT(Account.Industry) .

B is incorrect because ISPICKVAL() checks whether a picklist equals a specific text value and returns true/false; it does not display the picklist value.

A and C are incorrect because creating a copied field and trying to update it through a relationship is unnecessary when a formula field can stay synchronized automatically.

===========

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.

===========

Queues are represented through Salesforce Group records, and their stable programmatic identifier is the DeveloperName , or API name. A flow that determines a regional queue dynamically can first calculate the appropriate queue API name in a text or formula resource and then use Get Records against the Group object, filtering DeveloperName to that value and Type to Queue. Salesforce ' s current Flow guidance provides this exact architecture for dynamically resolving queues rather than hard-coding IDs. Hard-coded user or queue IDs are brittle across environments and conflict with the dynamic-routing requirement. An asynchronous path changes execution timing but does not resolve the assignee. A custom Task text field likewise does not establish an actual queue assignment. Therefore, the formula-resource plus Get Records pattern is the correct declarative solution.

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

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

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

Why others are incorrect:

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

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

===========

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

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

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

===========

The correct place to verify whether a change set can be deployed is Inbound Change Sets in the target org, normally Production.

Salesforce guidance says that after uploading a change set from the source sandbox, the app builder goes to Setup → Inbound Change Sets, opens the change set awaiting deployment, and clicks Validate. Validation checks whether the deployment succeeds or fails before committing the changes.

A. Deployment Settings is mainly used to authorize deployment connections and allow inbound changes from another org. C. Deployment Status is used to monitor deployment progress/results, not to initiate validation of an inbound change set.

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 answers are A. Recent items, B. Filter list/List View, and C. Rich text.

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

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

===========

The correct answer is 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 correct answer is D. Unable to reference the child records.

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

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

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

===========

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

===========

The correct answer is C. Data Export Service.

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

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

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

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

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

===========

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

===========