Salesforce Exam Sharing-and-Visibility-Architect Topic 4 Question 31 Discussion

Actual exam question for Salesforce's Salesforce Certified Sharing and Visibility Architect exam

Question #: 31
Topic #: 4

[All Salesforce Certified Sharing and Visibility Architect Questions]

A banking company wants their customers Date of Birth Field searchable by Banking Reps, but only editable by Customer Support Reps.

Which approach is recommended to meet this requirement?

ACreate a Validation rule in the Data of Birth field so the rule returns true only when user.profilename matches Customer Support Rep.

BSet the Fled Level Security for the Date of Birth field to be Visible to Customer Support Rep Profile, and set the Date of Birth Field Visible and Read-only to Banking Rep profile.

CAdd Date of Birth field to the Search layout of the Contact Object. Modify the Page layout assigned to Customer Support Rep and add Date of Birth field as Required.

Show Suggested Answer

Suggested Answer: B

by Oretha at Mar 10, 2024, 05:42 PM

Limited Time Offer

25%

Off

Get Premium Sharing-and-Visibility-Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Glenn

3 months ago

Option A sounds like it would be a pain to maintain. Validation rules can get messy, especially when you have different profiles involved.

upvoted 0 times

Kris

2 months ago

Yeah, Option C might make it easier for Banking Reps to search, but Option B ensures the security and control needed for editing.

upvoted 0 times

...

Melina

2 months ago

I agree, Option B provides a clear separation of access for Banking Reps and Customer Support Reps.

upvoted 0 times

...

Daniel

2 months ago

Option B seems like the best approach. It clearly defines who can view and edit the Date of Birth field.

upvoted 0 times

...

Portia

3 months ago

Haha, I bet the banking reps are gonna spend way too much time searching for people's birthdays. Maybe they should just get a cake for everyone's birthday instead!

upvoted 0 times

...

Carman

3 months ago

Option C might work, but it feels a bit overkill. Why make the field required for the Customer Support Reps when they just need to be able to edit it?

upvoted 0 times

Kristian

2 months ago

A: Option C might be overkill, as you mentioned. Option B provides the necessary access control without complicating things.

upvoted 0 times

...

Carolann

2 months ago

B: I agree, Option B is the most efficient way to meet the requirement without unnecessary restrictions.

upvoted 0 times

...

Linwood

3 months ago

A: Option B seems like the best approach. It restricts editing to Customer Support Reps while allowing visibility to Banking Reps.

upvoted 0 times

...

Merilyn

3 months ago

I agree, Option B is the way to go. It's a clean and straightforward solution that meets the requirements.

upvoted 0 times

Miss

3 months ago

I think so too. Setting the Field Level Security correctly is key to meeting the requirement.

upvoted 0 times

...

Portia

3 months ago

Option B is definitely the best choice. It ensures that only Customer Support Reps can edit the Date of Birth field.

upvoted 0 times

...

Chauncey

4 months ago

Option B seems like the best approach. It keeps the Date of Birth field editable for the Customer Support Reps while still making it searchable for the Banking Reps.

upvoted 0 times

Gilma

3 months ago

I agree, setting the Field Level Security and making the Date of Birth field visible and read-only for Banking Reps is a good solution.

upvoted 0 times

...

Cristy

3 months ago

Option B seems like the best approach. It keeps the Date of Birth field editable for the Customer Support Reps while still making it searchable for the Banking Reps.

upvoted 0 times

...