Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Agentforce Sales Consultant (Sales-Con-201) Exam - Topic 2 Question 107 Discussion

Posted by Denny on Dec 11, 2024 at 02:03 AM

Cloud Kicks (CK) recently implemented Einstein Opportunity Scoring in its production org. CK is using the Amount field in its Opportunity Scoring model.

What will a user without access to the Amount field on the Opportunity object observe?

Suggested Answer: C

In Einstein Opportunity Scoring, if a user lacks access to a field (such as the Amount field) that is used as a contributing factor, that field is omitted from the scoring details that the user sees. Salesforce respects field-level security settings, so users without permission to view certain fields will not see those fields in the contributing factors section. Instead, the scoring model will still display, but without the restricted fields in the breakdown of contributing factors.


Get Premium Salesforce Certified Agentforce Sales Consultant (Sales-Con-201) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
36 comments · newest first
SH
Sharika 11 months ago
I heard the Opportunity Score might still show up though.
SA
Sarah 11 months ago
Yeah, it makes sense for it to be hidden.
TR
Truman 12 months ago
I’m not so sure about that, could be an error too.
CO
Cornell 12 months ago
Definitely agree, it won't show an error.
CA
Cassandra 1 year ago
I think the Amount field will just be hidden.
HU
Hui 1 year ago
I feel like the answer could be C, but I’m not completely confident. I need to double-check how contributing factors work in relation to field access.
AN
Annamae 1 year ago
I’m a bit confused about this one. If the user can’t see the Amount field, does that mean they can’t see the Opportunity Score at all?
AL
Alaine 1 year ago
I think I saw a similar question where access restrictions only hid certain fields, so maybe the Amount field will just be hidden from the contributing factors?
DE
Dexter 1 year ago
I remember studying how field-level security affects visibility, but I'm not sure if it hides the entire Opportunity Score too.
EM
Emilio 1 year ago
I'm pretty confident that the correct answer is B. If the user doesn't have access to the Amount field, both the Opportunity Score and the Amount field will be hidden from their view.
VE
Venita 1 year ago
Okay, let me think this through. If the Amount field is used in the scoring model, and a user doesn't have access to that field, then the field will likely be hidden from the contributing factors section. That's my best guess.
AU
Audrie 1 year ago
Hmm, I'm a little unsure about this one. I know Einstein Opportunity Scoring uses fields to calculate the score, but I'm not sure what happens if a user can't see one of those fields.
CL
Clement 1 year ago
This seems pretty straightforward. I think the key is understanding how Einstein Opportunity Scoring works and what happens when a user doesn't have access to a field used in the model.
HY
Hyman 2 years ago
I've got to say, hiding the Amount field is the funniest way to handle this. Imagine the user's face when they see a big empty space where the field should be. Option C all the way!
JU
Julieta 2 years ago
↳ replying to Hyman
User 3: Option C seems like the most logical choice in this situation.
LE
Leonardo 2 years ago
↳ replying to Hyman
User 2: Yeah, it would be confusing for the user to see a big empty space there.
JA
Jacob 2 years ago
↳ replying to Hyman
User 1: I agree, hiding the Amount field is definitely the funniest option.
LA
Lacresha 2 years ago
Yes, Mattie is correct. The Opportunity Score field and the Amount field will be hidden for that user.
RU
Rutha 2 years ago
The error message in the contributing factors section would be a bit confusing for the user. Hiding the field entirely, as in option C, is a cleaner approach in my opinion.
CE
Cecil 2 years ago
↳ replying to Rutha
User 4: Yeah, hiding the field entirely makes sense.
JA
Jamal 2 years ago
↳ replying to Rutha
User 3: Option C seems like the best choice then.
CO
Colton 2 years ago
↳ replying to Rutha
User 2: I agree, the error message could be confusing.
LA
Larae 2 years ago
↳ replying to Rutha
User 1: I think hiding the Amount field is a cleaner approach.
GE
Gerry 2 years ago
But what about the Opportunity Score field? Will that be hidden too?
MA
Mattie 2 years ago
I agree with Edna. The Amount field will be hidden from the contributing factors section.
AL
Alison 2 years ago
Hmm, hiding the entire Opportunity Score field and Amount field seems a bit excessive. I think option C, where just the Amount field is hidden, makes the most sense.
LA
Latonia 2 years ago
↳ replying to Alison
User1: Yeah, hiding just the Amount field makes more sense.
GE
Gerardo 2 years ago
↳ replying to Alison
User3: I think option C is the most logical choice.
EM
Emerson 2 years ago
↳ replying to Alison
User2: I agree, option B seems too extreme.
TH
Theron 2 years ago
↳ replying to Alison
User1: I think option A is incorrect.
ED
Edna 2 years ago
I think the user will not see the Amount field in the contributing factors section.
DO
Donte 2 years ago
If the user doesn't have access to the Amount field, I'd expect the Amount field to be hidden from the contributing factors section. Option C seems like the correct answer here.
GA
Garry 2 years ago
↳ replying to Donte
Exactly. It's important for users to have access to all the necessary fields for accurate scoring.
HU
Hubert 2 years ago
↳ replying to Donte
So, the user won't be able to see the Amount field's impact on the Opportunity Score.
LI
Lizbeth 2 years ago
↳ replying to Donte
Yes, that makes sense. It would be logical for it to be hidden if the user doesn't have access.
TO
Tora 2 years ago
↳ replying to Donte
I think the Amount field will be hidden from the contributing factors section.
0/2000 characters

Save Cancel