Practical Application OF Sales Cloud Expertise practice questions

A Workflow Rule with a field update.

Why it fails: A Workflow Rule field update can only modify fields on the triggering Opportunity or its master, never create a new Project record. It is tempting because workflow rules are declarative and fire on criteria such as Closed Won, but record creation on a separate custom object requires a Flow.

An Apex Trigger.

Why it fails: An Apex Trigger is code, not declarative, so it fails the requirement for the most efficient declarative tool and adds maintenance overhead. It is tempting because triggers can create records on any object with full control, and would be correct where declarative limits are exceeded or complex logic is needed.

A Process Builder with an action to create a record.

Why it fails: Process Builder is retired and superseded by Flows.

Sharing Rules configuration.

Why it fails: Sharing rules control visibility, not deletion restrictions.

A Validation Rule using the ISCLOSED function.

Why it fails: Validation rules cannot prevent record deletion.

An Approval Process.

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

Within CPQ Package Settings.

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

In the App Launcher under Email Templates.

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

On the Opportunity page layout properties.

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

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

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

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

Why it fails: 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 it fails: Manual sharing is not scalable and does not dynamically update when team composition changes.

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

Why it fails: Role hierarchy is separate from territory hierarchy.

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

Why it fails: Territory management automates sharing without requiring manual rules.

The Organization-Wide Default sharing setting for Territories.

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

Opportunity split types mapped to campaign records.

Why it fails: Opportunity split types distribute credit among team members on a single opportunity; they record revenue attribution percentages, not campaign totals. Campaign ROI needs the summed amount of won opportunities linked to a campaign, which the standard Campaign object's built-in roll-up fields provide without any split configuration.

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

Why it fails: Roll-up summary fields cannot be created on the Campaign object referencing Opportunities, because Campaign Influence is modelled through a junction object rather than a direct lookup or master-detail relationship. The standard Campaign object already exposes roll-up fields for won opportunity value, so no custom field is needed.

Campaign Hierarchy roll-up summaries.

Why it fails: Campaign Hierarchy roll-up summaries aggregate metrics from child campaigns into a parent campaign, so they total across related campaigns rather than across the opportunities attached to one campaign. The standard Campaign object already rolls up won opportunity value directly, so hierarchy aggregation is unnecessary here.

Advanced Currency Management

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

Account Teams and Opportunity Teams

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

Multi-Currency and Territory Management

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

A custom report type filter.

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

Salesforce Surveys sent automatically via flow.

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

Default opportunity team creation rules.

Why it fails: Team creation does not gate stage progression.

Assets (directly on Campaign detail page)

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

Cases (directly linked for customer support attribution)

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

A custom button leveraging URL hacking to launch a flow with pre-selected products.

Why it fails: URL hacking is deprecated in Lightning Experience.

Standard Opportunity Product Default settings in Setup.

Why it fails: Salesforce does not have a native 'default products' checkbox in standard setup without automation or CPQ.

Configuring a Price Book entry override rule in Account Settings.

Why it fails: Account settings do not govern default products.

Create a custom profile for the user that restricts standard field editing, combined with Opportunity Team Read/Write access.

Why it fails: A custom profile would restrict fields globally, which may not be desired for other opportunities where they are the owner.

Configure Field-Level Security (FLS) on standard opportunity fields to make them read-only for that user profile, while granting Read/Write via Opportunity Team.

Why it fails: Opportunity Team access applies to the entire record, overriding or operating alongside sharing rules; FLS applies globally to profiles/permission sets.

Use Opportunity Sharing Rules to grant field-specific permissions to the team member.

Why it fails: Sharing rules grant record-level access (Read/Write or Read-Only), not field-level permissions.

A dashboard component displaying overdue tasks grouped by Account owner.

Why it fails: Overdue tasks do not identify accounts that have completely lacked activity for 90 days.

A joined report combining Account data and Task data with a custom SQL join condition.

Why it fails: Salesforce reports do not use SQL join conditions, and cross filters are simpler and native.

A standard Account report with a standard 'Last Activity' field filter set to less than 90 days.

Why it fails: Filtering by Last Activity date excludes accounts with no activity history entirely or behaves unpredictably depending on task creation.

Creating an Order automatically closes the associated Opportunity as Closed Won.

Why it fails: Creating an order does not automatically close the opportunity; opportunity stage changes must be managed separately or via automation.

Updating the Quote after the Order is created automatically updates the corresponding Order line items.

Why it fails: Once an order is created from a quote, subsequent edits to the quote do not automatically sync or update the order.

Forecast managers cannot be changed once a forecast type is activated.

Why it fails: Forecast managers can be adjusted and assigned within the forecast hierarchy setup at any time.

Custom currency fields cannot be used as the basis for custom forecast types.

Why it fails: Custom currency fields on opportunities or line items can indeed be used as the basis for custom forecast types.

The user does not have a license for CPQ.

Why it fails: A CPQ licence governs access to quoting features, but the stem gives no evidence of a licensing gap, and a missing licence typically blocks the app entirely rather than one action. It is genuinely the cause when a user lacks the CPQ permission set.

The user is not in a role hierarchy.

Why it fails: Role hierarchies govern record access for users who own or share records, so their absence cannot block Quote creation itself. The tempting association arises because hierarchies are configured for manager visibility over subordinates' records, and they would be the relevant answer if the scenario instead described a manager unable to view a subordinate's quotes.

The Account does not have a contact.

Why it fails: A missing Account contact does not prevent Quote creation; contacts are optional on many quote layouts and unrelated to object-level create permission. It is genuinely relevant when generating quotes that require a primary contact for delivery or billing.

The user has a Profile with 'View All' on Contacts.

Why it fails: This would grant visibility.

The Contact OWD is set to Public Read/Write.

Why it fails: This would make them visible.

The user is the Owner of the Contact.

Why it fails: Ownership grants access.

Territory Management.

Why it fails: This is for sales territory assignment.

Multi-language support.

Why it fails: This supports translation, not currency logic.

Salesforce Shield.

Why it fails: This relates to security and compliance.

Create a Public Group with access to all Contacts.

Why it fails: This would expose all contacts, which is not desired.

Change OWD to Public Read/Write.

Why it fails: This violates the private security model.

Use a Permission Set to grant 'View All' on Contacts.

Why it fails: This grants access to all contacts in the org, violating the private model.

Workflow Rule.

Why it fails: Workflows cannot prevent stage changes.

Flow Builder.

Why it fails: Flow can automate, but Validation Rules are better suited for blocking user actions based on criteria.

Lead Assignment Rule.

Why it fails: These are for lead routing.

Account Team.

Why it fails: This is for collaboration, not global visibility.

Role Hierarchy.

Why it fails: Hierarchy only grants upward visibility.

Public Group.

Why it fails: A group doesn't automatically share records.