Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Sharing and Visibility Architect Topic 4 Question 44 Discussion

Actual exam question for Salesforce's Sharing and Visibility Architect exam
Question #: 44
Topic #: 4
[All Sharing and Visibility Architect Questions]

Customer complaints for bad interactions with a customer support agent are logged as Cases and assigned to a human resources representative. The agent of the complaint should not see the case, but their manager should.

How is this accomplished?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Julian
1 months ago
Option C is like trying to hide a bad review from the employee - good luck keeping that under wraps!
upvoted 0 times
Leonida
16 hours ago
B) Criteria based Sharing Rule on Case that shares to the Role Manager and above when a custom field Assigned Agent (subject of the complaint) is not blank.
upvoted 0 times
...
Helaine
16 days ago
A) Trigger on Case ta lookup and share to the manager of an Assigned Agent custom field (the subject of the complaint) using Apex Managed Sharing.
upvoted 0 times
...
...
Junita
1 months ago
Option B all the way! It's like sharing your favorite cookie recipe with your manager - you just can't keep it a secret!
upvoted 0 times
...
Linwood
1 months ago
Hmm, option C is a bit sneaky, but I guess it gets the job done. Although, I'd be a bit worried about the agent finding out some other way and feeling betrayed.
upvoted 0 times
...
Tamesha
1 months ago
Option A with Apex Managed Sharing sounds a bit more complex, but it could provide more fine-grained control if needed. As long as it's implemented correctly, it could be a good solution.
upvoted 0 times
Dierdre
18 hours ago
Yeah, it might be a bit more complex, but it could offer better control over who sees the case.
upvoted 0 times
...
Earlean
7 days ago
I think Option A with Apex Managed Sharing is the way to go.
upvoted 0 times
...
...
Tomoko
2 months ago
I like how option C uses the role hierarchy to control access. Removing CRED permissions on the case is a clever way to prevent the agent from seeing the complaint.
upvoted 0 times
Sabina
7 days ago
It's important to maintain confidentiality in these situations. Option C seems like the most secure choice.
upvoted 0 times
...
Sang
17 days ago
I agree, it's a clever solution. Removing CRED permissions on the case ensures the agent can't see the complaint.
upvoted 0 times
...
Barabara
1 months ago
Option C is definitely a smart way to handle this situation. Using the role hierarchy to control access makes sense.
upvoted 0 times
...
...
Cornell
2 months ago
Option B seems like the most straightforward way to handle this. Sharing the case with the manager when the Assigned Agent field is not blank is a clear and appropriate solution.
upvoted 0 times
Miesha
15 days ago
I still think Option B is the best choice for this scenario.
upvoted 0 times
...
Samira
20 days ago
I think Option C could cause some confusion with ownership of the case.
upvoted 0 times
...
Clorinda
1 months ago
But wouldn't Option A also work by using Apex Managed Sharing?
upvoted 0 times
...
Devon
1 months ago
I agree, Option B seems like the most straightforward solution.
upvoted 0 times
...
...
Kenny
2 months ago
I see both points, but I think option B is the most efficient. Sharing the case based on criteria to the Role Manager and above seems like a straightforward solution.
upvoted 0 times
...
Francisca
2 months ago
I disagree, I believe option C is more secure. By removing read permissions on the case for the agent, we ensure they cannot access the record.
upvoted 0 times
...
Kyoko
2 months ago
I think option A is the best way to accomplish this. Using Apex Managed Sharing to share the case with the manager makes sense.
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