MENU
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?
Suggested Answer: C
Get Premium CRT-403 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
38 comments · newest first
LI
Lili
11 months ago
Classic encryption seems unnecessary for this.
EL
Elbert
11 months ago
Wait, can users really only see that field? Sounds odd.
KE
Keneth
12 months ago
Sharing rules won't cut it here, right?
DE
Deeann
12 months ago
I think field-level security is the way to go.
DO
Dominque
1 year ago
Definitely need a filtered view for that!
CH
Chantay
1 year 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.
VI
Vince
1 year ago
Sharing rules seem more about record access rather than field visibility, so I’m leaning towards filtered view or field-level security.
VE
Verona
1 year ago
I'm not entirely sure, but I feel like field-level security might be the right choice since it deals with specific fields.
PA
Paola
1 year ago
I think I remember something about filtered views being used to control what users see based on their profiles.
NA
Nakisha
1 year 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.
CA
Carin
1 year 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.
ID
Idella
1 year 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.
MI
Minna
1 year 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.
TA
Tamar
1 year 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.
TH
Theodora
1 year 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.
LU
Luann
1 year ago
Hmm, this looks like a tricky one. I'll need to think it through carefully.
AL
Aliza
2 years ago
I believe filtered view might be a better option to control access to the Jupiter field.
MI
Mitzie
2 years ago
I'm not sure, but I think sharing rules could also work in this scenario.
RO
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?
IS
Isaac
2 years ago
I agree with Shayne, field-level security makes sense for this requirement.
EM
Emile
2 years ago
Classic encryption? That's about as useful as a solar-powered flashlight on the dark side of the moon.
DO
Dorcas
2 years ago
Field-level security is the best option to control access to the Jupiter field.
MY
My
2 years ago
Filtered view would be the way to go for this requirement.
VI
Vivan
2 years ago
Sharing rules? I'd rather share my telescope with a black hole than try to figure out this mess.
CA
Caprice
2 years ago
D) Sharing rules
JU
Jutta
2 years ago
C) Field-level security
MI
Mickie
2 years ago
B) Filtered view
LE
Leonor
2 years ago
A) Classic encryption
PE
Peggy
2 years ago
Filtered view? More like 'filtered common sense'. Just give the Outer Planets profile access and call it a day, folks.
RE
Rene
2 years ago
I agree, just set up the Outer Planets profile with access.
GA
Gayla
2 years ago
Filtered view is the way to go.
SH
Shayne
2 years ago
I think the app builder should use field-level security.
AL
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.
OL
Oliva
2 years ago
C) Field-level security
CO
Coletta
2 years ago
Yeah, no need to complicate things with field-level security when filtered view can do the job.
CR
Crista
2 years ago
I agree, just use filtered view to show the Jupiter field to Outer Planets profile users.
TI
Tijuana
2 years ago
C) Field-level security
GL
Glendora
2 years ago
True, field-level security seems like overkill for this situation.