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 Experience Cloud Consultant Topic 4 Question 79 Discussion

Actual exam question for Salesforce's Experience Cloud Consultant exam
Question #: 79
Topic #: 4
[All Experience Cloud Consultant 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.


Contribute your Thoughts:

Vincent
2 months ago
CSS overrides? What is this, the stone age? Just use Field-Level Security and call it a day.
upvoted 0 times
...
Katlyn
2 months 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 months 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
10 days ago
User 4: I think we should go with utilizing the Developer Console with coding for more control.
upvoted 0 times
...
Rickie
13 days ago
User 3: I agree with Rickie, CSS overrides would be a simpler solution.
upvoted 0 times
...
Princess
23 days ago
User 2: That's a good idea, but I prefer using CSS overrides to hide unwanted fields.
upvoted 0 times
...
Evangelina
1 months ago
D) Utilize the Developer Console with coding to hide unwanted fields.
upvoted 0 times
...
Melvin
1 months ago
User 1: I think we should use Field-Level Security to limit the fields.
upvoted 0 times
...
Kara
1 months ago
C) Use Field-Level Security to remove access to the unwanted fields.
upvoted 0 times
...
Adelle
2 months ago
A) Utilize CSS overrides to hide unwanted fields.
upvoted 0 times
...
...
Kizzy
2 months ago
I prefer utilizing CSS overrides to hide unwanted fields. It's easier to implement.
upvoted 0 times
...
Princess
2 months ago
I agree with Kelvin. It's the most secure way to limit access to the fields.
upvoted 0 times
...
Noemi
3 months 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
3 months 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 months ago
D) Utilize the Developer Console with coding to hide unwanted fields.
upvoted 0 times
...
Claudio
2 months ago
C) Use Field-Level Security to remove access to the unwanted fields.
upvoted 0 times
...
Georgene
2 months ago
B) Create a page variation for the customer portal to hide unwanted fields.
upvoted 0 times
...
Leila
2 months ago
A) Utilize CSS overrides to hide unwanted fields.
upvoted 0 times
...
...
Kelvin
3 months ago
I think we should use Field-Level Security to remove access to the unwanted fields.
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