Cyber Monday 2024! 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 2 Question 44 Discussion

Actual exam question for Salesforce's CRT-403 exam
Question #: 44
Topic #: 2
[All CRT-403 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:

Aliza
5 months ago
I believe filtered view might be a better option to control access to the Jupiter field.
upvoted 0 times
...
Mitzie
5 months ago
I'm not sure, but I think sharing rules could also work in this scenario.
upvoted 0 times
...
Rosalind
5 months ago
Hmm, field-level security. Sounds like a lot of work for a simple problem. Why not just let the Outer Planets folks see the Jupiter field and be done with it?
upvoted 0 times
...
Isaac
5 months ago
I agree with Shayne, field-level security makes sense for this requirement.
upvoted 0 times
...
Emile
5 months ago
Classic encryption? That's about as useful as a solar-powered flashlight on the dark side of the moon.
upvoted 0 times
Dorcas
4 months ago
Field-level security is the best option to control access to the Jupiter field.
upvoted 0 times
...
My
5 months ago
Filtered view would be the way to go for this requirement.
upvoted 0 times
...
...
Vivan
5 months ago
Sharing rules? I'd rather share my telescope with a black hole than try to figure out this mess.
upvoted 0 times
Caprice
4 months ago
D) Sharing rules
upvoted 0 times
...
Jutta
4 months ago
C) Field-level security
upvoted 0 times
...
Mickie
4 months ago
B) Filtered view
upvoted 0 times
...
Leonor
5 months ago
A) Classic encryption
upvoted 0 times
...
...
Peggy
5 months ago
Filtered view? More like 'filtered common sense'. Just give the Outer Planets profile access and call it a day, folks.
upvoted 0 times
Rene
5 months ago
I agree, just set up the Outer Planets profile with access.
upvoted 0 times
...
Gayla
5 months ago
Filtered view is the way to go.
upvoted 0 times
...
...
Shayne
5 months ago
I think the app builder should use field-level security.
upvoted 0 times
...
Alverta
6 months ago
Field-level security? That's like putting a Band-Aid on a black hole. Just let everyone see the Jupiter field, it's not like it's a secret or anything.
upvoted 0 times
Oliva
5 months ago
C) Field-level security
upvoted 0 times
...
Coletta
5 months ago
Yeah, no need to complicate things with field-level security when filtered view can do the job.
upvoted 0 times
...
Crista
5 months ago
I agree, just use filtered view to show the Jupiter field to Outer Planets profile users.
upvoted 0 times
...
Tijuana
5 months ago
C) Field-level security
upvoted 0 times
...
Glendora
5 months ago
True, field-level security seems like overkill for this situation.
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