Salesforce Certified Platform Foundations

Correct answer: B. B. Edit the Opportunity Stage picklist value 'Design Review' in Setup and assign it the appropriate Forecast Category (e.g., 'Pipeline') so Opportunities at that stage are included in the forecast roll-up.

Every Opportunity Stage must be mapped to a Forecast Category, so editing the stage picklist value in Setup fixes the missing roll-up. Simply adding a stage does not auto-assign a category, which is why the default-inheritance option fails.

Correct answer: B. B. The Salesforce Field Service mobile app, which includes offline capabilities allowing technicians to view and update Work Orders, log service reports, and sync changes when connectivity is restored.

The Field Service mobile app is built for offline work orders and syncing when connectivity returns. The standard mobile app has only limited offline viewing, and Mobile Offline Briefcase is legacy, so those distractors don't fit field service workflows.

Correct answer: B. B. In the Salesforce App (mobile) settings in Setup, under 'App Manager' — the admin edits the mobile app's navigation items to include only the relevant objects.

App Manager in Setup is where an admin edits the Salesforce mobile app's navigation items, selecting exactly which objects appear. Profiles control permissions, not the mobile navigation menu, and Lightning App Builder builds pages rather than navigation.

Correct answer: B. B. Create one Product record per product and create three custom Price Books — one per segment — each with a separate Price Book Entry defining the segment-specific price.

Price Books with Price Book Entries are the native way to give one product different prices per segment. Duplicate product records and custom formula fields break reporting and bypass the pricing engine that opportunity line items rely on.

Correct answer: B. B. Create a Custom Report Type with Campaign__c as primary, Campaign_Participant__c as secondary (must have related contact), and Feedback__c as tertiary with 'may or may not have related record' to include participants without feedback.

A custom report type chains the objects and the 'may or may not have related records' setting keeps participants without feedback. Setting Feedback as required, like option D, would drop exactly the rows the requirement asks to keep.

Correct answer: B. B. Joined Report — the admin creates two blocks, one using a Campaigns-related report type and one using a Cases report type, both filtered by Account and sharing the Account grouping.

Joined reports let multiple blocks use different report types while sharing a common field like Account. A dashboard only shows two separate reports side by side, and matrix or single summary formats can't span Campaigns and Cases in one report.

Correct answer: B. B. The field was not added to the Custom Report Type's field layout — custom report types require fields to be explicitly added to the field layout before they appear in the report builder.

Custom report types expose only fields added to the report type's field layout, so the admin must edit layouts and check the field there. Field-level security hides values at runtime but the missing-layout issue is the classic cause for absent fields.

Correct answer: B. B. Use Salesforce CLI with source-based development and a version control system (e.g., Git) — each team works in a separate branch, merges to a shared branch, and resolves conflicts before deploying to the integration sandbox.

Source tracking with the Salesforce CLI plus Git branches gives each team isolation and explicit merge conflict resolution before integration. Sequential change sets and sandbox refreshes can silently overwrite work, and DevOps Center doesn't auto-merge features.

Correct answer: B. B. Refresh the QA sandbox from production to reset it to the current production state, then re-apply only the authorised QA-specific configurations.

Refreshing the Partial Copy sandbox from production resets it to a clean production baseline, then approved QA-specific config can be redeployed. Promoting the drift back to production with a change set would spread unreviewed changes rather than fix the divergence.

Correct answer: B. B. DevOps Center provides a Git-based, source-driven release pipeline with a visual UI inside Salesforce Setup — connecting to version control, tracking work items, and orchestrating deployments between pipeline stages.

DevOps Center delivers a Git-backed, source-driven deployment pipeline with a visual Setup UI, work item tracking, and stage-to-stage promotion. Change Sets remain the legacy option; DevOps Center complements sandboxes rather than replacing them, so option A fails.

Correct answer: B. B. Managed packages protect the publisher's intellectual property — Apex code and components are locked and cannot be viewed or modified by the installing org; unmanaged packages expose all code, which can be viewed and modified.

Managed packages lock Apex and components in a protected namespace so subscribers cannot view or modify the publisher's code, while unmanaged packages expose everything for editing. Exam cue: managed means protected IP and upgradeable; unmanaged means fully editable source.

Correct answer: A. A. Configure Email-to-Case (or On-Demand Email-to-Case), setting up a routing address that forwards emails from support@swiftsupport.com to Salesforce, which auto-creates Cases with the email content.

Email-to-Case, especially the on-demand version, is the native feature that converts inbound emails to Cases while capturing subject and body automatically. Web-to-Case handles web forms, not email intake, which is why option B is wrong.

Correct answer: B. B. Configure Salesforce Connect with an OData 4.0 External Data Source pointing to the banking API; create an External Object mapped to the balance data; add the External Object as a related list on the Account page.

Salesforce Connect with an OData 4.0 external data source and an external object surfaces external data in real time without replication, shown as a related list on Account. Option A stores copies nightly, which violates the no-storage requirement.

Correct answer: B. B. A Scheduled Flow configured to run weekly on Monday at 6 AM, using a Get Records element to query qualifying Leads and an Update Records element to change their status.

A Scheduled Flow running weekly on Monday at 6 AM with Get Records and Update Records elements directly meets the recurring batch requirement declaratively. Remember, record-triggered scheduled paths and time-dependent workflow actions fire per record at a fixed offset, not on a repeating weekly schedule.

Correct answer: B. B. A Scheduled Flow that runs daily at 8 AM, queries Opportunities meeting both criteria (closing ≤14 days, no activity in past 7 days), and sends a custom email to each Opportunity owner using a Send Email action.

A daily Scheduled Flow at 8 AM can query Opportunities meeting both criteria and send an email to each owner, fully declaratively. Scheduled paths and time-dependent workflow actions fire once per record at a fixed offset, so they cannot deliver repeating daily reminders.

Correct answer: B. B. Upload the term sheet to Salesforce Files, attach it to the Opportunity record's Files related list — Salesforce Files supports version control where uploading a new file as a new version preserves the history.

Salesforce Files attached to the record's Files related list supports versioning, so uploading a new version preserves the history and everyone with record access sees the latest. Chatter attachments offer no version history, and external drive links bypass Salesforce's sharing model.

Correct answer: B. B. Salesforce Privacy Center — the admin configures an Erasure policy in Privacy Center that, when executed for a specific individual, removes personal data fields from their records across related objects.

Salesforce Privacy Center lets admins configure an Erasure policy that removes an individual's personal data across related objects in a governed, auditable way. Encryption protects data at rest but is not deletion, and Data Loader is manual with no built-in compliance audit trail.

Correct answer: B. B. Use the Individual object and Data Use Purposes in Salesforce to record consent, linking each Contact or Lead to an Individual record that stores consent preferences.

The Individual object linked to a Contact or Lead, combined with Data Use Purposes, is the standard Salesforce model for capturing consent details and withdrawals. Custom checkbox fields lose history, and there is no single Setup toggle that logs consent events automatically.

Correct answer: B. B. Use Component Visibility filters in the Lightning App Builder on the LWC component, setting conditions for Stage equals 'Proposal' OR Stage equals 'Negotiation'.

Component visibility rules in Lightning App Builder let admins show a component only when record fields match conditions, no code changes required. JavaScript in connectedCallback violates the no-code constraint, and duplicate pages add needless maintenance.

Correct answer: A. A. Price Rules configured in CPQ that evaluate total quantity on the quote and apply a discount to all line items when the threshold is met.

Price rules can evaluate aggregate quote fields like total quantity and apply a discount across line items when a threshold is crossed. Discount schedules only tier discounts per individual product, so they fail the cross-product quantity requirement.

Correct answer: B. B. CPQ's Quote locking feature — once a quote enters 'Approved' status (through the CPQ Approval Process or standard Approval Process), CPQ can be configured to lock the quote, preventing any edits to line items.

CPQ's quote locking freezes the quote and its line items once the approval process marks it approved, preventing rep edits. Validation rules and read-only field security can be bypassed or affect other contexts, so the native lock is the intended control.

Correct answer: B. B. A Salesforce Data Entry Source in Journey Builder configured to monitor the Contact object in Salesforce CRM — when a new Contact is created and meets entry criteria, they enter the journey automatically.

The Salesforce Data Entry Source in Journey Builder uses Marketing Cloud Connect to inject contacts in real time the moment a new Contact is created and meets criteria. Automation Studio and report imports run on schedules, delaying journey entry by up to a day.

Correct answer: A. A. A Wait activity set to 7 days, followed by a Decision Split that evaluates a Contact attribute (e.g., Last_Workout_Date__c) to determine which path they take.

A Wait by Duration activity holds contacts until Day 7, then a Decision Split checks a synced field like Last_Workout_Date__c to route members down the SMS or normal path. An Engagement Split only measures email opens, not actual workout activity.

Correct answer: A. A. Use a Decision Split based on an engagement metric (e.g., email opens or a Salesforce data attribute like Workout_Count__c > 0) to route engaged members to the upsell email activity and non-engaged members to a Journey Exit activity.

A Decision Split on an engagement attribute routes engaged members to the upsell email activity and sends the rest to an exit, all in one journey. Path Optimizer is for testing variants, not deterministic rule-based branching on Day 14.

Correct answer: A. A. OWD: Private. Sharing Rule granting Sales read access to all Accounts. Permission Set granting Service 'View All' and 'Modify All' on Accounts.

Private OWD locks Finance to owned Accounts, a read-only sharing rule gives Sales visibility everywhere while ownership keeps edit rights, and View All plus Modify All covers Service. Public Read Only or Read/Write OWDs would expose every Account to Finance, breaking that requirement.

Correct answer: B. B. Salesforce re-runs all Apex tests in the production org during deployment; the 75% coverage threshold must be met based on the tests that run in production — sandbox coverage results are not transferred.

Deployments to production run Apex tests in the target org, and the 75% coverage threshold is recalculated from those production results. Sandbox coverage never transfers, so the 78% sandbox figure guarantees nothing regardless of the deployment tool.

Correct answer: C. C. A Permission Set with 'View All' on Portfolio__c assigned to every Compliance user.

A permission set with View All grants read access to every Portfolio record regardless of ownership, and it scales cleanly as new Compliance users are added. A sharing rule tied to ownership fails because it depends on who owns each record, while changing OWD violates the stated constraint.

Correct answer: B. B. Each Flow interview will issue a separate SOQL query and DML statement for the Account update; with 80,000 records, this approach risks exceeding SOQL and DML governor limits in bulk transactions.

Each flow interview issues its own SOQL query and DML statement against the Account, so a bulk load of 80,000 records risks exceeding governor limits. After-save flows can update parent records, and Flows do run during Bulk API loads, so those distractors state false limits.

Correct answer: B. B. Use a Batch Apex class that processes Orders in configurable batches (e.g., 200 records per batch), collecting Account and Service Plan data in aggregate before performing bulk DML updates.

Batch Apex processes Orders in configurable batches and aggregates Account and Service Plan updates into bulk DML, staying safely within governor limits. A scheduled flow in a single transaction would hit limits, and per-record before-save or event-driven processing is not bulkified.

Correct answer: A. A. Account (primary, must have), Contact (may or may not have), Opportunity (may or may not have), Opportunity Product (may or may not have related record).

Setting each child level to 'may or may not have' creates a left-outer-join effect, so Accounts without Contacts and Opportunities without Products still appear. Custom Report Types support up to four object levels, so the depth claim in the last option is simply false.

Correct answer: B. B. The admin must edit the Custom Report Type's Field Layout and manually add the new Opportunity field to the available fields section before it appears in the report builder.

New fields do not automatically appear; the admin must edit the Custom Report Type's layout properties and add the field to the available fields section. Exam cue: remember that Custom Report Types act as a field filter, unlike standard report types which reflect the schema automatically.

Correct answer: B. B. Standard Salesforce reports display a maximum of 2,000 rows on screen; however, the full dataset (up to 100,000 rows for export) is available when using the Export function directly — the admin should use the report export rather than copying from the screen view.

Salesforce reports display up to 2,000 rows on screen, but the Export function downloads the full dataset up to the export limit. Exam cue: the 2,000-row cap is a display limit, not an export limit, so switching file format or splitting the report is unnecessary.

Correct answer: C. C. Data Skew (specifically child record skew or lookup skew) — one parent has a disproportionately large number of child records, causing lock contention during DML and slow page loads on the parent record.

Data skew, specifically lookup or child record skew, occurs when one parent owns an enormous number of children, causing parent record lock contention and slow page loads. Ownership skew in option B involves record ownership, not parent-child volume, so it does not fit.

Correct answer: B. B. Enable a Custom Index on the AccountId field in the Order__c object through a Salesforce Support case — custom indexes improve SOQL query performance on high-cardinality fields.

A custom index, requested through Salesforce Support, lets selective SOQL filters on the lookup field avoid full-table scans over millions of records. LIMIT clauses only truncate results, and changing the relationship type violates the stated no data-model-change constraint.

Correct answer: A. A. 5 Cases, or 2 Chats and 1 Case, or 1 Call and 1 Case — but not 1 Call and 1 Chat simultaneously.

Five cases, two chats plus one case, and one call plus one case each total exactly five units, while a call plus a chat totals six and is blocked. Option B lists valid combinations but omits the five-case maximum, making A the only complete enumeration.

Correct answer: B. B. Omni-Channel automatically manages this — when an agent reaches maximum capacity, the system stops routing new work items to them regardless of their declared status; agents cannot manually override capacity enforcement.

Omni-Channel enforces capacity natively; once an agent reaches maximum capacity, routing stops regardless of the agent's declared status. Custom validation rules or flows on UserServicePresence are unsupported workarounds that risk conflicting with the routing engine.

Correct answer: B. B. A Price Rule in CPQ configured with a condition checking the Quote's Total Amount field and an action that sets a 15% discount on all Quote Line Items when the condition is met.

A Price Rule evaluates a condition on the quote total and takes an action that sets discounts on line items automatically. Product rules with alerts or validation rules only notify or block saves, so they cannot apply pricing without user intervention.

Correct answer: B. B. Data Cloud Identity Resolution uses configurable Match Rules (e.g., match on email OR loyalty ID OR name+address combination) and Reconciliation Rules to merge matched source records into a single Unified Individual.

Identity Resolution combines configurable match rules, like email or loyalty ID, with reconciliation rules to merge records from multiple sources into one Unified Individual. CRM duplicate rules only work within Salesforce and cannot unify disparate external system identities.

Correct answer: B. B. Data Cloud Segmentation — the admin builds a segment on the Unified Individual profile, adding a filter where a calculated attribute (Lifetime Spend, derived from aggregated transaction data from all sources) is greater than $10,000.

Data Cloud Segmentation on the Unified Individual profile with a calculated attribute is the native way to define a cross-source segment like Lifetime Spend over $10,000. A CRM report or Marketing Cloud SQL query cannot aggregate unified data the way Data Cloud segmentation does.

Correct answer: B. B. Data Cloud Activations — specifically a Real-Time API Activation or a webhook-based activation — can push segment membership updates to the hotel's room control system endpoint when a guest enters or exits the segment.

Data Cloud real-time API or webhook-based activations push segment membership changes to external endpoints as guests enter or exit a segment. A scheduled flow introduces polling latency, and Journey Builder or Platform Events add indirect layers that are not the native activation path.

Correct answer: B. B. A Record-Triggered Flow on Case that fires when Priority changes to 'High' and Status changes to 'Escalated', using a Create Records element to create a Work Order with the Case lookup populated.

A record-triggered Flow on Case can fire on the priority and status change, then use a Create Records element to build the Work Order with the Case lookup populated. Escalation rules mainly notify or reassign; they do not create related records cleanly.

Correct answer: B. B. Fundamentally different compliance requirements (GDPR vs HIPAA) with distinct data residency, retention, and access control obligations make a single org very complex to configure correctly and increases regulatory risk.

Conflicting regulations like GDPR and HIPAA impose distinct residency, retention, and access rules, making a single org hard to secure and risky. The 800-user limit is not a real Salesforce constraint, and change-set convenience never justifies an org strategy.

Correct answer: B. B. Salesforce Connect with a Cross-Org Adapter configured in Org A, creating External Objects that surface Org B's Account and Opportunity data directly in Org A without data duplication.

Salesforce Connect with the cross-org adapter surfaces Org B's Accounts and Opportunities as external objects inside Org A with no data duplication. SSO only shares login credentials, while Salesforce-to-Salesforce replicates records and creates sync and governance overhead.

Correct answer: B. B. Convert the Public Chatter Group used for case collaboration to a Private or Unlisted group, restricting membership to authorised users; reps should post case updates on the Case record feed rather than in a shared group.

Converting the public group to private or unlisted restricts who can see posts, and using the Case record feed ties visibility to record access. Feed tracking and field-level security do not control Chatter post visibility at all.

Correct answer: A. A. Enable Collaborative Forecasts in Setup — this allows reps to adjust forecast amounts and managers to see aggregated team forecasts including roll-ups by role hierarchy.

Collaborative Forecasts lets reps submit and adjust monthly forecast commits while managers see automatic roll-ups driven by the role hierarchy. Reports cannot capture commits, and Einstein Forecasting still requires the underlying forecast configuration to work.

Correct answer: B. B. Collaborative Forecasts distinguishes between the 'Owner Forecast' (manager-adjusted), 'Forecast Without Adjustments' (pure pipeline), and individual rep adjustments — managers can toggle between views to see both values.

Collaborative Forecasts shows both the unadjusted pipeline figure and the adjusted owner forecast, so managers can toggle between views. A distractor about a Forecast Adjustment Audit Trail invents a feature that does not auto-email differences to managers.

Correct answer: B. B. The integration org already has a newer active version of the same Flow (deployed by a previous run), and deploying an older version from source conflicts with the active version number; the admin must deactivate the current version or update the source's version number.

Only one Flow version can be active, so a newer active version in the target org blocks activating an older one; deactivate it or bump the source version. The missing-flag distractor confuses deployment activation with version conflicts.

Correct answer: B. B. Health Cloud's Care Team model — each patient (Person Account or Contact) has associated CareProgramTeamMember or CareTeamMember records linking providers with defined roles to the patient.

Health Cloud's native Care Team model links multiple providers to a patient with defined roles through Care Team member records. A custom junction object duplicates built-in functionality and adds maintenance overhead.

Correct answer: B. B. Create an owner-based sharing rule that shares all Opportunities owned by any user with the Strategic Accounts public group, granting Read Only access.

An owner-based sharing rule sharing Opportunities owned by any user effectively grants the public group read-only access to all records. Permission sets cannot be assigned to public groups, so the View All option is not even feasible.

Correct answer: B. B. DML operations performed before the fault are committed to the database; only the failing operation is rolled back. Using a Fault connector means the flow continues without rolling back successful prior DML.

Handling an error with a Fault connector lets the flow continue, so earlier successful DML stays committed and only the failing operation rolls back. Automatic full rollback happens only when an error goes unhandled.

Correct answer: A. A. Place all four DML elements (Create Records) sequentially in the Flow without any Fault connectors — if any element fails, Salesforce automatically rolls back the entire transaction.

A flow runs as one transaction, so with no Fault connectors any failed DML rolls back everything automatically. There is no Try/Catch construct in Flow, which makes that distractor a fabrication.

Correct answer: B. B. Offline record creation requires the Salesforce Field Service app with offline priming configured; the standard Salesforce mobile app caches existing records for viewing but does not support creating new records offline.

The standard Salesforce mobile app only lets users view cached records offline; creating records offline needs the Field Service app with offline priming. There is no Offline User license, and object permissions alone don't explain the offline gap.

Correct answer: B. B. IF(Expiry_Date__c >= TODAY(), Expiry_Date__c - TODAY(), 0) · C. C. MAX(Expiry_Date__c - TODAY(), 0)

Both B and C clamp the days-remaining value at zero: B uses an IF condition while C uses MAX with a floor of zero. A and D can return negative values once the expiry date has passed, so they fail the stated requirement.

Correct answer: B. B. A managed package can access Salesforce data based on the permissions granted during installation — the installer chooses which profiles can access the package, and the package code runs under those permissions.

Managed package code executes under the permissions of the users granted access, and the installer controls which profiles can use it. Packages are not isolated from standard objects, and nothing grants automatic System Administrator rights, so A, C, and D fail.

Correct answer: A. A. External Objects are read-only virtual representations of data stored in an external system; custom objects store data physically in the Salesforce database.

External objects are virtual mappings to data held outside Salesforce, while custom objects physically store records in the Salesforce database. External objects lack full native features like roll-up summary fields and triggers, which makes option B clearly wrong.

Correct answer: A. A. Salesforce Connect queries the external system in real time on every page load — performance is dependent on the external system's API response time; adding server-side pagination or caching at the external system level can improve this.

Salesforce Connect queries the external API live on each access, so latency depends on that system's response time; pagination and external caching mitigate it. Options B, C, and D invent limits and features that do not exist in Salesforce Connect.

Correct answer: B. B. Looping over 200,000 records and performing a Get Records query or DML for each record inside the loop will exceed the Flow's governor limits (SOQL queries, DML statements, or CPU time) in a single transaction.

Running Get Records queries or DML inside a loop over 200,000 records blows past governor limits like SOQL queries, DML statements, and CPU time in one transaction. The classic exam cue is never query or update records inside a loop; instead, filter in Get Records and perform bulk updates from a collection.

Correct answer: B. B. Chatter feed posts on a record are automatically scoped to users who have access to that record through the standard Salesforce sharing model — no additional configuration is required.

Record feed posts automatically follow the standard Salesforce sharing model, so only users with access to the Opportunity can see its feed — no extra Chatter setting is needed. Beware distractors naming fake Chatter privacy toggles or linking groups to records.

Correct answer: A. A. Configure Scheduled Flows — one to anonymise Contacts 90 days after inactivation and one to delete records older than 7 years — running on a daily schedule.

Scheduled flows run daily, find Contacts inactive for 90 days or records older than 7 years, and anonymize or delete them without code. Privacy Center retention policies are the purpose-built alternative, which makes option B defensible, but flows are the reliable, always-available answer here.

Correct answer: D. D. Use the Approval Step's 'If the approver does not respond within' setting to automatically reassign or escalate after 48 hours when configured with an escalation approver.

Approval Process steps include a built-in timeout setting that can escalate to an alternate approver, such as the manager's manager, after 48 hours. Reminders only nudge the original approver, and adding a separate step or workflow rule does not create a true timeout escalation path.

Correct answer: B. B. Einstein Bot with a defined dialog flow — a structured menu-driven or slot-filling interaction is well-suited for predictable, bounded tasks like looking up a value based on a specific input.

A dialog-based Einstein Bot with slot filling gives deterministic validation and a predictable lookup path for an exact account number. An autonomous agent adds unnecessary interpretation risk for a bounded task, and a scheduled flow cannot answer a real-time inquiry.

Correct answer: B. B. Agentforce autonomous agent — it uses large language model (LLM) reasoning to interpret the customer's free-form description, determine the appropriate action (create Case, route it), and confirm the outcome without a rigid dialog script.

Free-form outage descriptions need large language model reasoning to infer intent, create the Case, and route it without a rigid script. Hardcoded keyword intents break on synonyms and new phrasings, and dropdown forms or exact-match flows cannot handle natural language variability.

Correct answer: A. A. Configure an Agent Topic defining the outage reporting domain, and create Agent Actions backed by a Flow — one to create the Case and one to route it — then link the Actions to the Topic.

Agentforce requires a Topic defining the outage domain and Agent Actions backed by Flows that create and route the Case, all declaratively with no Apex. The LLM does not perform arbitrary CRUD from prompts alone, and Einstein Bot dialogs are not reused by Agentforce agents.

Correct answer: B. B. After the batch updates the Account records, use a second Queueable Apex job or a Platform Event to handle email notifications asynchronously, keeping email sending outside the bulk DML transaction.

A second Queueable job or Platform Event sends notifications asynchronously after the batch commits the counter and flag updates, isolating email limits from the bulk DML transaction. Sending inside execute() or via a workflow email alert ties emails to the same transaction and risks limits.

Correct answer: B. B. Replace the standard Related List with an Enhanced Related List or configure the related list to show a limited number of recent records (e.g., last 5), reducing the initial query volume on page load.

Limiting the rows rendered in the related list, such as with enhanced related lists showing recent records, cuts the initial query volume and speeds up page load. Option D also defers loading via a tab, which is a defensible alternative, creating some overlap between choices.

Correct answer: B. B. The agents' Presence Configuration total capacity is set higher than 5 for the Chat channel, overriding the org-level setting.

A presence configuration capacity set above five lets Omni-Channel keep assigning chats beyond the intended load. Option A, a chat weight of zero, would also cause over-routing since chats consume no capacity, so both are defensible misconfigurations from the wording.

Correct answer: B. B. Use Salesforce Data Cloud or a third-party analytics platform (like Tableau CRM connected to multiple orgs) to aggregate data from all three orgs into a unified reporting layer.

A unified analytics layer such as Data Cloud or Tableau CRM connects to all three orgs and consolidates revenue without migration. Manual spreadsheets are error-prone, and federated SOQL or custom connected apps are not supported native patterns.

Correct answer: B. B. Salesforce Files (Content) — when a file is uploaded to a record's Files related list, users can upload a new version of the same file, and all previous versions are retained and accessible via the file's version history.

Salesforce Files natively keeps every previous version in the file's version history when a new version is uploaded to a record. Chatter attachments have no real version history, and Content Libraries are the legacy model rather than the standard record-based answer.

Correct answer: C. C. Enable the 'Moderate Chatter' permission in the user's profile or permission set, which allows the user to flag, delete, and manage Chatter posts across the org.

The Moderate Chatter permission, granted through a profile or permission set, lets a user delete and manage posts org-wide without admin rights. Group moderation is scoped per group, and roles control data visibility, not Chatter moderation ability.

Correct answer: C. C. The release manager manually reviews both XML files, identifies the conflicting Flow elements, merges the changes by editing the XML directly or in the Flow Builder, commits the resolved version, and re-deploys.

Manually reviewing both XML versions and merging in Flow Builder preserves both developers' changes with validated logic. Accepting one branch as canonical risks losing edits, and there is no reliable intelligent Flow merge tool for complex XML.

Correct answer: A. A. Use the sf project deploy validate command to run a check-only deployment against production — it validates metadata and runs Apex tests without committing changes, acting as a pre-production gate.

A check-only validation deployment runs Apex tests and validates metadata without saving changes, giving an automated pre-production gate. The strongest distractor invents a Deployment Approval feature that Salesforce does not provide in Setup.

Correct answer: B. B. Use sharing rules based on the Care Team relationship — Health Cloud supports sharing configuration that grants a provider access to patient records where they are an active Care Team member.

Care Team-based sharing grants providers access only to patients they actively support while preserving Private OWD. View All would expose every patient and violate least privilege, making it the clearest wrong choice.

Correct answer: B. B. Sequential placement of Flow elements on the canvas — Flow executes elements in the order they are connected; placing the Account Update element after the Milestone creation elements ensures correct sequencing.

Flows execute elements in the order their connectors link them, so placing the Account update after the Milestone creations guarantees it runs last. Remember there is no 'Final Action' setting, and Wait elements don't affect transaction commit behavior in a single flow execution.

Correct answer: D. D. A Roll-Up Summary field is not supported on Opportunity for OpportunityLineItem because they have a system-managed relationship; instead, use a Flow that totals line item list prices and updates a custom currency field.

Salesforce does not allow roll-up summary fields on Opportunity over Opportunity Products because that relationship is system-managed, so a Flow totaling line-item list prices into a custom field is the supported no-code approach. Option A describes a feature that isn't available here.

Correct answer: B. B. Email-to-Case uses email threading headers (such as In-Reply-To and References) to associate incoming replies to the correct Case; agent replies from the Case feed maintain the thread automatically.

Email-to-Case threading uses standard email headers plus Salesforce's thread ID to associate replies with the correct Case, keeping conversations continuous. There is no dedicated Thread-ID toggle in routing settings, so option C describes a nonexistent feature.

Correct answer: C. C. Inside the LWC, use the @api formFactor property or import { CurrentPageReference } to detect the form factor and conditionally render a simplified template using conditional rendering directives.

Detecting the form factor inside the component and conditionally rendering a simplified template keeps one codebase and adapts automatically per device. Separate desktop and mobile components duplicate effort, and the wording of the form factor API is imprecise but the concept is right.