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 Platform User Experience Designer (Plat-UX-101) Exam - Topic 6 Question 8 Discussion

A UX Designer is creating a custom To-Do List component to replace the standard Salesforce one. Their developer is using a parent-child Lightning Web Component (LWC) structure to build the component, creating a parent component for the list and a single repeated child component for each To-Do Item within the list.Which two impacts of the LWC's Shadow DOM should be considered when designing or developing the stylesheets for these components?Choose 2 answers
B) The CSS styles defined in the parent list component are not shared with the child items. and C) Any custom shared between the list and child items should be imported from a shared CSS file.
A) Any needed Saleforce Lightning Design System (SLDS) classes and styles must be imported into both the parent list and child items.
D) The CSS style defined in the parent list component are inherited by the child items

Salesforce Certified Platform User Experience Designer (Plat-UX-101) Exam - Topic 6 Question 8 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform User Experience Designer (Plat-UX-101) exam
Question #: 8
Topic #: 6
[All Salesforce Certified Platform User Experience Designer (Plat-UX-101) Questions]

A UX Designer is creating a custom To-Do List component to replace the standard Salesforce one. Their developer is using a parent-child Lightning Web Component (LWC) structure to build the component, creating a parent component for the list and a single repeated child component for each To-Do Item within the list.

Which two impacts of the LWC's Shadow DOM should be considered when designing or developing the stylesheets for these components?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B, C

by Nieves at May 03, 2022, 02:38 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform User Experience Designer (Plat-UX-101) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Alecia
7 months ago
I’m surprised about the Shadow DOM implications, didn’t think it was that complex!
upvoted 0 times
...
Nan
7 months ago
C makes sense, shared CSS is a good approach.
upvoted 0 times
...
Rosalyn
8 months ago
Wait, D is wrong, right? Child components don’t inherit styles!
upvoted 0 times
...
Theron
8 months ago
Totally agree with A, SLDS needs to be in both.
upvoted 0 times
...
Stevie
8 months ago
B is definitely true, styles don’t carry over.
upvoted 0 times
...
Rickie
8 months ago
I practiced a similar question, and I think any shared styles should come from a separate CSS file. So, option C sounds right to me.
upvoted 0 times
...
Desiree
8 months ago
I'm a bit unsure about the SLDS classes. I think they might need to be imported into both components, but I can't recall if that's always necessary.
upvoted 0 times
...
Kimberely
8 months ago
I remember that the Shadow DOM encapsulates styles, so I think the styles from the parent won't apply to the child components. That makes me lean towards option B.
upvoted 0 times
...
Laurel
8 months ago
I feel like the styles from the parent should be inherited by the child components, but I remember something about encapsulation in Shadow DOM that makes me doubt that. Maybe option D is incorrect?
upvoted 0 times
...
Patti
9 months ago
Okay, let's see. Profiles, Sharing Rules, and Role Hierarchy all sound like they could be ways to control record-level access. I'll have to double-check which one is not.
upvoted 0 times
...
Hailey
9 months ago
This seems like a tricky one. I'll need to think through the mobility group configuration carefully.
upvoted 0 times
...

Save Cancel