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 Platform App Builder Topic 5 Question 93 Discussion

Actual exam question for Salesforce's Platform App Builder exam
Question #: 93
Topic #: 5
[All Platform App Builder Questions]

At Ursa Solar Major, only users with the Outer Planets profile need to see

the Jupiter field on the Solar System object.

How should the app builder satisfy this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: C

To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:

C . Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.

Steps to set up field-level security:

Navigate to Setup Object Manager Solar System.

Select Fields & Relationships Jupiter field.

Click Field-Level Security.

For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.

For the Outer Planets profile, check Visible to grant access.

This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.

For more information on field-level security, check Salesforce's guide on Field-Level Security.


Contribute your Thoughts:

Novella
11 months ago
Field-level security, baby! That's how you keep those Outer Planets users in their lane. Unless, of course, you want them seeing Uranus. Wait, that came out wrong...
upvoted 0 times
Trinidad
11 months ago
C) Field-level security
upvoted 0 times
...
Ariel
11 months ago
A) Classic encryption
upvoted 0 times
...
...
Elbert
11 months ago
I think sharing rules might be too broad for this specific requirement.
upvoted 0 times
...
Shawnda
12 months ago
I believe filtered view could also work to restrict access to the Jupiter field.
upvoted 0 times
...
Thora
12 months ago
I agree with Rasheeda, field-level security makes sense for this requirement.
upvoted 0 times
...
Alline
12 months ago
Sharing rules? What is this, a social network? I'm feeling a 'Filtered view' kind of vibe here.
upvoted 0 times
...
Keith
12 months ago
Oh come on, classic encryption? What is this, the Dark Ages? Field-level security is the way to go, hands down.
upvoted 0 times
Rozella
10 months ago
Classic encryption may not be the best fit for this specific requirement.
upvoted 0 times
...
Loise
10 months ago
Sharing rules can be too broad, field-level security is more precise.
upvoted 0 times
...
Jonell
11 months ago
I agree, field-level security provides more granular control over who can see what.
upvoted 0 times
...
Fletcher
11 months ago
Filtered view is also a good option, it restricts access based on criteria.
upvoted 0 times
...
...
Selma
12 months ago
Filtered view? That's like trying to hide a planet from an astronomer. Gotta go with field-level security on this one.
upvoted 0 times
Maryln
11 months ago
I agree, field-level security is the way to go for this requirement.
upvoted 0 times
...
Celestina
11 months ago
Filtered view? That's like trying to hide a planet from an astronomer.
upvoted 0 times
...
...
Rasheeda
12 months ago
I think the app builder should use field-level security.
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