New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E716 Exam - Topic 8 Question 34 Discussion

Actual exam question for Adobe's AD0-E716 exam
Question #: 34
Topic #: 8
[All AD0-E716 Questions]

An Adobe Commerce developer successfully added a new column to the customers grid. This column needs the data to be formatted before showing its content in the grid.

According to best practices, how would the developer add the custom logic to render the column?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Sanjuana
3 months ago
Not sure about the after plugin approach, feels a bit hacky.
upvoted 0 times
...
Yoko
3 months ago
Definitely A, it keeps things clean and efficient.
upvoted 0 times
...
Ronald
3 months ago
Surprised that C is even an option, seems too complex!
upvoted 0 times
...
Gayla
4 months ago
I think B is more straightforward though.
upvoted 0 times
...
Christiane
4 months ago
Option A is the best practice for this!
upvoted 0 times
...
Nichelle
4 months ago
I recall that using an after plugin is often recommended for modifying existing functionality, so maybe A is the right choice after all.
upvoted 0 times
...
Cammy
4 months ago
I’m leaning towards option C, but I’m uncertain about overriding the DataProvider class. It feels like it might be too much for just formatting a column.
upvoted 0 times
...
Lashandra
4 months ago
I remember practicing with similar questions, and I feel like extending the class in option B could be a valid way to add custom logic, but it seems a bit more complex.
upvoted 0 times
...
Merrilee
5 months ago
I think option A sounds familiar, but I'm not entirely sure if using an after plugin is the best approach for rendering a column.
upvoted 0 times
...
Tracey
5 months ago
This is a good one. I think option B is the way to go, but I'd want to double-check the Magento documentation to make sure I'm following the best practices. Extending the column class and adding the logic in prepareDataSource seems like the most straightforward approach.
upvoted 0 times
...
Henriette
5 months ago
I'm a bit confused by the wording of this question. I'm not sure if I fully understand the difference between the options. I'll need to re-read the question and think it through carefully before answering.
upvoted 0 times
...
Anika
5 months ago
Ah, I've done something like this before. I'm pretty confident that option B is the correct answer. Creating a custom column class and adding the logic there is the cleanest way to handle this requirement.
upvoted 0 times
...
Vicky
5 months ago
This seems like a straightforward question. I think option B is the way to go - creating a custom column class and adding the logic in the prepareDataSource method.
upvoted 0 times
...
Izetta
5 months ago
Hmm, I'm a bit unsure about this one. I'm trying to decide between options A and B. I'll need to review the best practices for extending Magento UI components to make sure I choose the right approach.
upvoted 0 times
...
Bong
1 year ago
I prefer option C because it allows for more flexibility in customizing the logic.
upvoted 0 times
...
Jutta
1 year ago
I disagree, I believe option B is more appropriate.
upvoted 0 times
...
Maryann
1 year ago
You know, this reminds me of the time I had to format a column that displayed customers' credit card numbers. Talk about a headache!
upvoted 0 times
Phillip
1 year ago
Oh wow, dealing with credit card numbers must have been challenging. It's important to handle sensitive data like that carefully.
upvoted 0 times
...
Lezlie
1 year ago
C) Override the Magento\\Customer\\Ui\\Component\\DataProvider Class using a preference. Override the getData() method and add the custom logic per row.
upvoted 0 times
...
Gennie
1 year ago
A) Create an after plugin for Magento\\Ui\\Component\\Listing\\Columns\\Column::prepareColumn(). Add the custom logic within the afterPrepareColumn method.
upvoted 0 times
...
Terina
1 year ago
B) Create a custom class extending Magento\\Ui\\Component\\Listing\\Columns\\Column. Add the custom logic within the prepareDataSource method. Add an attribute class to the column node within the module's customer_listing.xml.
upvoted 0 times
...
...
Kerry
1 year ago
Option B looks good, but I wonder if there's a way to do it without creating a custom class. Hmm, something to look into.
upvoted 0 times
...
Johnna
1 year ago
Haha, I bet the developer who wrote this question has dealt with their fair share of customer grids! Option B it is.
upvoted 0 times
Chan
1 year ago
Definitely, adding an attribute class to the column node is the way to go.
upvoted 0 times
...
Tasia
1 year ago
Yeah, creating a custom class and adding the logic in prepareDataSource method makes sense.
upvoted 0 times
...
Oretha
1 year ago
I agree, Option B seems like the best choice.
upvoted 0 times
...
...
Goldie
1 year ago
I agree with Anabel, the steps outlined in Option B align with best practices for extending the UI components.
upvoted 0 times
Isaiah
1 year ago
Salina: Definitely, following these steps will ensure the new column is formatted correctly in the customers grid.
upvoted 0 times
...
Bok
1 year ago
Agreed, also adding an attribute class to the column node in customer_listing.xml is important.
upvoted 0 times
...
Salina
1 year ago
Yeah, extending the Column class and adding custom logic in prepareDataSource is the best practice.
upvoted 0 times
...
Carmen
1 year ago
I think Option B is the way to go.
upvoted 0 times
...
...
Beth
1 year ago
I think option A is the best choice.
upvoted 0 times
...
Anabel
1 year ago
Option B seems to be the most comprehensive approach, covering all the necessary steps.
upvoted 0 times
Mindy
1 year ago
Agreed, it seems like the most comprehensive approach for adding custom logic to render the column.
upvoted 0 times
...
Tina
1 year ago
I think option B is the way to go, it covers all the necessary steps.
upvoted 0 times
...
...

Save Cancel