Practical Application OF Sales Cloud Expertise practice questions

Create a Criteria-Based Sharing Rule based on the Opportunity Owner field.

Why wrong: Criteria-based sharing rules cannot dynamically evaluate team membership.

Change the Organization-Wide Default for Opportunity to Public Read Only.

Why wrong: This would open opportunity visibility to all users, violating the restriction requirement.

Create a Public Group for each Sales Team and assign them via manual sharing.

Why wrong: Manual sharing is not scalable and does not dynamically update when team composition changes.

Assets (directly on Campaign detail page)

Why wrong: Assets relate to accounts and contacts, not directly as a core related list on campaigns.

Cases (directly linked for customer support attribution)

Why wrong: Cases relate to accounts, contacts, and assets, not directly to campaigns.

A Workflow Rule with a field update.

Why wrong: Workflow rules cannot create new records; they can only update the triggering record.

An Apex Trigger.

Why wrong: An Apex trigger is code and violates the declarative requirement for efficiency when flows can handle it.

A Process Builder with an action to create a record.

Why wrong: Process Builder is retired and superseded by Flows.

From the custom exchange rate object populated by a nightly batch job.

Why wrong: Salesforce has built-in currency management features that negate the need for custom objects.

From the user's personal locale and currency settings.

Why wrong: Currency conversion is based on corporate currency and dated/active conversion rates, not personal user settings.

From the Price Book entry associated with the opportunity line items.

Why wrong: Price books store product prices, not currency conversion rates.

Sharing Rules configuration.

Why wrong: Sharing rules control visibility, not deletion restrictions.

A Validation Rule using the ISCLOSED function.

Why wrong: Validation rules cannot prevent record deletion.

An Approval Process.

Why wrong: Approval processes control record locking and approval routing, not direct deletion prevention.

Within CPQ Package Settings.

Why wrong: Standard quotes do not use CPQ settings unless Salesforce CPQ is installed.

In the App Launcher under Email Templates.

Why wrong: Email templates are used for standard emails, not for generating structured PDF quotes with line items.

On the Opportunity page layout properties.

Why wrong: Quote templates are separate record layouts managed in Setup, not directly on the page layout properties.

Sales Process picklist values.

Why wrong: Sales processes define picklist values for stages, but do not provide the visual path interface on the record page.

Opportunity dashboards.

Why wrong: Dashboards are reporting tools, not record-level milestone trackers.

Custom related lists for milestones.

Why wrong: A custom related list is unnecessary when Path natively fulfills this requirement.

The Account access level assigned in the Territory Model settings for the user's assigned role.

Why wrong: Role hierarchy is separate from territory hierarchy.

Manual sharing rules created on the Account object for territory members.

Why wrong: Territory management automates sharing without requiring manual rules.

The Organization-Wide Default sharing setting for Territories.

Why wrong: Territories do not have OWD settings in the same way standard objects do; access is governed by territory models.

Custom lead fields are lost upon conversion and must be re-entered manually.

Why wrong: Data is preserved through field mapping.

Custom lead fields are automatically mapped to all three objects based on field API names.

Why wrong: Salesforce does not automatically map custom lead fields by name; they must be explicitly mapped.

Custom lead fields can only be mapped to the Opportunity object.

Why wrong: They can be mapped to Account, Contact, and Opportunity.

Only from the Reports tab.

Why wrong: Reports are for viewing aggregated data, not sending transactional emails.

From the Lead Conversion window.

Why wrong: Lead conversion merges data into accounts, contacts, and opportunities, and is not used for emailing leads.

From the Campaign Member status history.

Why wrong: Campaign member status tracks participation, not direct email composition.

Public Read/Write/Transfer

Why wrong: This would grant full access to all contacts across the organization.

Public Read Only

Why wrong: Public Read Only would allow all users to view all contacts.

Private

Why wrong: Private would require manual or rule-based sharing for contacts independent of accounts.

The contact mailing address automatically populates from the account billing address.

Why wrong: Contact addresses do not auto-populate from account addresses by default in standard Salesforce.

The contact address is locked to match the account shipping address.

Why wrong: Addresses are independent fields.

The contact inherits the account phone number and address simultaneously.

Why wrong: Only relationship linkages occur; field values are not copied automatically.

Salesforce Einstein Activity Capture logs.

Why wrong: Einstein Activity Capture logs emails and events, not historical stage durations.

Custom object triggered by a flow on every stage change.

Why wrong: A custom tracking object is unnecessary since standard history tracking and reporting exist.

Campaign Influence reports.

Why wrong: Campaign influence tracks marketing attribution, not sales pipeline velocity.

The system prevents changing the price book if line items exist.

Why wrong: The system allows the change but displays a warning that existing products will be deleted.

They remain on the opportunity, but are marked as inactive.

Why wrong: They are completely deleted.

They are automatically updated with prices from the new price book.

Why wrong: Salesforce does not automatically match items across different price books.

Order and Contract.

Why wrong: Orders and contracts can track fulfillment, but standard forecasting relies on opportunities and splits.

Account, Contact, and Lead.

Why wrong: Forecasts measure revenue or quantity, typically anchored on opportunities, not leads or accounts.

Campaign and Quote.

Why wrong: Campaigns and quotes are not primary forecast source objects in standard Collaborative Forecasts.

Opportunity split types mapped to campaign records.

Why wrong: Opportunity splits allocate revenue among sales team members, not campaigns.

Custom Roll-Up Summary fields on the Campaign object pointing to Opportunities.

Why wrong: Roll-up summary fields cannot be created on Campaign pointing directly to Opportunity because they are on different relationship paths (via Campaign Member or Primary Campaign Source).

Campaign Hierarchy roll-up summaries.

Why wrong: Hierarchy roll-ups summarize campaign metrics across parent-child campaigns, not directly opportunity amounts.

The order is automatically deleted from the system and converted into an invoice.

Why wrong: Orders are not deleted upon activation.

The order record is locked and cannot be edited by any user.

Why wrong: Users with specific permissions or administrators can sometimes edit, but standard editing is restricted. Actually, standard activated orders are read-only for standard users.

The order status resets to Draft automatically after 24 hours.

Why wrong: Order status does not reset automatically.

Advanced Currency Management

Why wrong: Advanced Currency Management is used for dated exchange rates, not sales credit splits.

Account Teams and Opportunity Teams

Why wrong: Teams grant record access and collaboration roles, but do not split revenue percentages for forecasting.

Multi-Currency and Territory Management

Why wrong: These features manage currencies and territory assignment, not revenue partitioning.

A custom report type filter.

Why wrong: Report types are for reporting, not data entry enforcement.

Salesforce Surveys sent automatically via flow.

Why wrong: Surveys gather customer feedback, not internal sales process gating.

Default opportunity team creation rules.

Why wrong: Team creation does not gate stage progression.

Automatically enforce territory realignment based on account revenue changes.

Why wrong: Territory realignment is handled by Enterprise Territory Management, not account teams.

Allow users to set up a Default Account Team to quickly add members to opportunities they own.

Why wrong: Default account teams are added to accounts, not opportunities directly.