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?

AUtilize CSS overrides to hide unwanted fields.

BCreate a page variation for the customer portal to hide unwanted fields.

CUse Field-Level Security to remove access to the unwanted fields.

DUtilize the Developer Console with coding to hide unwanted fields.

Show Suggested 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:

Submit Cancel

Sophia

3 months ago

Definitely not using the Developer Console for this.

upvoted 0 times

...

Donette

3 months ago

Surprised there's no mention of validation rules!

upvoted 0 times

...

Shawana

3 months ago

CSS overrides? That sounds risky!

upvoted 0 times

...

Erasmo

4 months ago

I think a page variation would be easier.

upvoted 0 times

...

Tawna

4 months ago

Field-Level Security is the way to go!

upvoted 0 times

...

Lorean

4 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

4 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

4 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

5 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

5 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

5 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

5 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

5 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

5 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

1 year ago

CSS overrides? What is this, the stone age? Just use Field-Level Security and call it a day.

upvoted 0 times

...

Katlyn

1 year 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

1 year 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

1 year ago

User 4: I think we should go with utilizing the Developer Console with coding for more control.

upvoted 0 times

...

Rickie

1 year ago

User 3: I agree with Rickie, CSS overrides would be a simpler solution.

upvoted 0 times

...

Princess

1 year ago

User 2: That's a good idea, but I prefer using CSS overrides to hide unwanted fields.

upvoted 0 times

...

Evangelina

1 year ago

D) Utilize the Developer Console with coding to hide unwanted fields.

upvoted 0 times

...

Melvin

1 year ago

User 1: I think we should use Field-Level Security to limit the fields.

upvoted 0 times

...

Kara

1 year ago

C) Use Field-Level Security to remove access to the unwanted fields.

upvoted 0 times

...

Adelle

1 year ago

A) Utilize CSS overrides to hide unwanted fields.

upvoted 0 times

...

Kizzy

1 year ago

I prefer utilizing CSS overrides to hide unwanted fields. It's easier to implement.

upvoted 0 times

...

Princess

1 year ago

I agree with Kelvin. It's the most secure way to limit access to the fields.

upvoted 0 times

...

Noemi

1 year 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

1 year 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