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 5 Question 26 Discussion

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

An architect has a requirement to create a criteria-based sharing rule based on the customer Social Security Number. However, when setting up the rule in Contact Sharing, the field is not shown on the list of available fields.

What is causing this issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Lorrine
1 months ago
I'm feeling option C. The architect must be running around the office, begging for permission to the Compliance fields. 'Please, sir, may I have some access?'
upvoted 0 times
Hoa
2 days ago
B) The architect's profile does not have Field Level Security for this field.
upvoted 0 times
...
Mauricio
4 days ago
A) The field has been configured for encryption.
upvoted 0 times
...
...
Reiko
2 months ago
Aha, I reckon it's option B. The architect needs to get their profile updated with the right Field Level Security. Welcome to the world of Salesforce administration!
upvoted 0 times
Brendan
12 days ago
The architect should definitely look into updating their profile for that field.
upvoted 0 times
...
Kerry
20 days ago
Yeah, the Field Level Security might be the issue here.
upvoted 0 times
...
Elza
20 days ago
Definitely. The architect needs to make sure they have the right permissions for that field.
upvoted 0 times
...
Mi
1 months ago
Yeah, the Field Level Security might be the issue here. They should update it.
upvoted 0 times
...
Carri
1 months ago
I think it's option B too. The architect should check their profile settings.
upvoted 0 times
...
Lakeesha
1 months ago
I think it's option B too. The architect should check their profile settings.
upvoted 0 times
...
...
Kenneth
2 months ago
Haha, I'm going with option C. The architect probably doesn't have permission to access the compliance fields. Classic case of 'it's not you, it's the permissions'.
upvoted 0 times
Martina
1 days ago
User 4: Yeah, I agree. It's likely a permissions issue.
upvoted 0 times
...
Ceola
5 days ago
User 3: I'm with Ceola on this one. The architect probably doesn't have permission to Compliance fields.
upvoted 0 times
...
Hortencia
10 days ago
User 2: Hortencia, I disagree. I believe the architect's profile does not have Field Level Security for this field.
upvoted 0 times
...
Roxanne
2 months ago
User 1: I think it's because the field has been configured for encryption.
upvoted 0 times
...
...
Barney
2 months ago
I'm betting on option A. If the field is encrypted, that would explain why it's not showing up in the list. Gotta love those security features, right?
upvoted 0 times
...
Ammie
2 months ago
Hmm, I think it's option B. The architect's profile must not have the necessary permissions to access this field. Access control strikes again!
upvoted 0 times
Terrilyn
28 days ago
Maybe the field is encrypted, that could be causing the issue.
upvoted 0 times
...
Dana
29 days ago
I agree, it's probably option B. The architect needs to check their profile permissions.
upvoted 0 times
...
Abel
1 months ago
Maybe the field is encrypted, that could be causing the issue.
upvoted 0 times
...
Amos
2 months ago
I agree, it's probably option B. The architect needs to check their profile permissions.
upvoted 0 times
...
...
Jacqueline
3 months ago
But could it also be that the architect does not have permission to Compliance fields?
upvoted 0 times
...
Leota
3 months ago
I agree with Fernanda, it makes sense that encryption would hide the field.
upvoted 0 times
...
Fernanda
3 months ago
I think the issue is that the field has been configured for encryption.
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