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

Adobe Exam AD0-E716 Topic 8 Question 35 Discussion

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

An Adobe Commerce developer has created a module that adds a product attribute to all product types via a Data Patch-According to best practices, how would the developer ensure this product attribute is removed in the event that the module is uninstalled at a later date?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Renay
2 months ago
I'm not sure, but I think making the Data Patch implement PatchRevertableInterface could also work to remove the attribute.
upvoted 0 times
...
Janessa
2 months ago
Option C, no doubt. Gotta love those revertable patches - it's like having an 'undo' button for your database changes!
upvoted 0 times
...
Howard
2 months ago
Option C ftw! I'd rather not have to remember to manually remove that attribute every time I uninstall the module. Revertability is the way to go.
upvoted 0 times
Judy
28 days ago
User 4: Revertability is key in maintaining a clean and efficient system when working with modules in Adobe Commerce.
upvoted 0 times
...
Yong
29 days ago
User 3: It definitely simplifies the process and reduces the risk of forgetting to remove the attribute manually.
upvoted 0 times
...
Elsa
1 months ago
User 2: I agree, having the revert method implemented in the Data Patch makes it much easier for developers and merchants.
upvoted 0 times
...
Kiley
2 months ago
Option C sounds like the best approach for ensuring the product attribute is removed when uninstalling the module.
upvoted 0 times
...
...
Winifred
3 months ago
Ah, the age-old question of how to handle module uninstallation. Option C is definitely the way to go, no need to burden the merchants with manual cleanup.
upvoted 0 times
Raymon
2 months ago
Lauran: Manual cleanup can be a hassle, so having the module handle it automatically is definitely the way to go.
upvoted 0 times
...
Lauran
2 months ago
Absolutely, it's important to make the uninstall process as seamless as possible for merchants.
upvoted 0 times
...
Ocie
2 months ago
I agree, option C is the most efficient way to ensure proper cleanup.
upvoted 0 times
...
...
Vanda
3 months ago
I agree with Benton. That way, the uninstall method can be implemented to remove the product attribute.
upvoted 0 times
...
Benton
3 months ago
I think the best practice would be to add an Uninstall.php file to the module's Setup directory.
upvoted 0 times
...
Myra
3 months ago
I agree, Option C is the best practice here. Keeping the uninstall logic within the module itself is crucial for maintaining a clean and reliable system.
upvoted 0 times
Johnathon
2 months ago
Vi: Okay, I see the benefit of Option C now. Thanks for the insight.
upvoted 0 times
...
Pearlie
2 months ago
I agree with Pearlie, keeping the uninstall logic within the module is important.
upvoted 0 times
...
Vi
2 months ago
I disagree, I believe Option C is the best practice.
upvoted 0 times
...
Ronny
3 months ago
I think Option A is the way to go.
upvoted 0 times
...
...
Quentin
3 months ago
Option C looks like the way to go. Implementing the revert method in the Data Patch is the most straightforward approach to ensure the attribute is removed on uninstall.
upvoted 0 times
Teddy
2 months ago
I agree, having the Data Patch implement the revert method is the cleanest solution.
upvoted 0 times
...
Deeanna
2 months ago
Option C is definitely the best choice. It ensures the attribute is removed properly.
upvoted 0 times
...
...

Save Cancel