New Year Sale ! 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-403 Topic 5 Question 34 Discussion

Actual exam question for Salesforce's CRT-403 exam
Question #: 34
Topic #: 5
[All CRT-403 Questions]

Ursa Major Solar (UMS) uses a public sharing model for accounts. UMS would like to move to a more restrictive sharing model but wants the Sales team to continue to have access to all account records with the sales record type.

Which two actions should an app builder complete to implement this change?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Update the organization-wide defaults and create a criteria based sharing rule are two actions that an app builder should complete to implement the change of moving to a more restrictive sharing model while allowing the Sales team to access all account records with the sales record type. Updating the organization-wide defaults can set the baseline level of access for accounts, and creating a criteria based sharing rule can grant additional access based on record type. Updating the Sales profile and creating an owner-based sharing rule are not necessary or sufficient actions for this change.


Contribute your Thoughts:

Kayleigh
6 months ago
Yeah, Quentin's got a point. Salesforce security can be a real headache, but at least they give us options like criteria-based and owner-based sharing rules to work with.
upvoted 0 times
Florinda
5 months ago
C) Create a criteria-based sharing rule.
upvoted 0 times
...
Tamie
5 months ago
A) Update the Sales profile.
upvoted 0 times
...
...
Quentin
6 months ago
Haha, I bet the app builder is sweating bullets trying to figure out the best way to implement this change. Gotta love those tricky Salesforce security requirements!
upvoted 0 times
...
Lamar
7 months ago
I agree with Ronna. C and D are the way to go. This will give the Sales team the required access without compromising the overall security of the system.
upvoted 0 times
Quentin
5 months ago
No, I think C and D are more appropriate in this case.
upvoted 0 times
...
Lai
5 months ago
B) Update the organization-wide defaults
upvoted 0 times
...
Curt
5 months ago
D) Create an owner-based sharing rule.
upvoted 0 times
...
Almeta
6 months ago
A) Update the Sales profile.
upvoted 0 times
...
Elmer
6 months ago
I agree, that sounds like the best approach.
upvoted 0 times
...
Leontine
6 months ago
D) Create an owner-based sharing rule.
upvoted 0 times
...
Filiberto
6 months ago
C) Create a criteria-based sharing rule.
upvoted 0 times
...
Arlette
6 months ago
C) Create a criteria-based sharing rule.
upvoted 0 times
...
...
Marguerita
7 months ago
A and B don't seem to be the right choices here. Updating the Sales profile or the organization-wide defaults won't give the Sales team the specific access they need while limiting access for others.
upvoted 0 times
Cordell
6 months ago
Exactly. It's a more targeted approach to meet UMS's requirements.
upvoted 0 times
...
Lavonna
6 months ago
That makes sense. And creating an owner-based sharing rule would ensure the Sales team has access to all account records with the sales record type.
upvoted 0 times
...
Honey
6 months ago
It might be, but it would allow for more control over who has access to the records.
upvoted 0 times
...
Johnetta
6 months ago
But wouldn't creating a criteria-based sharing rule be too specific?
upvoted 0 times
...
Earleen
7 months ago
D) Create an owner-based sharing rule.
upvoted 0 times
...
Ettie
7 months ago
C) Create a criteria-based sharing rule.
upvoted 0 times
...
...
Ronna
7 months ago
I think the correct answers are C and D. Creating a criteria-based sharing rule and an owner-based sharing rule will allow the Sales team to continue accessing all account records with the sales record type while restricting access for other users.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77