New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce CRT-403 Exam - 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:

0/2000 characters
Lili
3 months ago
Classic encryption seems unnecessary for this.
upvoted 0 times
...
Elbert
3 months ago
Wait, can users really only see that field? Sounds odd.
upvoted 0 times
...
Keneth
3 months ago
Sharing rules won't cut it here, right?
upvoted 0 times
...
Deeann
4 months ago
I think field-level security is the way to go.
upvoted 0 times
...
Dominque
4 months ago
Definitely need a filtered view for that!
upvoted 0 times
...
Chantay
4 months ago
I practiced a question similar to this, and I think filtered views were the answer there too. But I’m still a bit confused about the differences.
upvoted 0 times
...
Vince
4 months ago
Sharing rules seem more about record access rather than field visibility, so I’m leaning towards filtered view or field-level security.
upvoted 0 times
...
Verona
4 months ago
I'm not entirely sure, but I feel like field-level security might be the right choice since it deals with specific fields.
upvoted 0 times
...
Paola
5 months ago
I think I remember something about filtered views being used to control what users see based on their profiles.
upvoted 0 times
...
Nakisha
5 months ago
The key here is satisfying the requirement that only users with the Outer Planets profile need to see the Jupiter field. I think a filtered view might be the most efficient way to handle this.
upvoted 0 times
...
Carin
5 months ago
Hmm, I'm not entirely sure about this one. I'll need to think through the different options carefully to determine the best approach.
upvoted 0 times
...
Idella
5 months ago
This seems like a straightforward question about controlling access to specific fields. I'd start by considering field-level security as a potential solution.
upvoted 0 times
...
Minna
5 months ago
Classic encryption doesn't seem relevant to this scenario. I'm leaning towards field-level security or sharing rules as the most likely solutions.
upvoted 0 times
...
Tamar
5 months ago
Hmm, I'm a bit confused by the wording of the options. I'll need to re-read them a few times to make sure I understand the differences between them.
upvoted 0 times
...
Theodora
5 months ago
Okay, I've got this. The key is to update the daemon.json file with the right settings for the Splunk logging solution. That should do the trick and export the container logs as required. Option A is the way to go.
upvoted 0 times
...
Luann
5 months ago
Hmm, this looks like a tricky one. I'll need to think it through carefully.
upvoted 0 times
...
Aliza
2 years ago
I believe filtered view might be a better option to control access to the Jupiter field.
upvoted 0 times
...
Mitzie
2 years ago
I'm not sure, but I think sharing rules could also work in this scenario.
upvoted 0 times
...
Rosalind
2 years 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
2 years ago
I agree with Shayne, field-level security makes sense for this requirement.
upvoted 0 times
...
Emile
2 years ago
Classic encryption? That's about as useful as a solar-powered flashlight on the dark side of the moon.
upvoted 0 times
Dorcas
2 years ago
Field-level security is the best option to control access to the Jupiter field.
upvoted 0 times
...
My
2 years ago
Filtered view would be the way to go for this requirement.
upvoted 0 times
...
...
Vivan
2 years ago
Sharing rules? I'd rather share my telescope with a black hole than try to figure out this mess.
upvoted 0 times
Caprice
2 years ago
D) Sharing rules
upvoted 0 times
...
Jutta
2 years ago
C) Field-level security
upvoted 0 times
...
Mickie
2 years ago
B) Filtered view
upvoted 0 times
...
Leonor
2 years ago
A) Classic encryption
upvoted 0 times
...
...
Peggy
2 years 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
2 years ago
I agree, just set up the Outer Planets profile with access.
upvoted 0 times
...
Gayla
2 years ago
Filtered view is the way to go.
upvoted 0 times
...
...
Shayne
2 years ago
I think the app builder should use field-level security.
upvoted 0 times
...
Alverta
2 years 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
2 years ago
C) Field-level security
upvoted 0 times
...
Coletta
2 years ago
Yeah, no need to complicate things with field-level security when filtered view can do the job.
upvoted 0 times
...
Crista
2 years ago
I agree, just use filtered view to show the Jupiter field to Outer Planets profile users.
upvoted 0 times
...
Tijuana
2 years ago
C) Field-level security
upvoted 0 times
...
Glendora
2 years ago
True, field-level security seems like overkill for this situation.
upvoted 0 times
...
...

Save Cancel