Salesforce Platform-App-Builder Dumps

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. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory related list to the Asset page layout.

To show Asset Inventory records as a related list on Asset, the child object must contain the relationship field pointing to the parent object. In this scenario, Asset Inventory is the child/detail-style object, and Asset is the parent record where the related list should appear.

Salesforce relationship fields connect records between objects, and related lists can then be added to the parent object’s page layout. Salesforce documentation for related lists confirms that related lists are managed from the object’s page layout.

Why others are incorrect:

B is incorrect because a roll-up field does not create the relationship or related list.

C is incorrect because the relationship direction is wrong; the relationship field should be created on Asset Inventory, not on Asset.

D is incorrect because a junction object is only needed for many-to-many relationships. Here, Asset Inventory records simply need to relate to Asset records.

===========

The correct answer is A because the rule must fire only when Sales Organization = Canada and Pricing Tier is blank.

ISPICKVAL() checks whether a picklist equals a specific text value, and TEXT() converts a picklist value into text so ISBLANK() can evaluate whether it is empty. Salesforce documents ISPICKVAL() for comparing picklist values and TEXT() for converting picklist values in formulas.

Why others are incorrect:

B has invalid formula structure.

C uses incorrect picklist blank logic.

D uses OR , which would require Pricing Tier even when Sales Organization is not Canada.

===========

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 answer is D. Choose an unmanaged package from AppExchange that closely meets the requirements of the project and allows programmatic development.

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

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

The correct answer is A. Import Wizard.

Cloud Kicks needs to insert 25,000 records and use deduplication for a custom object. Salesforce Trailhead states that the Data Import Wizard can import data into custom objects and supports up to 50,000 records at a time, so 25,000 records fits within the Import Wizard limit.

Salesforce Help also states that the Data Import Wizard prevents duplicate custom object records by matching records against fields such as the custom object name or Salesforce ID.

B. Data Loader is not the best answer because Data Loader is better for larger or automated loads, but this question specifically requires deduplication and only 25,000 records. C. Lightning Object Creator creates objects from spreadsheets; it is not the correct deduplication import tool. D. Schema Builder is for creating and viewing data models, not importing records.

===========

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.

===========

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 answers are A. Change the Lead Duplicate Rule details to Bypass Sharing Rules and D. Change the Lead Duplicate actions to Block on Create.

Because Lead OWD is Private, users may not have access to existing duplicate Lead records. Salesforce duplicate rules can be configured to bypass sharing rules, allowing the duplicate rule to check possible duplicates regardless of ownership or user visibility. Salesforce Help specifically explains duplicate prevention can block users from creating duplicate records whether or not they have access to the existing record.

D is also required because detecting a duplicate is not enough. The duplicate rule action must be set to Block on Create to stop users from saving new duplicate Leads.

Why others are incorrect:

B is incorrect because Lead Assignment Rules assign leads; they do not prevent duplicate creation.

C may expose more Lead records, but changing OWD from Private to Public Read is not the best security-safe solution when duplicate rules can bypass sharing.

===========

The correct answer is B.

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

Why others are incorrect:

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

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

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

===========

The correct answer is D. Flow.

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

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

===========

The correct answers are A. Public Groups, D. Roles and Subordinates, and E. Users.

For a custom object with Private sharing, manual sharing is used to open access to selected records on a case-by-case basis. Salesforce manual sharing allows individual records to be shared with users, public groups, and roles. Salesforce Classic manual sharing also lets the user select the type of group, user, role, or territory to add.

B. Private Groups is not the standard Platform App Builder answer here.

C. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

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.

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.

===========

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 C. Create a validation rule that uses the PRIORVALUE function.

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

Example logic:

Estimated_Hours__c > PRIORVALUE(Estimated_Hours__c)

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

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

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

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

===========

The correct answers are C. Lightning App Builder and D. Lightning components in Setup.

In Lightning App Builder, custom Lightning components that are configured for use in Lightning App Builder appear in the Lightning Components pane.

In Setup → Lightning Components, Salesforce allows admins to view a list of Lightning Web Components and Aura components in the org.

Why others are incorrect:

A. Visualforce components in Setup lists Visualforce custom components, not Lightning components.

B. Salesforce Optimizer App analyzes org configuration and recommendations; it is not the place to list available custom Lightning components.

===========

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. 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. Dynamic Actions and C. Approval Process.

An Approval Process is required because sales managers must provide formal sign off when an Opportunity discount meets the defined criteria. Salesforce approval processes define the criteria a record must meet, the steps required for approval, and who must approve it.

Dynamic Actions are also needed because Universal Containers wants the sign-off action available quickly from the Opportunity record page. Dynamic Actions let app builders control which actions appear on Lightning record pages based on conditions.

Why others are incorrect:

Schema Builder is for data model design, not approval/sign-off UI behavior.

Validation Rule can block invalid data, but it does not provide manager approval or sign-off.

===========

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.

===========

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

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

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

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

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

===========

The correct answer is B. The deployed permission set will only contain changes related to the change set.

When permission sets are included in change sets, the deployment carries permission settings related to the components included in the change set. The existing permission set in production is not completely overwritten as a whole object, and field-level security changes can be included when the relevant fields are part of the deployment. Salesforce documents permission sets and profile settings as access settings that can be included with change sets.

A is incorrect because the whole permission set is not simply wiped and replaced.

C is incorrect because field-level security can be deployed when included properly.

D is close in plain language, but the more accurate exam answer is that the deployed permission set contains only changes related to the change set.

===========

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

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

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

===========

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. 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 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 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 C. Submit the record for approval from an automated process.

The issue is not the approval process itself. The issue is that sales reps forget to manually submit the Opportunity. Salesforce supports submitting records for approval from automation, including Flow’s Submit for Approval action. Salesforce also documents using an after-save record-triggered flow to automatically submit records into an approval process.

A does not solve the problem because changing approval entry criteria does not automatically submit the record. B only reminds the manager and does not run the approval process. D is unrelated to automatic submission.

===========

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

For a Salesforce Classic-to-Lightning Experience migration, the app builder should look for prebuilt apps, components, adoption tools, and consultant solutions on AppExchange. Salesforce now refers to this marketplace as AgentExchange in newer Trailhead content, but the exam op tion “AppExchange” is still the intended answer. Salesforce describes it as the marketplace for Salesforce solutions, including apps, agents, components, and more, and specifically notes that admins can look there instead of building everything from scratch.

Flow Builder is for automation, Lightning Object Creator is for creating objects from spreadsheets, and Import Wizard is for importing data. They are not marketplaces for prebuilt adoption or migration resources.

===========

The correct answer is A.

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

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

Why others are incorrect:

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

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

===========

The correct answer is D. Accordion.

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

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

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

===========

A utility bar gives users quick access to commonly used productivity tools and components from within a Lightning app or console app. Salesforce describes the utility bar as a fixed footer that provides fast access to tools such as Notes, History, softphone, flows, and custom utilities. Utilities open in docked panels, allowing users to keep working without leaving the current page. This exactly matches the requirement: components accessible from anywhere in the app without leaving the page.

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

Why not others:

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

C. Dependent Picklist controls values based on another field.

D. Related Picklist is not the correct Salesforce feature.

===========

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

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

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

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

===========

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

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

===========

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 A. Create a child record, C. Update a related record, and D. Send an email alert.

Process Builder was designed to automate repetitive business actions. Salesforce documentation describes Process Builder as a tool for automating tasks, emails, and record updates.

Process Builder can improve productivity by performing actions such as:

Create a child record — Process Builder can create a record when criteria are met.

Update a related record — Process Builder can update the record that started the process or related records.

Send an email alert — Salesforce documentation specifically states that a process can send an email by using an email alert.

B is incorrect because “Start an additional message” is not a standard Process Builder productivity capability.

E is incorrect because Process Builder does not delete related records as a standard declarative action.

===========

The correct answers are C. My Domain must be deployed and D. The component is tagged for record pages instead of home pages.

Salesforce custom Lightning components must be properly configured before they appear in Lightning App Builder. Salesforce Trailhead explains that custom components configured for Lightning App Builder appear in the Lightning Components pane, and the component bundle must be compatible with Lightning App Builder and Lightning pages.

C is correct because Salesforce requires My Domain for adding custom Lightning components in Lightning Experience/App Builder scenarios. Salesforce Help notes that users cannot add a custom Lightning component without enabling and deploying My Domain.

D is correct because Lightning components must be exposed for the correct page type. A component exposed only for record pages will not appear for a Lightning Home page. Salesforce Developer documentation states that lightning__HomePage enables a component to be used on a Home page, while record-page-only configuration is separate.

Why others are incorrect:

A is incorrect because a custom tab is not required to add components to a Lightning Home page.

B is incorrect because “developer permission” is not the normal reason a downloaded component cannot be added to a Lightning Home page.

===========

The correct answer is A. Existing reports created under the Sun__c with Planet__c report type made by Salesforce will be unusable, but not deleted.

When a relationship is changed from master-detail to lookup, the available standard report types can change. Salesforce documentation notes that converting a lookup relationship to master-detail or vice versa can make existing custom reports unusable because of differences in available standard report types.

B is incorrect because roll-up summary fields are not automatically deleted from reports as part of the conversion. In fact, Salesforce states that a master-detail relationship cannot be converted to lookup while roll-up summary fields exist on the master object.

C is incorrect because roll-up summary fields do not remain and simply stop updating.

D is incorrect because the reports are not deleted; they become unusable.

===========

When deploying from a sandbox on a newer Salesforce version to production on a current version, any components that rely on features not yet available in production will fail.

Change sets do not automatically upgrade production.

All features must be supported in the target org at deployment time.

Salesforce documentation notes that compatibility issues may occur if components use version-specific features, and deployments must be tested against the target org’s current version. (Salesforce Help)

A is incorrect because deployments do not automatically wait for production upgrades.

B is partially true, but deployments are possible if features are supported.

C is incorrect; components are not automatically upgraded.

===========

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 must happen when a Contact is saved because the missing field is Region on the Contact record. Salesforce validation rules evaluate data before a record is saved and return an error when the formula evaluates to True.

The app builder can create a validation rule on Contact that checks the related Account’s Customer Status field and requires Region only when the Account is marked High Priority.

Example logic:

AND(

ISPICKVAL(Account.Customer_Status__c, " High Priority " ),

ISBLANK(Region__c)

)

Why others are incorrect:

A is wrong because the missing field is on Contact, not Account.

B is wrong because Customer Status being required does not require Contact Region.

D is wrong because it would require Region for all Contacts, not only High Priority Account Contacts.

===========

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

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

===========

The correct answer is B. Approval Process.

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

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

Why others are incorrect:

Slack message only sends communication.

Email alert only notifies someone.

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

===========

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

===========

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

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

===========

The correct answer is D. Roll-up summary field.

Cloud Kicks wants to display a count of related Opportunities on the Account record where the Opportunities are Closed Won and have a Close Date within the last year. A roll-up summary field is the correct declarative feature because it calculates values from related records, including counts, sums, minimums, and maximums. Salesforce documentation confirms that roll-up summary fields calculate values from related records and can display values on the parent record.

The app builder can create a roll-up summary field on Account with filter criteria such as:

Stage = Closed Won

Close Date = Last 365 Days / Last Year

Why others are incorrect:

Activity timeline displays activities, not Opportunity counts.

Formula field cannot count multiple child Opportunity records.

Validation rule blocks invalid saves; it does not calculate related record totals.

===========

The correct answer is C.

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

LEFT(Account.Zip_Code__c, 5)

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

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

===========

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.

===========

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.

===========

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

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

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

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

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

===========

The correct 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. 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 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 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 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 B. Master-detail relationship.

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

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

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

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

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

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

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

===========

The validation rule must fire when two things are true:

Job_Accepted__c is already populated

Hire_Date__c is being changed

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

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

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

Why others are incorrect:

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

===========

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 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 B. User will be presented with a “Record Lock” notification.

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

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

===========

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

===========

The correct answer is C. Flow.

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

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

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

The correct answer is B. Create a Chatter stream.

A Chatter stream gives users a combined feed from selected people, groups, and records. Salesforce documentation states that users can create a Chatter stream to get a combined view of feeds from selected profiles, groups, and records.

For this requirement, the sales rep can create a stream that includes only the key Account and Opportunity records, so their Chatter feed is filtered to those important records.

Why others are incorrect:

A. Chatter bookmarks save individual posts, but they do not create a filtered feed.

C. Chatter notification alerts users, but it does not filter the feed.

D. Chatter group is for group collaboration, not filtering posts from selected records.

===========

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

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

Enables roll-up summaries on Opportunity if needed.

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

B. Hierarchical is only available for User object.

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

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

===========

The correct answer is C. Record-triggered flow.

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

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

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

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

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

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

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

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

===========

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

===========