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

Actual exam question for Salesforce's Salesforce Certified Platform User Experience Designer (Plat-UX-101) exam

Question #: 68
Topic #: 2

[All Salesforce Certified Platform User Experience Designer (Plat-UX-101) Questions]

A UX Designer at Cloud Kicks is having difficulty getting its developers to see why the design changes would improve the user experience.

How should the designer help mitigate pushback from developers?

AA Share research notes from previous projects with them.

BGet buy-in from the development lead first and let them persuade others.

CWork together on setting up UX Indicators.

Show Suggested Answer

Suggested Answer: A

To optimize the relationship between two objects in Salesforce, such as Container and Container Bids, where there is a need for a tight relationship and cascading delete functionality, a Master-Detail relationship is most suitable. This type of relationship has the following characteristics:

Cascading Delete: When a record in the master (or parent) object is deleted, all related detail (or child) records are automatically deleted. This ensures data integrity and aligns with the requirement that Container Bids should be deleted when their associated Container is deleted.

Tight Coupling: A Master-Detail relationship creates a strong linkage between the two objects, where the detail (child) record's existence is dependent on the master (parent) record. This is appropriate for scenarios where the child record should not exist without its parent.

Options B (Hierarchical Lookup) and C (Many-to-one Lookup) do not provide the same level of dependency and cascading delete functionality inherent in a Master-Detail relationship.

Reference: Salesforce's official documentation provides extensive information on different types of relationships between objects, including Master-Detail relationships. The Salesforce Developer Documentation is a valuable resource for understanding how to set up and use these relationships to ensure data integrity and optimize application design.

by Jess at Sep 17, 2024, 02:13 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:

Submit Cancel

Lenora

3 months ago

Wait, are developers really that resistant to design changes?

upvoted 0 times

...

Mila

3 months ago

Working together on UX Indicators could really help!

upvoted 0 times

...

Jenise

3 months ago

Getting the dev lead on board first sounds smart!

upvoted 0 times

...

Sunshine

4 months ago

Not sure if that’ll change their minds though.

upvoted 0 times

...

Monroe

4 months ago

I think sharing research notes is a solid move.

upvoted 0 times

...

Peggie

4 months ago

I remember a practice question where collaboration was key, so maybe involving developers early on could ease their concerns.

upvoted 0 times

...

Wilda

4 months ago

Working together on UX Indicators seems like a good way to align goals, but I wonder how we would measure success effectively.

upvoted 0 times

...

Edelmira

4 months ago

Getting buy-in from the development lead sounds like a solid strategy, but what if they don't fully agree with the design changes either?

upvoted 0 times

...

Sena

5 months ago

I think sharing research notes could help, but I'm not sure if developers would actually find them convincing.

upvoted 0 times

...

Felix

5 months ago

This is a tough one. I'm leaning towards option A - the research notes could be really compelling. But I'm also intrigued by option C. Maybe a combination of the two could work well? Sharing the research and then collaborating on the UX indicators.

upvoted 0 times

...

Sage

5 months ago

Ooh, I like the idea of working together on UX indicators in option C. That could be a great way to get the developers more invested in the process and help them see the value of the changes. I might go with that one.

upvoted 0 times

...

Stephen

5 months ago

Hmm, I'm not sure. Getting buy-in from the development lead first seems like it could be a smart strategy, but I'm worried it might come across as going behind the other developers' backs. Option B is interesting, but I'd want to think it through a bit more.

upvoted 0 times

...

Lorrie

5 months ago

This seems like a tricky situation. I'm thinking option A might be a good place to start - sharing research notes could really help the developers understand the reasoning behind the design changes.

upvoted 0 times

...

Amalia

5 months ago

I remember applying filters in similar questions, but I can't tell if that's the most flexible method for delivering flagged messages.

upvoted 0 times

...

Francine

10 months ago

Haha, I bet the developers are like, 'UX? What's that? We just write the code, man.' But seriously, communication is key here.

upvoted 0 times

Monte

9 months ago

A) Share research notes from previous projects with them.

upvoted 0 times

...

Gertude

9 months ago

Yeah, developers can sometimes be resistant to change.

upvoted 0 times

...

Cristal

9 months ago

C) Work together on setting up UX Indicators.

upvoted 0 times

...

Colette

9 months ago

B) Get buy-in from the development lead first and let them persuade others.

upvoted 0 times

...

Laquanda

10 months ago

A) Share research notes from previous projects with them.

upvoted 0 times

...

Ivory

10 months ago

I like the idea of working together on UX indicators. That collaborative approach can really help foster a shared understanding.

upvoted 0 times

...

Mitzie

10 months ago

Definitely agree that getting the development lead's buy-in first is key. If the team sees that the lead is on board, they'll be more likely to listen.

upvoted 0 times

...

Ardella

10 months ago

Sharing the research notes is a great way to get the developers on board. Seeing the data will help them understand the reasoning behind the design changes.

upvoted 0 times