MENU
Ursa Major Solar would like to expose the custom object SolarPanels to its customer portal. This particular object contains 150 fields, and a majority of the fields are technical codes and internal information.
How should the administrator limit the fields available in the customer portal?
Suggested Answer: C
Get Premium Salesforce Certified Experience Cloud Consultant (EX-Con-101) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
To limit the fields available in the customer portal, the administrator should use Field-Level Security to remove access to the unwanted fields. Field-Level Security is a feature that allows the administrator to control the visibility and editability of fields for different profiles and permission sets. The administrator can use Field-Level Security to hide or make read-only the technical codes and internal information fields for the customer portal profile or permission set.
33 comments · newest first
SO
Sophia
11 months ago
Definitely not using the Developer Console for this.
DO
Donette
11 months ago
Surprised there's no mention of validation rules!
SH
Shawana
12 months ago
CSS overrides? That sounds risky!
ER
Erasmo
12 months ago
I think a page variation would be easier.
TA
Tawna
1 year ago
Field-Level Security is the way to go!
LO
Lorean
1 year ago
I recall a practice question about hiding fields, and I think field-level security was the answer there too.
LY
Lynsey
1 year ago
Creating a page variation sounds familiar, but I feel like it might be more complicated than just using field-level security.
GL
Glenna
1 year ago
I’m not entirely sure, but I think using CSS overrides might not be the best approach for this scenario.
ER
Ernest
1 year ago
I remember we discussed field-level security in class, and it seems like a solid way to control access to specific fields.
JU
Jutta
1 year ago
Whoa, 150 fields? That's a lot to deal with. I'm not super familiar with all the Salesforce security features, but the Field-Level Security option sounds like the way to go. Probably the cleanest and most maintainable solution.
LI
Lilli
1 year ago
Okay, this is a good one. I'm leaning towards the Field-Level Security solution since it's a built-in Salesforce feature and seems like the most direct way to control field access. The other options seem a bit hacky or require more custom development.
LU
Lucia
1 year ago
Hmm, 150 fields is a lot to manage. I'm not sure if CSS overrides or page variations are the best approach here. I'd probably go with the Field-Level Security option to selectively hide the technical fields.
DA
Daniel
1 year ago
This seems like a straightforward question about limiting fields in a customer portal. I think the key is to use the appropriate Salesforce security features to control field visibility.
DA
Danilo
1 year ago
External ID field is definitely the way to go here. That's the standard approach for integrating with legacy systems and ensuring data integrity.
VI
Vincent
2 years ago
CSS overrides? What is this, the stone age? Just use Field-Level Security and call it a day.
KA
Katlyn
2 years ago
A) Utilize CSS overrides to hide unwanted fields. This could work, but it's not the most robust or maintainable solution.
LI
Ligia
2 years ago
D) Utilize the Developer Console with coding to hide unwanted fields. Although this may be more complex, it offers more granular control over the field visibility.
BE
Bev
2 years ago
User 4: I think we should go with utilizing the Developer Console with coding for more control.
RI
Rickie
2 years ago
User 3: I agree with Rickie, CSS overrides would be a simpler solution.
PR
Princess
2 years ago
User 2: That's a good idea, but I prefer using CSS overrides to hide unwanted fields.
EV
Evangelina
2 years ago
D) Utilize the Developer Console with coding to hide unwanted fields.
ME
Melvin
2 years ago
User 1: I think we should use Field-Level Security to limit the fields.
KA
Kara
2 years ago
C) Use Field-Level Security to remove access to the unwanted fields.
AD
Adelle
2 years ago
A) Utilize CSS overrides to hide unwanted fields.
KI
Kizzy
2 years ago
I prefer utilizing CSS overrides to hide unwanted fields. It's easier to implement.
PR
Princess
2 years ago
I agree with Kelvin. It's the most secure way to limit access to the fields.
NO
Noemi
2 years ago
B) Create a page variation for the customer portal to hide unwanted fields. This allows for better control and flexibility in managing the displayed fields.
AL
Alberto
2 years ago
C) Use Field-Level Security to remove access to the unwanted fields. This is the most straightforward and secure way to limit field visibility in the customer portal.
JA
James
2 years ago
D) Utilize the Developer Console with coding to hide unwanted fields.
CL
Claudio
2 years ago
C) Use Field-Level Security to remove access to the unwanted fields.
GE
Georgene
2 years ago
B) Create a page variation for the customer portal to hide unwanted fields.
LE
Leila
2 years ago
A) Utilize CSS overrides to hide unwanted fields.
KE
Kelvin
2 years ago
I think we should use Field-Level Security to remove access to the unwanted fields.