BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CRT-211 Topic 3 Question 102 Discussion

Actual exam question for Salesforce's CRT-211 exam
Question #: 102
Topic #: 3
[All CRT-211 Questions]

The sales department has asked to limit access to the Amount field on the Opportunity to only tnose users. In the sales department and on the executtve team, Northern Trail Outfitters uses six custom profiles including Sales User. Marketing user, call Center user. Executive User Sales Manager user, ana call Center Manager user. Field level access is removed from three or the profiles In the sandbox.

What action should an administrator take to make sure this change is in production?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Stefany
23 days ago
I'm going with C. Deploying the change set from the sandbox is the way to go. Hey, at least it's not a multiple-choice question about the Dewey Decimal System!
upvoted 0 times
Jerry
10 days ago
Definitely. Deploying the change set is the most efficient way to ensure the update is implemented correctly.
upvoted 0 times
...
Jolene
14 days ago
That's a good choice. It's important to make sure the change is reflected in production.
upvoted 0 times
...
Linn
15 days ago
C) Deploy a change set from the sandbox to production including the Amount field with all the custom profiles.
upvoted 0 times
...
...
Gertude
1 months ago
B? More like 'Boo' to manually restricting access for each profile. C is the clear winner here.
upvoted 0 times
Vicky
4 days ago
B? More like 'Boo' to manually restricting access for each profile. C is the clear winner here.
upvoted 0 times
...
Vivienne
13 days ago
C) Deploy a change set from the sandbox to production including the Amount field with all the custom profiles.
upvoted 0 times
...
Sylvia
14 days ago
A) Create a sandbox template and push it to production to reflect the update.
upvoted 0 times
...
...
Dick
1 months ago
D sounds good, but I think C is better. It's more comprehensive and covers all the profiles.
upvoted 0 times
Ailene
13 days ago
That sounds like the best approach to ensure the update is implemented correctly.
upvoted 0 times
...
Lindsey
15 days ago
Let's deploy a change set from the sandbox to production, including the Amount field with all the custom profiles.
upvoted 0 times
...
Viva
17 days ago
I agree, it seems like the most efficient way to make sure the change is in production.
upvoted 0 times
...
Kent
20 days ago
I think we should go with option C.
upvoted 0 times
...
Joseph
23 days ago
C is definitely the best option. It ensures all profiles are covered in the change set.
upvoted 0 times
...
Devon
1 months ago
D) Process a change set with the profiles that should no longer have access to the field.
upvoted 0 times
...
Samira
1 months ago
C) Deploy a change set from the sandbox to production including the Amount field with all the custom profiles.
upvoted 0 times
...
...
Lorrie
1 months ago
I'm not sure, maybe we should manually restrict access to the field for each profile like in the sandbox.
upvoted 0 times
...
Markus
2 months ago
I agree with Belen, that seems like the most efficient way to make sure the change is in production.
upvoted 0 times
...
Belen
2 months ago
I think we should deploy a change set from the sandbox to production.
upvoted 0 times
...
Delisa
2 months ago
C is the way to go. Pushing the sandbox changes to production is the most efficient solution here.
upvoted 0 times
Emilio
23 days ago
D) Process a change set with the profiles that should no longer have access to the field.
upvoted 0 times
...
Mauricio
24 days ago
C is the way to go. Pushing the sandbox changes to production is the most efficient solution here.
upvoted 0 times
...
Chauncey
1 months ago
A) Create a sandbox template and push it to production to reflect the update.
upvoted 0 times
...
Ricarda
1 months ago
C) Deploy a change set from the sandbox to production including the Amount field with all the custom profiles.
upvoted 0 times
...
...

Save Cancel