Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Experience Cloud Consultant (EX-Con-101) Exam - Topic 4 Question 79 Discussion

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?
C) Use Field-Level Security to remove access to the unwanted fields.
A) Utilize CSS overrides to hide unwanted fields.
B) Create a page variation for the customer portal to hide unwanted fields.
D) Utilize the Developer Console with coding to hide unwanted fields.

Salesforce Certified Experience Cloud Consultant (EX-Con-101) Exam - Topic 4 Question 79 Discussion

Actual exam question for Salesforce's Salesforce Certified Experience Cloud Consultant (EX-Con-101) exam
Question #: 79
Topic #: 4
[All Salesforce Certified Experience Cloud Consultant (EX-Con-101) Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: C

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.


by Gearldine at Sep 16, 2024, 06:05 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Experience Cloud Consultant (EX-Con-101) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sophia
9 months ago
Definitely not using the Developer Console for this.
upvoted 0 times
...
Donette
10 months ago
Surprised there's no mention of validation rules!
upvoted 0 times
...
Shawana
10 months ago
CSS overrides? That sounds risky!
upvoted 0 times
...
Erasmo
10 months ago
I think a page variation would be easier.
upvoted 0 times
...
Tawna
10 months ago
Field-Level Security is the way to go!
upvoted 0 times
...
Lorean
10 months ago
I recall a practice question about hiding fields, and I think field-level security was the answer there too.
upvoted 0 times
...
Lynsey
11 months ago
Creating a page variation sounds familiar, but I feel like it might be more complicated than just using field-level security.
upvoted 0 times
...
Glenna
11 months ago
I’m not entirely sure, but I think using CSS overrides might not be the best approach for this scenario.
upvoted 0 times
...
Ernest
11 months ago
I remember we discussed field-level security in class, and it seems like a solid way to control access to specific fields.
upvoted 0 times
...
Jutta
11 months 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.
upvoted 0 times
...
Lilli
11 months 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.
upvoted 0 times
...
Lucia
11 months 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.
upvoted 0 times
...
Daniel
11 months 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.
upvoted 0 times
...
Danilo
11 months 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.
upvoted 0 times
...
Vincent
2 years ago
CSS overrides? What is this, the stone age? Just use Field-Level Security and call it a day.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
Bev
2 years ago
User 4: I think we should go with utilizing the Developer Console with coding for more control.
upvoted 0 times
...
Rickie
2 years ago
User 3: I agree with Rickie, CSS overrides would be a simpler solution.
upvoted 0 times
...
Princess
2 years ago
User 2: That's a good idea, but I prefer using CSS overrides to hide unwanted fields.
upvoted 0 times
...
Evangelina
2 years ago
D) Utilize the Developer Console with coding to hide unwanted fields.
upvoted 0 times
...
Melvin
2 years ago
User 1: I think we should use Field-Level Security to limit the fields.
upvoted 0 times
...
Kara
2 years ago
C) Use Field-Level Security to remove access to the unwanted fields.
upvoted 0 times
...
Adelle
2 years ago
A) Utilize CSS overrides to hide unwanted fields.
upvoted 0 times
...
...
Kizzy
2 years ago
I prefer utilizing CSS overrides to hide unwanted fields. It's easier to implement.
upvoted 0 times
...
Princess
2 years ago
I agree with Kelvin. It's the most secure way to limit access to the fields.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
James
2 years ago
D) Utilize the Developer Console with coding to hide unwanted fields.
upvoted 0 times
...
Claudio
2 years ago
C) Use Field-Level Security to remove access to the unwanted fields.
upvoted 0 times
...
Georgene
2 years ago
B) Create a page variation for the customer portal to hide unwanted fields.
upvoted 0 times
...
Leila
2 years ago
A) Utilize CSS overrides to hide unwanted fields.
upvoted 0 times
...
...
Kelvin
2 years ago
I think we should use Field-Level Security to remove access to the unwanted fields.
upvoted 0 times
...

Save Cancel