Courseiva

CCNA Practical Application Of Sales Cloud Expertise Questions

75 of 82 questions · Page 1/2 · Practical Application Of Sales Cloud Expertise topic · Answers revealed

Practice these questionsExam hubAll questions
1
Multi-Selecthard

Which THREE of the following are capabilities of Campaign Management in Salesforce?

Select 3 answers
A.Campaigns can automatically update the Opportunity Stage to Closed Won
B.Campaign members can track custom status values such as 'Responded' or 'Attended'
C.Campaigns can be directly converted into Opportunities
D.Campaign members can be added from both Leads and Contacts
E.Campaign Hierarchy allows for rolling up data from child campaigns to parent campaigns
AnswersB, D, E

Campaign members support configurable status values beyond the default picklist, letting teams record responses such as 'Responded' or 'Attended'. This satisfies the stem's requirement for campaign management capability, since member status tracking drives response reporting and campaign ROI analysis within Salesforce.

Why this answer

Option B is correct because Campaign Members have a Status field that can be customized with picklist values such as 'Responded' or 'Attended' to track each member's engagement. Option D is correct because Campaign Members can be individual Leads or Contacts (and Person Accounts), allowing you to associate both types with a single campaign. Option E is correct because Campaign Hierarchy lets you link child campaigns to a parent campaign and roll up metrics like responses and ROI to the parent level.

Option A is not a capability of Campaign Management; Opportunity Stage changes are driven by Opportunity processes or automation, not by campaigns directly. Option C is incorrect because campaigns cannot be directly converted into Opportunities; conversion applies to Leads, and Opportunities are created separately or via automation.

Exam trap

Sales-Con-201 often tests the misconception that Campaigns can drive Opportunity Stage changes or be converted into Opportunities, when campaigns only track influence and membership.

Practice this question →
2
Multi-Selectmedium

Which THREE items can be tracked in an Activity Timeline?

Select 3 answers
A.Tasks.
B.Log a call records.
C.Events.
D.Opportunity status changes.
E.Account hierarchy updates.
AnswersA, B, C

Tasks appear on the Activity Timeline as open and completed to-dos, showing what needs doing and what has been done against the record. They are one of the activity types the timeline aggregates alongside events and logged calls.

Why this answer

In Salesforce, the Activity Timeline component on a record page displays a unified chronological feed of activities and related records, and it specifically tracks Tasks (option A), Log a Call records (option B), and Events (option C) — these are the standard activity objects whose entries appear as timeline items with due dates, times, and statuses. Tasks appear as actionable to-dos, logged calls appear as completed call entries with call type, purpose, and comments, and Events appear as scheduled meetings or appointments with start/end times. Option D (Opportunity status changes) is not an activity object but a field-history/Stage History concept, which is surfaced through related lists or reports, not the Activity Timeline.

Option E (Account hierarchy updates) relates to the account hierarchy structure and is likewise not an activity record, so it does not appear in the Activity Timeline.

Exam trap

Sales-Con-201 often tests whether candidates confuse activity objects (Tasks, Events, Calls) with field history or audit trail data — the timeline only shows activities, not field changes.

Practice this question →
3
MCQeasy

A sales manager wants to track key milestones during the sales cycle for opportunities, such as identifying decision makers and presenting proposals, directly on the opportunity record page. Which feature should the administrator configure?

A.Path Settings and Key Fields.
B.Sales Process picklist values.
C.Opportunity dashboards.
D.Custom related lists for milestones.
AnswerA

Path Settings with Key Fields displays a guided sales process on the opportunity record, highlighting milestones such as identifying decision makers and presenting proposals. It satisfies the requirement to track cycle milestones directly on the record page.

Why this answer

Path Settings and Key Fields allow administrators to add a guided path on the Opportunity record page that displays key milestones (stages) and prompts users to complete critical fields at each stage. This directly supports tracking milestones like identifying decision makers and presenting proposals. Sales Process picklist values define the stages but do not provide the visual guidance or milestone tracking on the record page.

Exam trap

Sales-Con-201 often tests the confusion between Sales Process picklist values (which define stages) and Path Settings (which provide the visual milestone guidance), tempting candidates to choose the picklist option for a UI guidance requirement.

How to eliminate wrong answers

Option B is wrong because Sales Process picklist values only define the stage values available for an opportunity record type; they do not provide the on-page guidance or milestone tracking feature. Option C is wrong because Opportunity dashboards are reporting tools that visualize data, not a mechanism to guide users through milestones on the record page. Option D is wrong because custom related lists display related records (e.g., milestones as child records) but do not offer the guided path UI or key field prompting that Path provides.

Practice this question →
4
Multi-Selectmedium

Which THREE objects can be linked to a Campaign?

Select 3 answers
A.Price Book.
B.Lead.
C.Opportunity.
D.Contact.
E.Order.
AnswersB, C, D

Leads capture unqualified interest and can be associated with a Campaign to track their originating marketing effort, satisfying the requirement that Campaigns link to pre-qualification records. This association lets sellers monitor which campaigns generate leads before those leads convert into opportunities, aligning with Dynamics 365 Sales campaign management.

Why this answer

In Salesforce, a Campaign can be linked to Leads, Contacts, and Opportunities through Campaign Members and the Opportunity Campaign Influence feature. Option B (Lead) is correct because leads can be added as campaign members to track their response to a campaign. Option C (Opportunity) is correct because opportunities can be associated with campaigns via Campaign Influence, allowing attribution of revenue to marketing efforts.

Option D (Contact) is correct because contacts can also be added as campaign members, enabling tracking of their engagement. Option A (Price Book) is not correct because price books are related to products and price book entries, not campaigns. Option E (Order) is not correct because orders are not directly linked to campaigns in standard Salesforce functionality.

Exam trap

The trap is assuming any object can be linked to a Campaign; candidates may pick Order or Price Book, but only Leads, Contacts, and Opportunities have native campaign associations.

Practice this question →
5
MCQhard

An organization wants to restrict the visibility of the 'Discount' field on an Opportunity based on the user's Profile. What is the most secure way to do this?

A.Sharing Rules.
B.Field-Level Security.
C.Validation Rules.
D.Page Layout assignments.
AnswerB

Field-Level Security directly satisfies the Profile-based visibility constraint by defining read/edit permissions per field, per profile. Unlike page layouts, which merely hide fields cosmetically and remain bypassable via reports, list views, or the API, FLS enforces restrictions at the data layer, ensuring the Discount field stays inaccessible regardless of how the record is queried.

Why this answer

Field-Level Security (FLS) is the most secure and appropriate way to restrict visibility of a specific field, such as 'Discount' on Opportunity, based on a user's Profile. FLS is configured at the Profile or Permission Set level and controls whether a user can view or edit a field, regardless of page layout or record access. This ensures that even if a user has access to the record, the field itself remains hidden or read-only.

Exam trap

Sales-Con-201 often tests the confusion between record-level security (Sharing Rules) and field-level security (FLS), leading candidates to choose Sharing Rules when field visibility is the requirement.

How to eliminate wrong answers

Option A is wrong because Sharing Rules control record-level access, not field-level visibility; they cannot hide a specific field. Option C is wrong because Validation Rules enforce data integrity on save, not field visibility; they cannot prevent a user from seeing a field. Option D is wrong because Page Layout assignments control the arrangement and presence of fields on a page layout, but they are not a security mechanism—users can still access the field via reports, APIs, or other layouts.

Practice this question →
6
MCQhard

A Sales Rep needs to change the owner of an Opportunity, but the new owner does not have access to the Account associated with that Opportunity. How does Sales Cloud handle this visibility?

A.The change will be blocked by the system
B.The user will gain implicit Read access to the Account
C.The user will gain Edit access to the Account
D.The user must manually be added to the Account Team
AnswerB

Changing an Opportunity's owner grants the new owner implicit Read access to the parent Account, satisfying the requirement that they can see the associated record without an explicit sharing rule. This inherited access flows from the Opportunity's lookup relationship to the Account, ensuring visibility is maintained automatically upon ownership transfer.

Why this answer

When an Opportunity's owner is changed to a user who lacks access to the parent Account, Salesforce grants that user implicit Read access to the Account. This ensures the Opportunity owner can view the Account context needed to work the deal, without granting Edit rights on the Account itself. This is a built-in behavior of the sharing model.

Exam trap

The trap is assuming the system blocks the ownership change or requires manual sharing — candidates often miss that Salesforce automatically grants implicit Read access to the parent Account for child record owners.

How to eliminate wrong answers

Option A is wrong because Salesforce does not block the ownership change — it automatically grants the necessary access. Option C is wrong because the implicit access granted is Read-only, not Edit; the new owner cannot modify the Account unless separately granted access. Option D is wrong because manual Account Team addition is not required — implicit sharing handles visibility automatically, though adding to the team is an option for granting broader access.

Practice this question →
7
Multi-Selecthard

When configuring Collaborative Forecasts, which THREE metrics or parameters can be selected to define forecast types? (Choose three.)

Select 3 answers
A.Opportunity Quantity
B.Opportunity Splits (Revenue or Percentage)
C.Lead Conversion Count
D.Opportunity Amount (Revenue)
E.Campaign ROI Percentage
AnswersA, B, D

Opportunity Quantity is a supported forecast type metric, letting managers forecast on the number of opportunities rather than revenue. Selecting it satisfies the stem's requirement that forecast types be defined by a valid metric, since quantity is natively available for Collaborative Forecasts configuration.

Why this answer

In Salesforce Collaborative Forecasts, forecast types are defined by selecting a forecast category and one or more measure metrics from the available set: Opportunity Amount (Revenue), Opportunity Quantity, and Opportunity Splits (Revenue or Percentage). Option A (Opportunity Quantity) is correct because quantity-based forecasting lets users forecast on the number of units/products rather than monetary value. Option B (Opportunity Splits) is correct because forecast types can be configured to use either revenue-based or percentage-based opportunity splits, enabling split-credit forecasting.

Option D (Opportunity Amount (Revenue)) is correct because it is the standard revenue measure used to build a forecast type. Options C (Lead Conversion Count) and E (Campaign ROI Percentage) are not selectable forecast metrics — leads and campaigns are not forecastable objects in Collaborative Forecasts, so neither can define a forecast type.

Exam trap

Sales-Con-201 often tests whether candidates can distinguish between valid forecast metrics (Quantity, Amount, Splits) and unrelated metrics (Lead Conversion, Campaign ROI) — the trap is picking metrics that sound sales-related but are not forecastable.

Practice this question →
8
MCQeasy

A company needs to ensure that all Quotes created for an Opportunity are based on the products in that Opportunity. What is the mandatory step?

A.Use Campaign Influence.
B.Ensure the Opportunity has products added.
C.Create a Lead first.
D.Enable Orders.
AnswerB

Quotes inherit their product line from the Opportunity's existing product records, so an Opportunity without products cannot generate a valid Quote. Adding products to the Opportunity satisfies this prerequisite, ensuring every Quote reflects the products listed against that Opportunity.

Why this answer

To create Quotes based on Opportunity products, the Opportunity must first have products added (OpportunityLineItem records). Quotes are generated from the opportunity's product list, so without products on the opportunity, there is nothing to base the quote on. This is a mandatory prerequisite in Salesforce's quoting flow.

Exam trap

Sales-Con-201 often tests the prerequisite relationship between Opportunity Products and Quotes, tempting candidates to select unrelated features like Campaign Influence or Orders instead of the mandatory product prerequisite.

How to eliminate wrong answers

Option A is wrong because Campaign Influence tracks marketing campaign impact on opportunities, not quote creation. Option C is wrong because creating a Lead first is unrelated to quoting; leads are pre-opportunity prospects. Option D is wrong because enabling Orders is a separate feature for order management and is not required to create quotes from opportunity products.

Practice this question →
9
MCQhard

A company needs to implement 'Territory Management' to structure their sales team. What is the primary benefit?

A.To simplify record ownership.
B.To track regional office expenses.
C.To automate lead routing.
D.To define territory-based access to accounts and opportunities.
AnswerD

Territory Management assigns accounts and opportunities to territories via assignment rules, then uses those territories to drive record-level access for sales reps. This satisfies the need to structure the sales team while restricting visibility by territory.

Why this answer

Territory Management in Sales Cloud is designed to structure sales teams by defining territories and assigning accounts and opportunities to those territories. Its primary benefit is to provide territory-based access to accounts and opportunities, ensuring that sales reps only see and work on records within their assigned territories, which improves focus and accountability.

Exam trap

Sales-Con-201 often tests the primary purpose of Territory Management, and candidates may confuse it with lead routing or expense tracking, which are unrelated features.

How to eliminate wrong answers

Option A is wrong because while territory management can simplify record ownership by automating assignment, the primary benefit is not just simplification but structured access control based on territories. Option B is wrong because tracking regional office expenses is a financial task, not the purpose of Territory Management. Option C is wrong because automating lead routing is typically handled by Lead Assignment Rules or other automation tools, not Territory Management, which focuses on accounts and opportunities.

Practice this question →
10
MCQhard

A user has 'Read' access to an Account but cannot see the Opportunity related to that Account. What is the most likely reason?

A.The Opportunity OWD is 'Private'.
B.The Opportunity has a different record type.
C.The user is not in the Account Team.
D.The user's profile lacks 'Read' on Opportunities.
AnswerA

Opportunity's organisation-wide default of Private restricts visibility to the owner and anyone above them in the hierarchy, regardless of Account read access. Because the user lacks a share on the Opportunity itself, they cannot see it, even though Account access is granted.

Why this answer

If the Opportunity's Organization-Wide Default is set to 'Private', only the Opportunity owner and users above them in the role hierarchy (plus those with explicit sharing) can see it. A user with Read access to the parent Account does not automatically gain access to Opportunities under that Account when Opportunity OWD is Private. This is the most likely reason for the visibility gap.

Exam trap

The trap is assuming that Account access cascades to Opportunities — candidates often confuse the implicit sharing behavior of Contacts (which do inherit from Account) with Opportunities (which do not when OWD is Private).

How to eliminate wrong answers

Option B is wrong because record types control picklist values, page layouts, and business processes — they do not restrict record visibility. Option C is wrong because Account Team membership grants access to the Account and, depending on configuration, related records, but the absence of team membership is not the primary reason an Opportunity is hidden when OWD is Private. Option D is wrong because if the profile lacked Read on Opportunities entirely, the user could not see any Opportunities — the question implies they can see some, so profile-level access is not the issue.

Practice this question →
11
Multi-Selectmedium

Which TWO fields are essential for calculating the 'Expected Revenue' on an Opportunity?

Select 2 answers
A.Lead Source.
B.Close Date.
C.Amount.
D.Probability.
E.Stage.
AnswersC, D

Amount supplies the monetary value that Expected Revenue multiplies by probability, so it directly satisfies the calculation requirement. Without a populated Amount field, the rollup cannot produce a figure, regardless of probability or close date. This makes Amount one of the two essential fields the stem demands.

Why this answer

Option C (Amount) is correct because Expected Revenue is calculated by multiplying the Opportunity's Amount by its Probability, so the Amount value is a required input for the formula. Option D (Probability) is correct because it serves as the percentage multiplier applied to the Amount to derive Expected Revenue. Lead Source (A) is a marketing attribution field that has no role in the Expected Revenue formula.

Close Date (B) is used for forecasting timelines but does not factor into the Expected Revenue calculation. Stage (E) is not used directly, since Probability is the field that carries the numeric percentage into the calculation.

Exam trap

Sales-Con-201 often tests the misconception that Stage directly determines Expected Revenue, when in fact Probability is the direct multiplier; Stage only influences Probability if mapped.

Practice this question →
12
Multi-Selectmedium

Which THREE objects are involved in the standard Opportunity-to-Revenue workflow?

Select 3 answers
A.Lead.
B.Opportunity.
C.Product.
D.Campaign.
E.Quote.
AnswersB, C, E

The Opportunity is the central transaction record in the Opportunity-to-Revenue workflow, capturing the potential deal before quoting. It links to the Account and later spawns Quotes and Orders, satisfying the stem's requirement for one of the three core objects in that sequence.

Why this answer

In the standard Opportunity-to-Revenue workflow, the Opportunity (B) is the central object because it represents the potential deal being tracked through qualification, negotiation, and closure. The Product (C) is involved because products are added to the opportunity as line items to define what is being sold and to calculate pricing and revenue. The Quote (E) is also involved because it is generated from the opportunity and its products to present formal pricing and terms to the customer before the deal is closed.

The Lead (A) belongs to the earlier Lead-to-Opportunity workflow, where it is converted into an opportunity, and the Campaign (D) is a marketing object used for lead generation and attribution rather than the Opportunity-to-Revenue process itself.

Exam trap

Sales-Con-201 often tests the distinction between the Lead-to-Opportunity process and the Opportunity-to-Revenue workflow, causing candidates to incorrectly include Lead or Campaign as part of the revenue cycle.

Practice this question →
13
MCQmedium

An organization uses 'Campaigns'. What is the 'Campaign Member' object used for?

A.To track revenue.
B.To track activities.
C.To track the relationship between Leads/Contacts and Campaigns.
D.To track products.
AnswerC

Campaign Member is a junction object linking a Lead or Contact to a Campaign, storing per-recipient status such as Sent or Responded. It satisfies the need to track which individuals belong to which campaign and their responses.

Why this answer

The Campaign Member object is used to track the relationship between Leads/Contacts and Campaigns. It represents an individual who is a member of a campaign, storing details such as status (e.g., Sent, Responded) and the associated Lead or Contact. This allows marketers to manage campaign membership and track responses.

Exam trap

The trap is confusing Campaign Member with other objects like Opportunity or Activity; candidates may think it tracks revenue or activities directly.

How to eliminate wrong answers

Option A is wrong because revenue tracking is typically done through Opportunities and Campaign influence, not directly via Campaign Member. Option B is wrong because activities are tracked via Tasks and Events, not Campaign Member. Option D is wrong because products are tracked via Products and Price Books, not Campaign Member.

Practice this question →
14
MCQmedium

A company is using 'Opportunity Splits' to manage revenue sharing. What must be enabled first?

A.Advanced Currency Management.
B.Orders.
C.Price Books.
D.Team Selling.
AnswerD

Opportunity Splits distribute revenue across multiple participants, so Team Selling must be enabled first to create the opportunity team whose members receive those splits. Without an active team, split records have no recipients to assign percentages to.

Why this answer

Opportunity Splits require Team Selling to be enabled first. Team Selling allows the creation of opportunity teams, which is a prerequisite for splitting opportunity revenue among team members. Without Team Selling, the Opportunity Splits feature is not available.

Exam trap

Sales-Con-201 often tests the prerequisite relationship between Team Selling and Opportunity Splits, catching candidates who overlook the foundational feature.

How to eliminate wrong answers

Option A is wrong because Advanced Currency Management is used for managing dated exchange rates and does not enable Opportunity Splits. Option B is wrong because Orders are a separate object for order management and are unrelated to Opportunity Splits. Option C is wrong because Price Books are used for managing product pricing and do not enable Opportunity Splits.

Practice this question →
15
MCQhard

Northern Trail Outfitters uses Collaborative Forecasting with Opportunity Revenue. A sales rep updates an Opportunity stage from 'Prospecting' to 'Closed Won' and changes the Amount from $10,000 to $12,000, but fails to update the Close Date, which remains set to a date in the previous fiscal quarter. How does this impact the forecast?

A.The forecast will show an error until the Close Date is updated to match the current fiscal quarter.
B.The $12,000 will appear in the current fiscal quarter forecast based on the date the stage changed.
C.The opportunity will be excluded entirely from forecasts because it is closed-won with a mismatched date.
D.The $12,000 will be attributed to the previous fiscal quarter forecast based on the Close Date.
AnswerD

Forecast attribution follows the Opportunity Close Date, not the stage-change timestamp. Because the Close Date still sits in the prior fiscal quarter, the revised $12,000 amount rolls into that earlier quarter's forecast, overriding the current-period expectation.

Why this answer

Forecasts rely on the Close Date to determine which time period the revenue is attributed to.

Practice this question →
16
Multi-Selectmedium

Which TWO methods can be used to share an Account with a colleague?

Select 2 answers
A.Set as record owner.
B.Account Team.
C.Manual Sharing.
D.Add to public folder.
E.Change Profile.
AnswersB, C

Account Team membership grants colleagues access to the shared account record directly within the sales application, satisfying the requirement to share an account without reassigning ownership. Adding colleagues to the Account Team links them to the record, so they can collaborate on it while the owner retains accountability.

Why this answer

Account Team (B) is correct because adding a colleague to the Account Team grants them access to the account record through the account team member's access level (Read/Write or Read Only), which is a standard way to share an account with other users. Manual Sharing (C) is correct because a user with sharing privileges can manually share an individual Account record with another user or group, granting Read or Read/Write access via the Sharing button on the record. Setting as record owner (A) transfers ownership rather than sharing, so it does not fit the scenario of sharing with a colleague.

Adding to a public folder (D) applies to sharing folders for reports, dashboards, and documents, not Account records. Changing the Profile (E) alters a user's overall permissions and object-level access, not sharing of a specific Account record.

Exam trap

Sales-Con-201 often tests the difference between ownership, sharing, and permission changes — the trap is selecting 'change owner' or 'change profile' when the question asks about sharing access without transferring ownership.

Practice this question →
17
Multi-Selectmedium

Which TWO components are needed for a Price Book?

Select 2 answers
A.Price Book Entry records.
B.Product records.
C.Order records.
D.Campaign records.
E.Lead records.
AnswersA, B

Price Book Entries link products to a price book and carry the actual list price, so a price book cannot hold pricing without them. They satisfy the stem's requirement that both a product and its price be present, forming the second mandatory component alongside Product records.

Why this answer

A Price Book requires Price Book Entry records (option A) because the Price Book Entry object is the junction that links a Product2 to a specific Price Book and stores the unit price for that product in that book; without entries, the Price Book contains no priced products. It also requires Product records (option B), since every Price Book Entry must reference a Product2, and the product supplies the item being priced and sold. Order records (option C) are transactional documents created after products and prices exist, so they are not components of a Price Book.

Campaign records (option D) belong to marketing functionality and have no relationship to Price Book structure. Lead records (option E) are pre-opportunity prospects and are unrelated to defining a Price Book.

Exam trap

Sales-Con-201 often tests the misconception that a Price Book only needs Product records, forgetting that Price Book Entries are the actual link that stores pricing and are mandatory for the price book to be usable.

Practice this question →
18
MCQmedium

A sales manager at Ursa Major Solar needs to ensure that when an Opportunity is created from an accepted Lead, specific custom Lead fields (e.g., Budget__c and Timeline__c) automatically populate the corresponding custom Opportunity fields. What is the most efficient declarative method to achieve this?

A.Use Lead Settings in Setup to map standard and custom Lead fields to Opportunity fields.
B.Configure a Process Builder to update the converted Opportunity upon creation.
C.Create a Record-Triggered Flow on the Opportunity object to look up the related Lead.
D.Write an Apex trigger on Lead conversion to copy field values.
AnswerA

Lead Settings provides native field mapping that transfers standard and custom Lead values, including Budget__c and Timeline__c, onto the Opportunity during conversion. This is declarative, requires no code, and runs automatically, making it the most efficient method.

Why this answer

Lead Settings in Setup includes a field mapping section that lets admins map standard and custom Lead fields to standard and custom Account, Contact, and Opportunity fields. When a Lead is converted, these mappings automatically populate the target records, making it the most efficient declarative method without automation.

Exam trap

Sales-Con-201 often tests whether candidates choose declarative built-in mapping over custom automation; the trap is picking Process Builder or Flow when Lead Settings mapping already solves it natively.

How to eliminate wrong answers

Option B is wrong because Process Builder would require custom logic and does not natively handle the conversion event as cleanly as built-in field mapping. Option C is wrong because a Record-Triggered Flow on Opportunity would need to query back to the Lead and adds unnecessary complexity. Option D is wrong because an Apex trigger is code-based, not declarative, and is overkill for simple field mapping.

Practice this question →
19
MCQeasy

,A sales representative creates a new contact and associates it with an existing account. Which address field behavior occurs by default on the contact record?

A.The contact mailing address automatically populates from the account billing address.
B.The contact mailing address remains blank until manually entered.
C.The contact address is locked to match the account shipping address.
D.The contact inherits the account phone number and address simultaneously.
AnswerB

Contact address fields are independent of the parent account; Salesforce does not inherit or copy the account billing or shipping address onto a new contact. The mailing address stays blank until a user enters it manually or automation populates it.

Why this answer

By default, when a contact is created and associated with an account, the contact's mailing address fields remain blank — Salesforce does not automatically copy the account's billing or shipping address to the contact. The user must manually enter the contact address or use a formula/flow to populate it. This is standard out-of-the-box behavior on the Contact object.

Exam trap

The trap is assuming Salesforce auto-populates related fields (like contact address from account) by default — candidates often confuse convenience features with actual out-of-the-box behavior, when in fact most cross-object field population requires customization.

How to eliminate wrong answers

Option A is wrong because Salesforce does not auto-populate contact mailing address from account billing address by default — this would require a custom formula field, Flow, or Apex trigger. Option C is wrong because there is no default locking mechanism tying contact address to account shipping address; contacts and accounts maintain independent address fields. Option D is wrong because the contact does not inherit the account phone number or address simultaneously — phone and address fields on Contact are independent and blank by default.

Practice this question →
20
MCQmedium

A company wants to ensure that all users have access to a specific report folder. How is this managed?

A.Public groups only.
B.Sharing rules.
C.Profile permissions.
D.Folder sharing settings.
AnswerD

Folder sharing settings govern which users or groups can access a report folder, letting the company grant access to the specific folder for all users. This directly satisfies the requirement that everyone reach that folder.

Why this answer

Folder sharing settings control access to report and dashboard folders in Salesforce. To ensure all users have access to a specific report folder, an admin configures the folder's sharing settings to grant access to all users or to specific groups/roles. This is the native mechanism for managing report folder visibility, distinct from record-level sharing rules or profile permissions.

Exam trap

Sales-Con-201 often tests the confusion between record-level sharing mechanisms (sharing rules, role hierarchy) and folder-level sharing, causing candidates to pick 'Sharing rules' when the question specifically asks about report folders.

How to eliminate wrong answers

Option A is wrong because public groups are only a means of grouping users for sharing; they do not themselves grant folder access without being referenced in folder sharing settings. Option B is wrong because sharing rules apply to records (e.g., accounts, opportunities), not to report folders. Option C is wrong because profile permissions control object and field-level access and system permissions, but do not directly control report folder visibility.

Practice this question →
21
MCQmedium

A company uses a complex sales process where Sales Representatives must involve different internal stakeholders at specific stages of the Opportunity lifecycle. The management needs to track the contribution of these stakeholders for commission purposes. What should the consultant implement?

A.Account Teams
B.Opportunity Teams
C.Case Teams
D.Opportunity Splits
AnswerB

Opportunity Teams let you add internal stakeholders as team members with defined roles, so their involvement at each sales stage is recorded against the Opportunity and can drive commission attribution. This directly satisfies the requirement to track stakeholder contribution across the lifecycle.

Why this answer

Opportunity Teams allow adding multiple users to an opportunity to track roles and share access, which is ideal for multi-stakeholder sales.

Practice this question →
22
MCQmedium

An organization uses Campaigns to track marketing efforts. A manager needs a report showing which Campaigns have generated the most closed-won Opportunities. What is the primary object that links these?

A.Opportunity Contact Role.
B.Account-Campaign mapping.
C.Lead Conversion.
D.Campaign Influence.
AnswerD

Campaign Influence records link Campaigns to Opportunities, attributing revenue credit to the campaigns that touched a deal. This satisfies the requirement to report which Campaigns generated the most closed-won Opportunities, since influence records persist after the Opportunity closes and can be aggregated by Campaign.

Why this answer

Campaign Influence is the primary object that links Campaigns to Opportunities, allowing reporting on which Campaigns have generated closed-won Opportunities. It tracks the influence of campaigns on opportunity revenue.

Exam trap

Sales-Con-201 often tests the confusion between objects that link Campaigns to Opportunities, with candidates selecting Opportunity Contact Role or Lead Conversion, rather than Campaign Influence.

How to eliminate wrong answers

Option A is wrong because Opportunity Contact Role links Contacts to Opportunities, not Campaigns. Option B is wrong because there is no standard 'Account-Campaign mapping' object; Accounts relate to Campaigns via Campaign Members. Option C is wrong because Lead Conversion creates Accounts, Contacts, and Opportunities from Leads, but does not directly link Campaigns to Opportunities for reporting.

Practice this question →
23
MCQmedium

A sales organization has multiple currencies enabled. A Sales Rep is trying to add a product to an Opportunity, but cannot find the desired product in the Price Book. What is the most likely cause?

A.The Product is not added to the specific Price Book with an entry for the Opportunity's currency
B.The User lacks permission to view the Price Book
C.The Opportunity stage is set to Closed Won
D.The Product is not active
AnswerA

Products appear in an Opportunity's Price Book selection only when a Price Book Entry exists linking that product to the Price Book in the Opportunity's currency. Without that entry, the product is invisible, which explains why the rep cannot find it.

Why this answer

When multiple currencies are enabled, a Product must have a Price Book Entry (PBE) for the specific Price Book AND for the Opportunity's currency. If the PBE exists only in a different currency, the product will not appear when adding products to that Opportunity. This is the most common cause of a missing product in a multi-currency org.

Exam trap

The trap is assuming a permissions or active-status issue when the real cause in multi-currency orgs is a missing Price Book Entry for the Opportunity's currency.

How to eliminate wrong answers

Option B is wrong because if the user lacked Price Book access, they would not be able to view the Price Book at all, and the error would be a permissions/visibility issue rather than a missing product in the selector. Option C is wrong because Opportunity stage (even Closed Won) does not prevent adding products; products can be added to closed opportunities unless a validation rule blocks it. Option D is wrong because an inactive Product would be missing from all Price Books, not just the one matching the Opportunity's currency; the scenario specifically points to a currency mismatch.

Practice this question →
24
MCQmedium

An administrator is setting up Collaborative Forecasts. Which object can be used to configure forecast types in Sales Cloud?

A.Order and Contract.
B.Opportunity, Opportunity Product, or Opportunity Split.
C.Account, Contact, and Lead.
D.Campaign and Quote.
AnswerB

Forecast types are configured from Opportunity, Opportunity Product or Opportunity Split, letting forecasts roll up by product family or split owner. This satisfies the stem's requirement to select a supported object when defining forecast types.

Why this answer

Collaborative Forecasts in Sales Cloud allow forecast types to be configured based on the Opportunity object, Opportunity Product, or Opportunity Split. These are the only objects that carry the revenue, quantity, and split data needed for forecast rollups. This enables organizations to forecast by product line or by team member contribution.

Exam trap

Sales-Con-201 often tests whether candidates know the exact objects available for forecast types — the trap is assuming any revenue-related object (like Quote or Order) can be used, when only Opportunity, Opportunity Product, and Opportunity Split are supported.

How to eliminate wrong answers

Option A is wrong because Order and Contract objects represent post-close transactions and are not used for pipeline forecasting in Collaborative Forecasts. Option C is wrong because Account, Contact, and Lead are pre-opportunity objects and do not carry forecastable revenue data. Option D is wrong because Campaign and Quote are marketing and quoting objects, not forecastable pipeline objects in Collaborative Forecasts.

Practice this question →
25
Multi-Selecthard

An organization uses Enterprise Territory Management. Which THREE actions can be performed using territory rules? (Choose three.)

Select 3 answers
A.Manually run territory rules for a model to re-evaluate all accounts in the model.
B.Automatically assign users to territories based on user profile attributes.
C.Automatically convert leads upon meeting territory assignment criteria.
D.Automatically assign accounts to territories based on account field values.
E.Evaluate rules upon account creation and when an account is edited matching rule criteria.
AnswersA, D, E

Territory rules can be run on demand for a model, letting administrators re-evaluate every account against current rule criteria outside the scheduled assignment cycle. This satisfies the requirement to refresh assignments manually after rule or hierarchy changes.

Why this answer

Option A is correct because in Enterprise Territory Management an administrator can manually run territory rules for a model (from the model's detail page, e.g., 'Run Rules') to re-evaluate and reassign all accounts in that model, which is useful after changing rule criteria or territory structure. Option D is correct because territory rules are built on account field criteria (such as BillingCountry, Industry, or custom account fields) and automatically assign accounts to the appropriate territories when those field values match the rule conditions. Option E is correct because, once rules are active, the system evaluates them on account creation and on account edits that match the rule criteria, so assignments stay current without a manual run.

Option B is not correct because territory rules assign accounts, not users; user membership in territories is handled through territory assignment (e.g., assignment rules based on user role, or manual assignment), not account-based territory rules. Option C is not correct because territory rules do not convert leads; lead conversion is a separate process and is not triggered by territory assignment criteria.

Exam trap

Sales-Con-201 often tests the distinction between territory rules (account assignment based on account fields) and user assignment — candidates may incorrectly believe territory rules assign users to territories based on profile attributes.

Practice this question →
26
MCQhard

A customer requires that the 'Discount' field on the Quote line item be restricted so that it cannot exceed 20%. Which feature should be used to enforce this constraint?

A.Workflow Rule
B.Approval Process
C.Roll-up Summary Field
D.Validation Rule
AnswerD

Validation Rules evaluate field values against defined criteria before a record saves, blocking any Discount entry above 20% and displaying a custom error message. This directly enforces the stem's hard ceiling on the Quote line item, unlike client-side scripting or field-level security, which cannot reliably prevent the over-limit value from persisting.

Why this answer

A Validation Rule is used to enforce data integrity by preventing records from being saved if they violate specified conditions. To restrict the Discount field on a Quote Line Item to not exceed 20%, a validation rule with a formula like Discount > 0.20 would trigger an error message when the condition is met, effectively enforcing the constraint.

Exam trap

Sales-Con-201 often tests the difference between validation rules and other automation tools, and candidates may incorrectly choose Approval Processes or Workflow Rules for enforcing constraints, not realizing that only validation rules can prevent saving.

How to eliminate wrong answers

Option A is wrong because a Workflow Rule can perform actions like field updates or email alerts based on criteria, but it cannot prevent a record from being saved; it runs after the record is saved. Option B is wrong because an Approval Process is for managing approvals, not for enforcing field-level constraints; it could be used to require approval for discounts over 20%, but it does not prevent the entry of such discounts. Option C is wrong because a Roll-up Summary Field aggregates data from related records, not for validating individual field values.

Practice this question →
27
Multi-Selectmedium

An administrator is setting up Lead Assignment Rules for inbound web leads. Which TWO criteria types are available when defining assignment rule entries? (Choose two.)

Select 2 answers
A.Criteria are met (Standard field operator comparisons).
B.Assigned user's role hierarchy depth.
C.A formula evaluates to true.
D.Chatter post sentiment analysis score.
E.Direct integration with Einstein Lead Scoring threshold.
AnswersA, C

The 'criteria are met' entry type evaluates standard field operator comparisons, such as Country equals United Kingdom, to determine whether a rule entry fires. This is one of the two available criteria types for defining lead assignment rule entries.

Why this answer

Option A, 'Criteria are met (Standard field operator comparisons),' is correct because Lead Assignment Rule entries in Salesforce are built on filter criteria that compare standard or custom lead fields using operators such as equals, not equal to, contains, starts with, and greater than, allowing the rule to fire when those field-based conditions are satisfied. Option C, 'A formula evaluates to true,' is also correct because assignment rule entries support formula criteria, where an administrator writes a Boolean formula referencing lead fields and the entry executes when that formula returns true. The other options are not valid criteria types for assignment rule entries: role hierarchy depth (B) is not an available filter, Chatter sentiment analysis (D) is not a supported assignment criterion, and Einstein Lead Scoring thresholds (E) are not directly selectable as assignment rule entry criteria.

Practice this question →
28
Multi-Selecthard

Which THREE factors affect whether a user can convert a Lead in Sales Cloud? (Choose three.)

Select 3 answers
A.The user has the 'Convert Leads' user permission enabled in their profile or permission set.
B.The Lead has at least one associated Task in the Activity timeline.
C.The Lead's email address matches an existing Contact in the database.
D.The Lead is not currently locked in an active Approval Process.
E.The user has Read and Edit access to the Lead record and target objects.
AnswersA, D, E

The 'Convert Leads' user permission is a hard prerequisite; without it, the Convert button is unavailable regardless of record access or field-level security. Enabling it via profile or permission set satisfies the stem's requirement, since conversion is gated by this explicit permission before any other factor applies.

Why this answer

Option A is correct because the 'Convert Leads' user permission must be enabled on the user's profile or a permission set; without it, the Convert button is unavailable regardless of record access. Option D is correct because a Lead that is locked in an active Approval Process cannot be converted until the approval process is recalled, rejected, or otherwise completed and the record is unlocked. Option E is correct because the user needs Read and Edit access to the Lead record itself as well as the target objects (Account, Contact, Opportunity) to create and map records during conversion.

Option B is incorrect because having an associated Task is not a requirement for conversion; activities are simply carried over or optionally not carried over. Option C is incorrect because a matching email address does not block conversion; instead, Salesforce may prompt the user to merge or associate the Lead with the existing Contact during conversion.

Exam trap

Sales-Con-201 often tests lead conversion prerequisites, and the trap is selecting plausible-sounding but non-required conditions (associated tasks, matching email) instead of the actual permission and record-lock factors that govern conversion.

Practice this question →
29
MCQeasy

Universal Containers wants sales reps to track whether an email interaction with a Lead was positive, neutral, or negative. Which feature should the administrator configure to capture this specific qualitative data on the standard Task object?

A.Create a custom picklist field on the Task object.
B.Modify the standard Subject field to be a dependent picklist.
C.Enable Opportunity Scoring in Einstein to categorize task outcomes.
D.Enable Email-to-Case to automatically score inbound email sentiment.
AnswerA

A custom picklist field on Task offers defined values (positive, neutral, negative), capturing qualitative sentiment directly on the standard Task record without custom objects. This satisfies the stem's requirement to track sentiment against email interactions.

Why this answer

To capture qualitative sentiment (positive/neutral/negative) on the standard Task object, the administrator should create a custom picklist field on Task. Custom fields extend standard objects without altering their core schema, and a picklist enforces consistent values for reporting and filtering. This is the standard declarative approach for capturing structured qualitative data.

Exam trap

The trap is assuming standard fields like Subject can be repurposed or that Einstein/Email-to-Case provide sentiment analysis out of the box — Salesforce requires a custom field for this kind of structured qualitative capture.

How to eliminate wrong answers

Option B is wrong because the standard Subject field on Task is a free-text field and cannot be converted to a dependent picklist — standard field data types are immutable in Salesforce. Option C is wrong because Einstein Opportunity Scoring predicts likelihood to close on Opportunities, not sentiment categorization on Tasks. Option D is wrong because Email-to-Case converts inbound emails into Cases and has no sentiment scoring capability — it's a case routing tool, not a sentiment analysis engine.

Practice this question →
30
MCQmedium

What is the purpose of an 'Opportunity Stage' probability percentage?

A.To define the discount percentage.
B.To forecast revenue in the pipeline.
C.To determine lead score.
D.To set the owner of the record.
AnswerB

The stage probability percentage weights each open opportunity's value by its likelihood of closing, producing a weighted pipeline forecast. This satisfies the stem's forecasting purpose, letting sales leaders project expected revenue rather than merely tracking deal counts.

Why this answer

The Opportunity Stage probability percentage is tied to the sales stage and represents the likelihood of closing the deal, which feeds directly into pipeline forecasting. Salesforce uses this percentage multiplied by the opportunity amount to calculate expected revenue in Collaborative Forecasts and pipeline reports. This allows sales managers to project realistic revenue based on where deals sit in the sales process.

Exam trap

Sales-Con-201 often tests whether candidates confuse stage probability with discount, lead score, or ownership — the trap is assuming probability serves a configuration purpose rather than a forecasting purpose.

How to eliminate wrong answers

Option A is wrong because discount percentages are configured separately on products, price books, or via custom fields — they are not derived from Opportunity Stage. Option C is wrong because lead scores are calculated from lead scoring models based on demographic and behavioral data, not from opportunity stage probability. Option D is wrong because record ownership is assigned through sharing rules, role hierarchy, or manual reassignment, and has no relationship to stage probability.

Practice this question →
31
MCQmedium

A company uses 'Orders' to track fulfillment. What object must be linked to an Order to track the products sold?

A.Account.
B.Price Book.
C.Order Product.
D.Opportunity.
AnswerC

Order Product is the junction object linking an Order to the Products sold, capturing quantity, unit price and line-level detail. Linking it satisfies the stem's requirement to track which products were sold against a given Order.

Why this answer

The Order Product object (also known as OrderItem) is the junction object that links an Order to the Products being sold. It stores the quantity, unit price, and total price for each product on the order. Without Order Products, an Order cannot track which products were sold.

Exam trap

The trap is confusing the Price Book (catalog) with the Order Product (line item); candidates may pick Price Book thinking it links products to orders, but it only defines available products and prices.

How to eliminate wrong answers

Option A is wrong because Account is the customer entity associated with the Order, not the product line items. Option B is wrong because Price Book is a catalog of products and prices; it is referenced by Order Products but does not itself link products to a specific order. Option D is wrong because Opportunity represents a potential sale, not the fulfilled order; while Orders can be created from Opportunities, the product tracking on an Order is done via Order Products.

Practice this question →
32
Multi-Selecthard

Which TWO settings affect the access a user has to an Opportunity?

Select 2 answers
A.Sharing Rules.
B.Organization-Wide Default (OWD).
C.Page Layout.
D.Task status.
E.Validation Rules.
AnswersA, B

Sharing Rules open up record access beyond the organisation-wide default by granting read or edit rights to specified users, roles or territories. For Opportunities, this directly widens a user's access where the default is too restrictive, satisfying the stem's requirement for a setting that affects Opportunity access.

Why this answer

Sharing Rules (A) are correct because they grant additional access to records—such as Opportunities—beyond the Organization-Wide Default by opening up access for specified roles, groups, or territories via criteria-based or owner-based rules. Organization-Wide Default (B) is correct because the OWD for Opportunity sets the baseline (most restrictive) level of access users have to Opportunity records they do not own, which sharing rules, role hierarchy, and manual sharing can then extend. Page Layout (C) only controls the arrangement and visibility of fields, buttons, and related lists on the record detail page; it does not grant or restrict record-level access.

Task status (D) is merely a picklist value on the Activity object and has no bearing on Opportunity record access. Validation Rules (E) enforce data quality by preventing saves that violate defined criteria; they do not determine which users can view or edit an Opportunity.

Exam trap

Sales-Con-201 often tests the misconception that Page Layout or field-level security controls record access — candidates confuse 'what you see on the page' with 'whether you can open the record at all.'

Practice this question →
33
Multi-Selectmedium

Which TWO items are commonly managed in a Price Book?

Select 2 answers
A.Prices.
B.Campaigns.
C.Products.
D.Leads.
E.Contacts.
AnswersA, C

Prices are a core Price Book entry, letting administrators define region- or currency-specific list prices that feed quote and opportunity line items. This satisfies the scenario's requirement to manage pricing data centrally, since the Price Book governs which price applies per product and market.

Why this answer

A Price Book is a Salesforce CPQ object that stores pricing information, so option A (Prices) is correct because it holds the price entries (PricebookEntry records) that define the selling price of each product for a given currency and price book. Option C (Products) is also correct because a Price Book associates products with their prices, meaning products must be added to the price book to be sellable. Options B (Campaigns), D (Leads), and E (Contacts) are incorrect because these are CRM marketing and sales objects managed outside the Price Book, not items commonly managed within it.

Exam trap

Sales-Con-201 often tests the distinction between objects that are directly managed within a Price Book (Products and Prices) versus those that are merely related to sales processes (Campaigns, Leads, Contacts).

Practice this question →
34
MCQmedium

A Sales Rep needs to see all tasks related to the Accounts they own. Where should they look?

A.Activity Timeline on the Account.
B.Opportunity stage report.
C.Lead Conversion report.
D.Contact role list.
AnswerA

The Activity Timeline on the Account record surfaces tasks, events and logged calls related to that account in one chronological view. Since the rep owns the account, opening it shows every related activity without building reports or filtering list views manually.

Why this answer

The Activity Timeline on the Account record displays all activities (tasks, events, emails, calls) related to that Account and its related records in a unified chronological view. Since the Sales Rep owns the Accounts, they can open each Account and see every associated task directly in the Activity Timeline component. This is the native, intended way to review all account-related activities.

Exam trap

The trap here is confusing activity visibility with reporting — candidates often pick a report when the question is about viewing tasks on a specific record, where the Activity Timeline is the correct native component.

How to eliminate wrong answers

Option B is wrong because an Opportunity stage report shows pipeline data grouped by stage, not the tasks associated with Accounts. Option C is wrong because a Lead Conversion report tracks Lead-to-Account/Contact/Opportunity conversion metrics, not task activity. Option D is wrong because the Contact role list shows the roles Contacts play on Opportunities (e.g., Decision Maker), which has nothing to do with viewing tasks.

Practice this question →
35
MCQmedium

A company wants to ensure that all 'Contacts' have an email address before they are saved. What feature should be used?

A.Validation Rule.
B.Assignment Rule.
C.Sharing Rule.
D.Workflow Rule.
AnswerA

A validation rule evaluates the Email field on save and blocks the record when it is blank, enforcing the mandatory email constraint at data-entry time. It fires on the Contact object itself, so no contact can be saved without an address.

Why this answer

Validation Rules in Salesforce enforce data integrity by evaluating a formula whenever a record is created or edited, and blocking the save if the condition is met. To require an email address on Contacts, you would create a rule with a formula like ISBLANK(Email) and an error message, which prevents saving until the field is populated. This is the standard declarative mechanism for field-level data quality enforcement.

Exam trap

Sales-Con-201 often tests the confusion between automation rules that act after save (Workflow, Assignment) and validation rules that block the save — candidates pick Workflow Rule because it sounds like it enforces a process, but only Validation Rules can prevent saving.

How to eliminate wrong answers

Option B is wrong because Assignment Rules only automatically assign ownership of new Leads or Cases to users or queues; they have no bearing on field validation. Option C is wrong because Sharing Rules extend record-level access to groups of users and cannot enforce field requirements. Option D is wrong because Workflow Rules perform automated actions (field updates, email alerts, tasks) after a record is saved, and they cannot block a save or enforce required fields.

Practice this question →
36
MCQeasy

Which object represents the individual person associated with an Account?

A.Account.
B.Contact.
C.Lead.
D.Opportunity.
AnswerB

Contact stores the individual person's details and is linked to the Account through the Account lookup, making it the object that represents a person rather than a business. One account can therefore hold many related contacts.

Why this answer

The Contact object in Salesforce is designed to store information about individual people, such as name, email, phone, and title. Contacts are always associated with an Account (unless they are personal contacts), and they represent the people you do business with. Therefore, Contact is the correct answer because it directly models the individual person linked to an Account.

Exam trap

Sales-Con-201 often tests the distinction between Account, Contact, Lead, and Opportunity, and candidates may confuse Lead with Contact because both represent people, but Lead is pre-qualification and not yet associated with an Account.

How to eliminate wrong answers

Option A is wrong because Account represents a company or organization, not an individual person. Option C is wrong because Lead represents a potential customer who has not yet been qualified, and it is not associated with an Account until converted. Option D is wrong because Opportunity represents a potential sale or deal, not a person.

Practice this question →
37
MCQhard

A Sales manager wants to report on the progress of sales cycles. They notice that the 'Stage' field is not accurately reflecting the actual sales duration. Which feature should be used to enforce specific stages based on opportunity probability?

A.Flow Builder.
B.Sales Processes.
C.Validation Rules.
D.Opportunity Teams.
AnswerB

Sales Processes define stage rules tied to opportunity probability, so stages advance only when the probability threshold is met. This enforces accurate stage progression and duration tracking, directly correcting the 'Stage' field that misreports actual sales cycle length.

Why this answer

Sales Processes allow an administrator to define which stages are available for a given record type and map each stage to a specific probability. This enforces a consistent sales cycle and ensures the Stage field accurately reflects the sales methodology. By restricting stages per record type, Sales Processes prevent users from selecting stages that don't align with the defined probability model.

Exam trap

The trap is assuming Flow Builder or Validation Rules can enforce stage-probability mapping; candidates overlook that Sales Processes are the native declarative tool for defining stage sets and probabilities per record type.

How to eliminate wrong answers

Option A is wrong because Flow Builder automates actions and can update fields, but it does not define or enforce the set of available stage values tied to probability — that is the role of Sales Processes. Option C is wrong because Validation Rules enforce data integrity conditions (e.g., required fields) but cannot define the stage-to-probability mapping or restrict picklist values by record type. Option D is wrong because Opportunity Teams manage the team of users working on an opportunity, not the sales stage progression or probability mapping.

Practice this question →
38
MCQmedium

What is the purpose of 'Opportunity Splits'?

A.To split the opportunity into multiple records.
B.To allocate revenue percentage to multiple team members.
C.To create multiple orders.
D.To divide the work among team members.
AnswerB

Opportunity Splits distribute a single opportunity's revenue across several team members by assigning each a percentage, so individual quotas and credit reflect their contribution. This directly satisfies the stem's requirement to allocate revenue percentage among multiple people, unlike territory or product-based assignment, which routes whole opportunities rather than dividing their value.

Why this answer

Opportunity Splits allow you to allocate credit for an opportunity's revenue among multiple users, typically team members, by assigning a percentage to each. This is used for commission and reporting purposes, ensuring that multiple contributors receive recognition for a deal. The splits can be based on revenue or overlay, and they sum to 100%.

Exam trap

Sales-Con-201 often tests the misconception that Opportunity Splits divide the opportunity into multiple records or divide work, when they actually allocate revenue credit percentages among team members.

How to eliminate wrong answers

Option A is wrong because Opportunity Splits do not create multiple opportunity records; they distribute credit within a single opportunity. Option C is wrong because creating multiple orders is unrelated to splits; orders are separate objects generated from opportunities. Option D is wrong because dividing work among team members is a project management concept, not the purpose of Opportunity Splits, which is about revenue credit allocation.

Practice this question →
39
MCQmedium

How can a Sales Rep provide a quote to a customer directly from an Opportunity?

A.By emailing the Opportunity.
B.By creating a new Account.
C.By using the 'New' button on the Quote related list.
D.By converting a Lead.
AnswerC

The Quotes related list on an Opportunity exposes a New button that creates a quote pre-linked to that opportunity, inheriting its account and price book. This lets the rep generate the customer quote directly from the opportunity record.

Why this answer

Quotes are created from an Opportunity via the Quotes related list using the 'New' button, which launches the quote creation flow tied to that opportunity's products and price book. This is the standard path for generating a customer-facing quote directly from the opportunity record.

Exam trap

The trap is overcomplicating the answer; Sales-Con-201 tests whether candidates know quotes are created from the Opportunity's Quote related list, not via email or lead conversion.

How to eliminate wrong answers

Option A is wrong because emailing the Opportunity does not generate a quote; it sends a record link or template, not a priced quote document. Option B is wrong because creating a new Account is unrelated to quoting and does not produce a quote record. Option D is wrong because converting a Lead creates Account, Contact, and Opportunity records, not a quote.

Practice this question →
40
MCQhard

A company needs to track the 'Source' of their revenue. They have multiple campaigns. What is the most effective way to allocate revenue to these campaigns?

A.Use Campaign Influence to associate multiple campaigns with an Opportunity.
B.Use the 'Lead Source' field only.
C.Only assign one primary campaign per opportunity.
D.Create a custom field for every campaign.
AnswerA

Campaign Influence links several campaigns to one opportunity, letting each campaign claim a weighted share of the resulting revenue. This satisfies the requirement to allocate revenue across multiple campaigns by attributing influence percentages, rather than forcing a single source onto the opportunity.

Why this answer

Campaign Influence allows multiple campaigns to be associated with a single Opportunity, enabling accurate revenue attribution when a customer interacts with several campaigns before converting. This is the most effective way to track revenue source because it captures the multi-touch nature of modern sales cycles. It provides both primary and non-primary campaign attribution.

Exam trap

The trap is thinking a single Lead Source or primary campaign is sufficient for revenue attribution; candidates underestimate the need for multi-touch attribution that Campaign Influence provides.

How to eliminate wrong answers

Option B is wrong because the Lead Source field only captures a single source and cannot represent multiple campaign touches or allocate revenue across campaigns. Option C is wrong because restricting to one primary campaign per opportunity ignores the reality that buyers often engage with multiple campaigns, leading to incomplete attribution. Option D is wrong because creating a custom field for every campaign is unscalable, error-prone, and does not leverage Salesforce's native attribution model.

Practice this question →
41
MCQeasy

What is the purpose of the 'Lead Conversion' process?

A.To create an Account, Contact, and Opportunity from a Lead.
B.To change the Lead status to 'Closed'.
C.To merge two duplicate leads.
D.To archive old leads.
AnswerA

Lead conversion maps the lead's captured data into an Account, Contact, and optionally an Opportunity, preserving the record through the sales funnel. This satisfies the process purpose by transitioning a qualified prospect into the objects Sales Cloud uses for ongoing account management and pipeline tracking.

Why this answer

Lead Conversion transforms a qualified Lead into an Account, Contact, and optionally an Opportunity, carrying over mapped fields and preserving the lead as a converted record. This is the standard process for moving a prospect into the sales pipeline as a full customer record.

Exam trap

Sales-Con-201 often tests whether candidates know conversion creates Account, Contact, and Opportunity; the trap is picking status change or merge as the purpose of Lead Conversion.

How to eliminate wrong answers

Option B is wrong because changing Lead status to 'Closed' is a status update, not conversion, and does not create Account/Contact/Opportunity records. Option C is wrong because merging duplicate leads is a deduplication action, not conversion. Option D is wrong because archiving old leads is a data management task, not the conversion process.

Practice this question →
42
MCQmedium

A customer wants to capture information from their website into Salesforce as a Lead. Which tool is best for this?

A.Email-to-Case.
B.Web-to-Lead.
C.AppExchange App.
D.Salesforce Connect.
AnswerB

Web-to-Lead generates an HTML form that posts submissions directly into Salesforce, creating Lead records automatically without manual entry or middleware. It satisfies the requirement to capture website visitor information as Leads, using Salesforce's native, no-code capture mechanism rather than custom integration or external tooling.

Why this answer

Web-to-Lead is the native Salesforce feature purpose-built to capture website form submissions directly into Salesforce as Lead records. It generates HTML form code from Setup that posts to Salesforce's Web-to-Lead endpoint, creating Leads automatically without manual entry or custom code. This is the standard, no-cost solution for the stated requirement.

Exam trap

Sales-Con-201 often tests whether candidates confuse Web-to-Lead with Email-to-Case or Web-to-Case — the trap is picking a support-oriented tool when the requirement is specifically about capturing Leads from a website.

How to eliminate wrong answers

Option A is wrong because Email-to-Case creates Cases from inbound emails, not Leads from web forms — it addresses support workflows, not lead capture. Option C is wrong because while an AppExchange app could theoretically do this, it introduces unnecessary cost and complexity when native Web-to-Lead already satisfies the requirement. Option D is wrong because Salesforce Connect is used for external data virtualization (OData, cross-org), not for capturing website form submissions as Leads.

Practice this question →
43
MCQmedium

A company wants to automatically assign leads to specific Sales Reps based on the Lead's 'Industry' field. What is the best way to achieve this?

A.Validation Rules.
B.Lead Assignment Rules.
C.Workflow Rules.
D.Custom Apex Trigger.
AnswerB

Lead Assignment Rules evaluate field values on the Lead record, such as Industry, and route the lead to the matching user or queue automatically. This satisfies the requirement to assign leads to specific Sales Reps based on the Industry field without manual intervention.

Why this answer

Lead Assignment Rules provide a declarative way to route leads to users or queues based on criteria.

Practice this question →
44
MCQmedium

An administrator at DreamHouse Realty needs to ensure that Quotes generated from an Opportunity always reflect the active Price Book entries. When a sales rep adds a new Quote to an Opportunity, what dictates the available Products and prices?

A.The Standard Price Book regardless of the Opportunity Price Book.
B.The user profile permissions governing Price Book access.
C.A global price book assignment rule defined in Setup.
D.The Price Book selected on the Opportunity record.
AnswerD

The Price Book selected on the Opportunity determines which products and prices populate any Quote created from it. This ensures quotes always reflect active Price Book entries, since the Opportunity's chosen book governs the available line items rather than the rep's manual selection.

Why this answer

The Price Book associated with the Opportunity dictates the available products and pricing for associated quotes.

Practice this question →
45
MCQmedium

A sales representative needs to apply a different Price Book to an existing Opportunity that already contains line items. What happens to the existing opportunity products when the Price Book is changed?

A.The system prevents changing the price book if line items exist.
B.They are removed from the opportunity, and products from the new price book must be added manually.
C.They remain on the opportunity, but are marked as inactive.
D.They are automatically updated with prices from the new price book.
AnswerB

Changing an opportunity's price book invalidates existing line items because each references products priced within the original book. Salesforce therefore deletes them, and the rep must re-add products from the newly selected price book manually, satisfying the stem's existing-line-items scenario.

Why this answer

When you change the Price Book on an Opportunity that already has line items, Salesforce removes all existing Opportunity Line Items. This is because the products must be associated with the new Price Book, and existing line items may not exist in the new Price Book. You must then manually add products from the new Price Book.

Exam trap

The trap is assuming line items are preserved or updated; the exam expects you to know they are deleted, requiring manual re-entry.

How to eliminate wrong answers

Option A is wrong because the system does not prevent changing the Price Book; it allows it but with consequences. Option C is wrong because line items are not marked inactive; they are deleted. Option D is wrong because prices are not automatically updated; the line items are removed entirely.

Practice this question →
46
MCQeasy

During lead qualification, a sales user wants to send a standardized email to a lead. Where can the user initiate this action directly within the standard Sales Cloud user interface?

A.Only from the Reports tab.
B.From the Lead Conversion window.
C.From the Campaign Member status history.
D.From the Activity timeline on the Lead record.
AnswerD

The Lead record's Activity timeline exposes the Email action directly, letting the user compose and send a standardised email without leaving the record. This satisfies the requirement to initiate the action within the standard Sales Cloud interface.

Why this answer

The Activity timeline or Global Actions / Send Email action on the Lead record.

Practice this question →
47
Multi-Selectmedium

Which THREE fields are standard on an Opportunity?

Select 3 answers
A.Stage.
B.Discount.
C.Close Date.
D.Opportunity Name.
E.Lead Source.
AnswersA, C, D

Stage is a standard picklist field on Opportunity, tracking progression through sales phases such as Prospecting, Qualification and Closed Won. It is a required field in the standard model, satisfying the stem's request for one of three standard Opportunity fields.

Why this answer

The three standard fields on an Opportunity are Stage (A), Close Date (C), and Opportunity Name (D). Stage is a required standard picklist that tracks the sales process phase (e.g., Prospecting, Qualification, Closed Won), making it fundamental to every Opportunity record. Close Date is a required standard date field representing the expected or actual date the opportunity will close, and it drives forecasting.

Opportunity Name is a required standard text field that identifies the deal, so it appears on every Opportunity by default. Discount (B) is not a standard Opportunity field; it is typically a custom field or part of a product/quote line item. Lead Source (E) is a standard field on the Lead object, not on the Opportunity object, so it does not belong here.

Exam trap

Sales-Con-201 often tests the distinction between standard fields on different objects, causing candidates to confuse Lead fields with Opportunity fields or assume common business terms like Discount are standard.

Practice this question →
48
MCQhard

An organization has strict compliance requirements. Sales reps should only be able to view contacts associated with accounts they own, but contacts should inherit sharing from the parent account. What should the Contact OWD setting be?

A.Controlled by Parent
B.Public Read/Write/Transfer
C.Public Read Only
D.Private
AnswerA

Controlled by Parent makes contact sharing inherit directly from the associated account, so reps see only contacts on accounts they own. This satisfies the compliance constraint requiring ownership-based visibility while preserving inheritance, unlike Private, which would need manual sharing rules.

Why this answer

Setting Contact OWD to 'Controlled by Parent' makes contact access inherit from the parent Account's sharing settings. This ensures sales reps can only view contacts associated with accounts they own, because account ownership drives contact visibility. It satisfies the compliance requirement without granting broader access.

Exam trap

Sales-Con-201 often tests the misconception that 'Private' OWD on Contacts automatically inherits from the parent Account, when in fact only 'Controlled by Parent' provides that inheritance behavior.

How to eliminate wrong answers

Option B is wrong because Public Read/Write/Transfer grants all users broad access to contacts regardless of account ownership, violating the strict compliance requirement. Option C is wrong because Public Read Only allows all users to view all contacts, which is too permissive. Option D is wrong because Private OWD on Contacts does not automatically inherit from the parent Account; it requires manual sharing or other mechanisms, and does not meet the 'inherit sharing from parent account' requirement.

Practice this question →
49
MCQmedium

A Sales Manager wants to ensure that Sales Reps only see Leads that are assigned to them or their subordinates. Which configuration change is required?

A.Create a Permission Set with 'View All' on Leads.
B.Enable Lead Teams.
C.Set the Organization-Wide Default for Leads to Private and utilize the Role Hierarchy.
D.Update the Lead Sharing Rules to Public Read/Write.
AnswerC

Setting the Lead organisation-wide default to Private restricts access to owners plus users above them in the role hierarchy. This satisfies the requirement that reps see only their own leads or those of subordinates, since hierarchy-based access grants managers visibility downward.

Why this answer

Setting the Organization-Wide Default for Leads to Private and utilizing the Role Hierarchy ensures that reps can only see Leads assigned to them or their subordinates. The Role Hierarchy grants managers access to records owned by users below them in the hierarchy, while Private OWD restricts access to everyone else. This is the standard Salesforce sharing model for hierarchical visibility.

Exam trap

Sales-Con-201 often tests whether candidates confuse sharing mechanisms that expand access (Sharing Rules, Teams, Permission Sets) with those that restrict access (Private OWD + Role Hierarchy) — the trap is picking a sharing rule when the requirement is to limit visibility.

How to eliminate wrong answers

Option A is wrong because a Permission Set with 'View All' on Leads would grant unrestricted access to all Leads, which is the opposite of the requirement. Option B is wrong because Lead Teams allow multiple users to collaborate on a single Lead but do not restrict visibility based on hierarchy — they expand access, not limit it. Option D is wrong because Public Read/Write sharing rules would make all Leads visible and editable by all users, violating the requirement for restricted visibility.

Practice this question →
50
MCQeasy

Which object acts as the 'Parent' in a standard Account-Opportunity relationship?

A.Campaign.
B.Contact.
C.Account.
D.Lead.
AnswerC

Account serves as the parent record in the standard Account-Opportunity relationship, with Opportunity as the child. This one-to-many model lets multiple opportunities roll up to a single Account, satisfying the stem's requirement that the Account holds the parent position.

Why this answer

In the standard Salesforce data model, the Account is the parent object in the Account-Opportunity relationship. An Opportunity is always associated with exactly one Account (the 'Account Name' field is required on Opportunity), and that Account is the lookup/master-detail parent. This parent-child link drives roll-up summaries, sharing inheritance, and reporting hierarchies.

Exam trap

Sales-Con-201 often tests the misconception that Contact or Campaign is the parent of Opportunity, when in fact Account is the sole required parent lookup on the Opportunity object.

How to eliminate wrong answers

Option A is wrong because Campaign is a related object linked to Opportunities via Campaign Influence, not a parent in the Account-Opportunity relationship. Option B is wrong because Contact is linked to Opportunities through Contact Roles (a junction object), not as a parent. Option D is wrong because Lead is a separate pre-conversion object that has no parent-child relationship with Opportunity; Leads are converted into Accounts, Contacts, and Opportunities.

Practice this question →
51
MCQeasy

A user needs to see all Leads that were created in the last month. Which feature should they use?

A.Dashboard.
B.Report Builder.
C.List Views.
D.Global Search.
AnswerC

List Views filter records by criteria such as creation date, so a view configured with "Created On = Last Month" shows exactly the Leads the user needs. This satisfies the requirement to see only recently created Leads, without exporting data or building a custom report.

Why this answer

List Views are the standard Salesforce feature for filtering and displaying records of a single object based on criteria such as Created Date. A user can create a Lead list view filtered to 'Created Date equals LAST 30 DAYS' to see all Leads created in the last month. List views are fast, native, and designed exactly for this kind of record browsing.

Exam trap

Sales-Con-201 often tests the distinction between List Views (browse/filter records on one object) and Reports (analyze data across objects) — the trap is choosing Report Builder when the requirement is simple record filtering.

How to eliminate wrong answers

Option A is wrong because a Dashboard visualizes aggregated metrics from source reports; it does not provide a filterable list of individual Lead records. Option B is wrong because Report Builder is used for analytical reporting across objects and is heavier than needed for a simple 'show me recent Leads' view — though it could technically filter by date, it is not the best or intended tool for this browsing use case. Option D is wrong because Global Search returns records matching a search term across objects; it cannot filter by Created Date or return a complete list of Leads from the last month.

Practice this question →
52
MCQeasy

A Sales Rep wants to see all the products associated with their current Opportunity. Where is this information located?

A.Opportunity Products related list.
B.Campaign related list.
C.Activity Timeline.
D.Account related list.
AnswerA

The Opportunity Products related list stores the specific line items linked to an Opportunity, so the Sales Rep sees every product associated with that deal in one place. This directly satisfies the stem's requirement to view all products tied to the current Opportunity, rather than products from other records or the product catalogue.

Why this answer

Products associated with an Opportunity are stored as Opportunity Line Items and displayed in the Opportunity Products related list on the Opportunity record. This related list shows each product, quantity, sales price, and total price for the deal.

Exam trap

Sales-Con-201 often tests related list identification; the trap is confusing Campaign or Activity related lists with the Opportunity Products related list that actually holds line items.

How to eliminate wrong answers

Option B is wrong because the Campaign related list shows campaign influence or membership, not products. Option C is wrong because the Activity Timeline shows tasks, events, and logged calls, not product line items. Option D is wrong because the Account related list shows related accounts (e.g., partners), not products on the opportunity.

Practice this question →
53
MCQhard

A Sales Rep needs to collaborate with a cross-functional team on a specific Opportunity. What is the most efficient way to grant access to the Opportunity for users who are not in the standard Role Hierarchy?

A.Change the Organization-Wide Default to Public Read/Write.
B.Add the users to the Opportunity Team.
C.Create a Public Group and assign it to the Opportunity.
D.Use Apex managed sharing for every Opportunity.
AnswerB

Adding users to the Opportunity Team grants record-level access without altering the shared Role Hierarchy, satisfying the requirement to collaborate on one specific Opportunity. The Opportunity Team is purpose-built for cross-functional collaboration, giving each member a defined access level on that record alone, which is more efficient than creating new roles or reassigning ownership.

Why this answer

Opportunity Teams are the standard, purpose-built feature for granting access to an Opportunity to users outside the role hierarchy. Adding a user to the Opportunity Team with a defined team member role grants them access based on the team member access level, without altering org-wide sharing or requiring code.

Exam trap

Sales-Con-201 often tests the misconception that Public Groups can be directly assigned to records — candidates confuse group-based sharing rules with direct record sharing, but groups only work through sharing rules or manual shares.

How to eliminate wrong answers

Option A is wrong because changing the Organization-Wide Default to Public Read/Write would expose every Opportunity to every user in the org, violating least privilege and creating a massive security regression. Option C is wrong because Public Groups cannot be assigned directly to an Opportunity record — sharing to a group requires a sharing rule, manual share, or team, not direct assignment. Option D is wrong because Apex managed sharing is a programmatic sharing mechanism intended for complex, dynamic sharing requirements; using it for every Opportunity is over-engineered, harder to maintain, and unnecessary when Opportunity Teams already solve the problem declaratively.

Practice this question →
54
MCQeasy

A Sales Manager wants a report that shows all Opportunities that have not had any activity in the last 30 days. Which report type is most suitable?

A.Opportunities and Contacts
B.Campaigns with Opportunities
C.Opportunities with Products
D.Opportunities with Activities
AnswerD

This report type joins Opportunities to their related Activities, so filtering on last-activity date surfaces records with no activity in the trailing 30 days. It satisfies the Sales Manager's requirement for a single report listing dormant Opportunities without manual cross-object reconciliation.

Why this answer

Opportunities with Activities report type allows for filtering based on activity dates.

Practice this question →
55
MCQeasy

Northern Trail Outfitters uses Leads to capture inquiries. A sales rep needs to convert a qualified lead into an account, contact, and opportunity. What standard Salesforce functionality occurs during lead conversion regarding custom lead fields?

A.Custom lead fields are lost upon conversion and must be re-entered manually.
B.Custom lead fields are automatically mapped to all three objects based on field API names.
C.Custom lead fields can be mapped to custom fields on Account, Contact, and Opportunity objects in Lead Settings.
D.Custom lead fields can only be mapped to the Opportunity object.
AnswerC

Custom lead fields map to Account, Contact and Opportunity fields through the Lead Settings mapping page, satisfying the requirement that converted data lands in the right destination fields. Mapping is configured per object, so a single custom lead field can populate a matching custom field on each of the three records created during conversion.

Why this answer

During lead conversion, custom lead fields can be mapped to custom fields on the Account, Contact, and Opportunity objects. This mapping is configured in Lead Settings, allowing administrators to control which fields transfer and to which objects. This ensures data continuity and reduces manual re-entry.

Exam trap

Candidates often assume custom fields map automatically or only to Opportunity; the trap is forgetting that mapping is configurable and can target all three objects.

How to eliminate wrong answers

Option A is wrong because custom lead fields are not lost; they can be mapped if configured. Option B is wrong because mapping is not automatic based on API names; it requires explicit configuration. Option D is wrong because custom lead fields can be mapped to all three objects, not just Opportunity.

Practice this question →
56
MCQhard

A company uses multiple currencies in Sales Cloud. An opportunity is created in EUR, but the corporate currency is USD. Where does Salesforce pull the exchange rate used to calculate the converted amount on corporate reporting?

A.From the custom exchange rate object populated by a nightly batch job.
B.From the user's personal locale and currency settings.
C.From the Price Book entry associated with the opportunity line items.
D.From the Manage Currencies page in Setup, based on active conversion rates.
AnswerD

Salesforce stores dated exchange rates against the corporate currency on the Manage Currencies page in Setup, and conversion for reporting uses the rate active on the opportunity's close date. This satisfies the stem's requirement that a EUR opportunity convert into USD corporate reporting figures using maintained, dated rates rather than a static or user-supplied value.

Why this answer

Salesforce stores corporate currency conversion rates in the Manage Currencies page under Setup, and these active rates are used to convert opportunity amounts into the corporate currency for reporting. The converted amount is calculated using the dated exchange rate effective at the opportunity's close date (if Advanced Currency Management is enabled) or the static rate otherwise.

Exam trap

The trap here is assuming exchange rates come from a custom object or user settings; Sales-Con-201 tests whether candidates know rates live in Setup's Manage Currencies page and that ACM enables dated rates.

How to eliminate wrong answers

Option A is wrong because Salesforce does not use a custom exchange rate object populated by a nightly batch job for standard currency conversion; rates are maintained in Setup. Option B is wrong because user locale and personal currency settings affect display formatting, not the corporate conversion calculation. Option C is wrong because Price Book entries store product prices in the price book's currency, not the exchange rate used to convert opportunity totals to the corporate currency.

Practice this question →
57
MCQeasy

Which object is used to track the interaction history with a prospect during the sales process?

A.Campaign.
B.Opportunity.
C.Activity.
D.Account.
AnswerC

Activities are the records that log every touchpoint with a prospect, including tasks, events and logged calls, so they build the interaction history the sales process requires. Each completed activity is time-stamped against the related lead or contact, giving the chronological trail the stem asks for.

Why this answer

In Salesforce, an Activity is the standard object used to track interactions such as calls, emails, meetings, and tasks related to a prospect or customer. Activities are directly associated with records like Leads, Contacts, and Opportunities, providing a chronological history of engagement. This makes Activity the correct choice for tracking interaction history during the sales process.

Exam trap

Sales-Con-201 often tests the distinction between objects that store transactional data (Opportunity) and those that store interaction data (Activity), causing candidates to overlook Activity as the primary tracking mechanism.

How to eliminate wrong answers

Option A is wrong because a Campaign is used to group and track marketing efforts across multiple leads and contacts, not individual interactions. Option B is wrong because an Opportunity represents a potential sale and its stages, but it does not itself record the granular interaction history; Activities do that. Option D is wrong because an Account is a company or organization record that aggregates related contacts and opportunities, but it does not track individual prospect interactions.

Practice this question →
58
MCQmedium

Which tool is used to automate the update of an Opportunity status when a milestone is reached?

A.Assignment Rules.
B.Workflow Rules.
C.Validation Rules.
D.Flow Builder.
AnswerD

Flow Builder automates record updates by triggering on milestone completion, directly satisfying the requirement to change Opportunity status without manual intervention. Its native Salesforce integration lets a milestone event launch an immediate field update on the Opportunity record, which is precisely the automation the scenario demands.

Why this answer

Flow Builder is the modern tool for complex automation, including status updates.

Practice this question →
59
Multi-Selectmedium

A sales manager wants to analyze pipeline by lead source and needs to ensure that lead source data is captured consistently. Which two actions should a consultant recommend? (Choose two.)

Select 2 answers
A.Convert Leads to Opportunities and ensure the Lead Source field is mapped
B.Set the Lead Source field as read-only on the Opportunity layout
C.Create a validation rule on the Lead object requiring Lead Source
D.Use a formula field on Opportunity to copy the Lead Source from the Campaign
E.Create a workflow rule to update the Opportunity Lead Source based on the owner's role
AnswersA, C

When converting a Lead, the Lead Source field can be mapped to the Opportunity's Lead Source field. This ensures that the source data is carried over consistently. Without mapping, the Opportunity would not inherit the Lead Source, leading to incomplete pipeline analysis. This is a standard best practice for maintaining data continuity.

Why this answer

Enforcing Lead Source at the Lead level with a validation rule ensures data is captured consistently. Mapping the Lead Source during conversion ensures it carries over to Opportunities. Together, these actions provide reliable pipeline analysis by lead source.

Other options either do not enforce capture or introduce inaccurate data.

Exam trap

The trap here is assuming that a formula field or workflow can retroactively populate Lead Source, when the data must be captured at the lead stage and mapped during conversion.

Practice this question →
60
MCQmedium

A company wants to ensure that all Opportunities have a 'Close Date' in the future. What should be used?

A.Sharing Rule.
B.Validation Rule.
C.Workflow Rule.
D.Assignment Rule.
AnswerB

Validation Rules evaluate a formula whenever a record is saved and block the save when the condition fails, so a rule testing Close Date against TODAY() prevents past dates on every Opportunity. This directly enforces the stem's constraint that all Opportunities carry a future Close Date, regardless of entry channel.

Why this answer

A Validation Rule is the correct tool to enforce that the Close Date is in the future. Validation Rules evaluate on save and prevent the record from being saved if the condition is violated, which is exactly the requirement for data integrity. The rule would compare CloseDate to TODAY() and return an error if CloseDate <= TODAY().

Exam trap

The trap is assuming Workflow Rules can enforce data integrity — they cannot block saves. Candidates often pick Workflow Rules because they are familiar automation, but Validation Rules are the only declarative tool that prevents invalid data from being saved.

How to eliminate wrong answers

Option A is wrong because Sharing Rules control record access, not data validation. Option C is wrong because Workflow Rules execute after save and cannot block a save — they can only perform actions like field updates or email alerts. Option D is wrong because Assignment Rules route records to owners and have no validation capability.

Practice this question →
61
Multi-Selectmedium

Which THREE types of reports can be created in Sales Cloud?

Select 3 answers
A.Lead-to-Cash.
B.Campaign-to-Deal.
C.Summary.
D.Tabular.
E.Matrix.
AnswersC, D, E

Summary reports group and subtotal records by row, giving totals per category without column-and-row cross-tabulation. Sales Cloud supports them alongside Tabular and Matrix formats, so Summary is one of the three report types the stem asks for.

Why this answer

In Salesforce Sales Cloud, reports are built on one of four standard report formats, and the three correct answers here are C. Summary, D. Tabular, and E.

Matrix. Tabular reports are the simplest format, presenting data in a flat table of rows and columns without groupings, subtotals, or charts, which is why D is valid. Summary reports group rows by up to three fields and provide subtotals and grand totals, making C a legitimate Sales Cloud report type.

Matrix reports are the most complex format, grouping data by both rows and columns (with subtotals along both axes), so E is also correct. Options A (Lead-to-Cash) and B (Campaign-to-Deal) are not report formats in Sales Cloud; they describe business processes or analytics concepts rather than the selectable report types, so they do not belong.

Practice this question →
62
MCQhard

A sales operations manager wants to track historical changes to opportunity stage durations to identify bottlenecks in the sales process. Which feature provides out-of-the-way tracking for this requirement?

A.Salesforce Einstein Activity Capture logs.
B.Custom object triggered by a flow on every stage change.
C.Standard Report Types using Opportunity History.
D.Campaign Influence reports.
AnswerC

Opportunity History stores field-change records, including stage and duration, in related history objects that standard report types can expose without custom development. This gives the sales operations manager historical stage-duration data to pinpoint bottlenecks, meeting the out-of-the-box tracking requirement without building custom objects.

Why this answer

Opportunity History is a standard related list and reportable object that automatically tracks stage, amount, probability, and close date changes each time an opportunity is edited. Standard Report Types built on Opportunity History (such as 'Opportunities with Opportunity History') allow time-in-stage analysis to identify bottlenecks without any custom development.

Exam trap

The trap is over-engineering — candidates pick custom object + flow solutions when the standard Opportunity History object and its report types already satisfy the requirement without code.

How to eliminate wrong answers

Option A is wrong because Einstein Activity Capture logs email and calendar activities, not opportunity stage transitions or duration metrics. Option B is wrong because building a custom object with a flow on every stage change is unnecessary custom development when Opportunity History already provides this natively, and it introduces maintenance overhead and governor limit risk. Option D is wrong because Campaign Influence reports attribute revenue to campaigns, not stage duration or pipeline bottleneck analysis.

Practice this question →
63
Multi-Selectmedium

Universal Containers utilizes Campaigns to track marketing initiatives. The marketing team needs to associate both Leads and Contacts to a single Campaign and track their response status. Which TWO actions can the administrator perform to meet this requirement? (Choose two.)

Select 2 answers
A.Add both Leads and Contacts directly to the Campaign using the 'Add Members' button from the Campaign record.
B.Create separate campaigns for Leads and Contacts and use hierarchical campaigns to roll up metrics.
C.Customize Campaign Member Status values to track specific response milestones for both Leads and Contacts.
D.Use Opportunity Contact Roles to automatically generate Campaign Member records for associated Contacts.
E.Create a junction object between Campaign and Account to relate Contacts directly.
AnswersA, C

Campaigns accept both Leads and Contacts as Campaign Members, so the 'Add Members' button lets the team attach either record type to one Campaign and assign each a Campaign Member Status, satisfying the single-Campaign requirement.

Why this answer

Option A is correct because the Campaign record's 'Add Members' button lets an administrator add both Leads and Contacts as Campaign Members, which is exactly how Salesforce associates either object type to a single Campaign. Option C is correct because Campaign Member Status values are customizable picklist entries on the Campaign that let the team track response milestones (for example, 'Sent', 'Responded', 'Attended') for both Leads and Contacts in that Campaign. Option B is incorrect because hierarchical campaigns roll up metrics between parent and child campaigns and do not associate Leads and Contacts to one Campaign.

Option D is incorrect because Opportunity Contact Roles relate Contacts to Opportunities and do not auto-generate Campaign Member records. Option E is incorrect because a Campaign-to-Account junction object would relate Accounts, not Contacts, and Campaign Members already provide the native Lead/Contact association.

Exam trap

Sales-Con-201 often tests the misconception that Leads and Contacts cannot coexist in a single Campaign, or that Campaign Member Status is a global picklist rather than per-Campaign customizable.

Practice this question →
64
Multi-Selecthard

Which THREE factors should be considered when designing an Opportunity Sales Process?

Select 3 answers
A.The number of team members.
B.The probability values for each stage.
C.The number of products per opportunity.
D.Which record types will use the process.
E.The stages required for the sales cycle.
AnswersB, D, E

Probability values assigned to each stage directly drive weighted revenue forecasting, so they must be defined when designing the sales process. This satisfies the stem's design requirement by ensuring stage progression reflects realistic close likelihoods, enabling accurate pipeline reporting and consistent qualification criteria across the organisation's opportunity stages.

Why this answer

Option B is correct because each stage in an Opportunity Sales Process must be assigned a probability value, which drives forecasting and is required when configuring stage-to-probability mappings in Salesforce. Option D is correct because a sales process is associated with specific opportunity record types, so you must determine which record types will use the process to ensure the correct stages and page layouts are applied. Option E is correct because the stages themselves—the sequence of steps an opportunity moves through during the sales cycle—are the core element being designed in an Opportunity Sales Process.

Option A is not a design factor for the sales process itself, since team member count relates to opportunity teams rather than stage configuration. Option C is also not a factor, as the number of products per opportunity affects products, schedules, and pricing, not the definition of the sales process stages.

Exam trap

Sales-Con-201 often tests the misconception that team size or product count influences sales process design, when the real drivers are stages, probabilities, and record types.

Practice this question →
65
MCQmedium

A Sales Rep needs to organize their daily tasks. Which view is best for this?

A.Report.
B.Task List View.
C.Opportunity Team view.
D.Dashboard.
AnswerB

The Task List View groups records by due date, priority, and status, letting the Sales Rep sequence daily activities within a single filtered grid. This directly satisfies the stem's requirement to organise daily tasks, unlike calendar or pipeline views that emphasise scheduling or deal progression rather than actionable to-do items.

Why this answer

The Task List View in Salesforce is purpose-built for organizing and prioritizing daily activities, showing tasks sorted by due date, priority, and status. It allows reps to filter, sort, and act on their to-dos directly from a single interface. This is the standard tool for personal task management in Sales Cloud.

Exam trap

The trap here is conflating analytical tools (Reports, Dashboards) with operational tools (Task List View) — candidates often pick Reports because they think 'organizing' implies analysis.

How to eliminate wrong answers

Option A is wrong because Reports are analytical tools for aggregating and visualizing data across records, not for managing individual daily task execution. Option C is wrong because the Opportunity Team view shows the members collaborating on a deal and their roles, not a rep's personal task queue. Option D is wrong because Dashboards display summarized metrics and KPIs for monitoring performance, not for interactive daily task management.

Practice this question →
66
MCQhard

A manager needs to restrict who can see the 'Expected Revenue' field on an Opportunity. What is the best approach?

A.Field-Level Security.
B.Page Layout.
C.Sharing Rule.
D.Profile permission 'View All'.
AnswerA

Field-level security on the Opportunity object controls whether a user's profile or permission set can view or edit Expected Revenue. It restricts visibility at the field level regardless of record access, which is precisely the granularity this requirement demands.

Why this answer

Field-Level Security (FLS) is the correct mechanism to restrict visibility of a specific field like Expected Revenue on the Opportunity object. FLS is configured per profile (or permission set) and controls whether a user can view or edit a field regardless of page layout or record access. This is the only option that directly hides the field's data from unauthorized users.

Exam trap

The trap is confusing page layout visibility with true field security — candidates often pick 'Page Layout' because it visually hides the field, not realizing FLS is required to actually secure the data.

How to eliminate wrong answers

Option B is wrong because Page Layouts only control whether a field appears on the UI — a user can still access the field via reports, list views, or the API, so it is not a security control. Option C is wrong because Sharing Rules control record-level access (which Opportunities a user can see), not field-level visibility within a record. Option D is wrong because 'View All' is a profile permission that grants access to all records, which is the opposite of restricting field visibility.

Practice this question →
67
MCQeasy

What is the first step in the Lead lifecycle?

A.Lead Creation.
B.Opportunity creation.
C.Campaign creation.
D.Lead Conversion.
AnswerA

Lead Creation is the entry point of the Lead lifecycle: a lead record must exist before any qualification, scoring or conversion activity can occur. This satisfies the stem by establishing the initial state from which all subsequent lifecycle stages progress.

Why this answer

The Lead lifecycle begins when a Lead record is created, whether manually, via web-to-lead, import, or API. Lead Creation is the entry point that precedes all qualification, assignment, and conversion activities. Without a Lead record existing, none of the subsequent lifecycle stages (assignment, qualification, conversion) can occur.

Exam trap

The trap here is confusing the Lead lifecycle with the overall sales process — candidates may pick 'Lead Conversion' thinking it's the starting point because it's the most discussed milestone, when in fact creation is always the first step.

How to eliminate wrong answers

Option B is wrong because Opportunity creation happens after a Lead is converted, which is near the end of the Lead lifecycle, not the beginning. Option C is wrong because Campaign creation is a marketing activity that may generate Leads but is not itself a stage in the Lead lifecycle. Option D is wrong because Lead Conversion is the final stage of the Lead lifecycle, occurring only after the Lead has been qualified and worked.

Practice this question →
68
MCQmedium

What is a 'Price Book Entry'?

A.A mapping of a Product to a Price Book.
B.A record in the Opportunity.
C.A discount for a customer.
D.A record of a sale.
AnswerA

A Price Book Entry links a Product to a specific Price Book, storing that product's price and currency for the given book. This mapping satisfies the scenario by letting one product carry different prices across multiple price books without duplicating the product record itself.

Why this answer

A Price Book Entry is a junction object that associates a Product with a specific Price Book and stores the price for that product in that price book. It is the mechanism that allows the same Product to have different prices in different Price Books (e.g., Standard vs. a regional or partner price book). Without a Price Book Entry, a Product cannot be added to an Opportunity.

Exam trap

The trap is confusing Price Book Entry with Opportunity Line Item — candidates often think the Price Book Entry is the line item on the Opportunity, when it is actually the product-price mapping that the line item references.

How to eliminate wrong answers

Option B is wrong because a Price Book Entry is not a record within an Opportunity — Opportunities contain Opportunity Line Items, which reference Price Book Entries. Option C is wrong because a discount is represented via fields like Discount on Opportunity Line Items or custom discount schedules, not by a Price Book Entry. Option D is wrong because a record of a sale is an Opportunity or Order, not a Price Book Entry.

Practice this question →
69
Multi-Selectmedium

Which THREE objects support 'Lead Conversion'?

Select 3 answers
A.Opportunity.
B.Contact.
C.Campaign.
D.Price Book.
E.Account.
AnswersA, B, E

Converting a lead creates an Opportunity when the lead is qualified, capturing the potential deal. This satisfies the stem's requirement for objects supporting Lead Conversion, alongside Account and Contact, which are the standard target records generated during the conversion process.

Why this answer

In Salesforce, Lead Conversion creates three records: an Account (E), a Contact (B), and optionally an Opportunity (A). Option E (Account) is correct because converting a lead generates a new Account (or links to an existing one) to represent the company. Option B (Contact) is correct because the lead's individual data is transferred into a new Contact record tied to that Account.

Option A (Opportunity) is correct because the conversion process can optionally create an Opportunity to track a potential deal resulting from the lead. Option C (Campaign) is not converted; campaigns are related to leads via Campaign Members but are not created or converted during lead conversion. Option D (Price Book) is unrelated to lead conversion, as price books are used to manage product pricing on opportunities and quotes, not to convert leads.

Exam trap

The trap is assuming Campaign or Price Book participate in conversion because they are common sales objects — candidates must remember that only Account, Contact, and Opportunity are the three conversion targets.

Practice this question →
70
Multi-Selectmedium

An administrator needs to configure Account Teams for an organization. Which THREE capabilities do Account Teams provide? (Choose three.)

Select 3 answers
A.Automatically enforce territory realignment based on account revenue changes.
B.Allow users to set up a Default Account Team to quickly add members to their accounts.
C.Grant flexible read or read/write access to related accounts, contacts, opportunities, and cases.
D.Allow users to set up a Default Account Team to quickly add members to opportunities they own.
E.Track different functional roles such as Account Manager, Executive Sponsor, or Technical Architect.
AnswersB, C, E

Account Teams support a Default Account Team setting, letting owners automatically add a predefined set of members to accounts they own. This satisfies the stem's capability requirement by removing repetitive manual member addition for each new account.

Why this answer

Account Teams in Salesforce provide a Default Account Team that users can configure so that a predefined set of members is automatically added to accounts they own, which is exactly what option B describes. Option C is correct because account team members can be granted flexible access levels — read-only or read/write — to the account and its related records such as contacts, opportunities, and cases. Option E is correct because Account Teams support assigning functional roles (for example Account Manager, Executive Sponsor, or Technical Architect) to each team member to reflect their responsibility.

Option A is incorrect because territory realignment based on revenue changes is handled by Enterprise Territory Management, not Account Teams. Option D is incorrect because the Default Account Team applies to accounts a user owns, not to opportunities they own.

Exam trap

Sales-Con-201 often tests the distinction between Account Teams and Opportunity Teams, and candidates may incorrectly assume that Default Account Teams apply to opportunities or that Account Teams automatically enforce territory realignment.

Practice this question →
71
MCQmedium

A company needs to track multiple prices for the same product based on customer segments (e.g., Retail vs. Wholesale). How should this be implemented?

A.Create multiple Product records for each price.
B.Use custom fields on the Opportunity Product object.
C.Create separate Opportunity record types.
D.Use Price Books to define different prices for the same product.
AnswerD

Price Books store product entries with their own unit prices, so the same product can appear in a Retail Price Book and a Wholesale Price Book at different amounts. This satisfies the segment-based pricing requirement without duplicating product records, since one product supports multiple price book entries.

Why this answer

Multiple Price Books allow different pricing tiers for the same Product record.

Practice this question →
72
MCQeasy

Sales reps at Cloud Kicks frequently need to send the exact same multi-line introductory email template to newly assigned Leads. Which feature should the administrator configure to streamline this process?

A.Email Templates
B.Sales Cadences
C.Macro Builder
D.Quick Actions on Campaign
AnswerA

Email Templates store reusable multi-line content that sales reps insert directly into Lead emails, eliminating retyping the standard introduction. This satisfies the stem's requirement for sending the exact same template repeatedly to newly assigned Leads, since templates can be selected during composition and merged with recipient and Lead fields automatically.

Why this answer

Email Templates combined with List Email or Send Email actions allow users to send standardized messages efficiently.

Practice this question →
73
MCQhard

A company wants to ensure that all Opportunities have a specific field populated before moving to the 'Closed-Won' stage. Which tool is the most appropriate?

A.Workflow Rule.
B.Sharing Rule.
C.Lead Assignment Rule.
D.Validation Rule.
AnswerD

Validation Rules enforce field-level data integrity at save time, blocking a record from being saved when defined criteria fail. This directly satisfies the stem's constraint: preventing an Opportunity from reaching the 'Closed-Won' stage unless the specified field is populated, without requiring code or workflow automation.

Why this answer

A Validation Rule is the correct tool because it enforces data integrity at the record level by preventing a save when defined criteria are not met. To require a field before an Opportunity can be moved to 'Closed-Won', the rule formula would check ISBLANK(field) AND ISPICKVAL(StageName, 'Closed Won') and fire an error. Validation Rules run on insert and update, making them ideal for stage-gated requirements.

Exam trap

The trap here is confusing Workflow Rules (post-save automation) with Validation Rules (pre-save enforcement); candidates often pick Workflow Rule because it sounds like it 'enforces' something, but it cannot block a save.

How to eliminate wrong answers

Option A is wrong because Workflow Rules execute after the record is saved and cannot block a save; they perform actions like field updates, email alerts, and tasks. Option B is wrong because Sharing Rules control record-level access for users/groups/roles, not field population requirements. Option C is wrong because Lead Assignment Rules determine which user or queue a Lead is assigned to, and they have no bearing on Opportunity stage validation.

Practice this question →
74
MCQeasy

A company is migrating from a legacy system and needs to import Leads. They want to ensure duplicate records are not created. Which feature should they configure?

A.Workflow Rules.
B.Validation Rules.
C.Salesforce Shield.
D.Matching and Duplicate Rules.
AnswerD

Matching rules identify potential duplicates by comparing field values, while duplicate rules then block or warn on record creation. Configuring both satisfies the stem's requirement to prevent duplicate Leads during import, since matching alone only surfaces candidates without enforcing any action.

Why this answer

Matching and Duplicate Rules in Salesforce are the declarative features designed to prevent duplicate records during import. Matching Rules define the criteria for what constitutes a duplicate (e.g., matching on Email or Name), and Duplicate Rules enforce the action (block or alert) when a duplicate is detected, including during Data Loader or import wizard operations.

Exam trap

Sales-Con-201 often tests the confusion between Validation Rules (field-level) and Duplicate Rules (record-level) — candidates pick Validation Rules because they think it can compare records, but only Matching/Duplicate Rules handle cross-record duplication.

How to eliminate wrong answers

Option A is wrong because Workflow Rules automate actions like field updates and email alerts after save, and cannot detect or block duplicates. Option B is wrong because Validation Rules enforce field-level data quality (e.g., required fields, format) but do not compare records against each other. Option C is wrong because Salesforce Shield is a security and compliance product (Event Monitoring, Platform Encryption, Field Audit Trail) and has nothing to do with duplicate prevention.

Practice this question →
75
Multi-Selectmedium

Which TWO actions can be automated with Flow Builder?

Select 2 answers
A.Changing the org-wide security settings.
B.Modifying the standard field types.
C.Sending an email alert.
D.Deleting the user database.
E.Updating a related record when an opportunity stage changes.
AnswersC, E

Flow Builder includes a Send Email action that dispatches an email to specified recipients when the flow's trigger criteria are met. This satisfies the automation requirement by executing the notification without manual intervention, using record data merged into the message.

Why this answer

Option C is correct because Flow Builder can automate sending email alerts through the core action 'Send Email' (or email alert actions), allowing a flow to notify users or external recipients when defined conditions are met. Option E is correct because Flow Builder supports record-triggered flows (e.g., a before-save or after-save flow on Opportunity) that use Update Records elements to modify related records when the opportunity's StageName changes. Option A is incorrect because org-wide security settings such as sharing defaults, password policies, and session settings are configured in Setup, not automated via Flow Builder.

Option B is incorrect because standard field types are fixed metadata and cannot be changed by a flow. Option D is incorrect because deleting the user database is not a Flow Builder action; user management and data deletion are handled through administrative tools and APIs, not flows.

Exam trap

Sales-Con-201 often tests the boundary between declarative automation (Flow) and administrative/metadata configuration (Setup, Object Manager), so candidates wrongly assume Flow can change security settings or field types because it 'automates everything.'

Practice this question →
Page 1 of 2 · 82 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Practical Application Of Sales Cloud Expertise questions.

Start 20-question session