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

Adobe AD0-E716 Exam - Topic 8 Question 35 Discussion

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?
C) Make the Data Patch implement \Magento\Framework\setup\Patch\PatchRevertabieinterface and implement the revert method to remove the product attribute.
A) Add an Uninstall.php file extending \l1agento\Framework\Setup\UninstallInterface tO the module's Setup directory and implement the uninstall method.
B) Add instructions to the module's README.md file instructing merchants and developers that they must manually remove this attribute if they want to uninstall the module.

Adobe AD0-E716 Exam - 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
Suggested Answer: C

According to the Develop data and schema patches guide for Magento 2 developers, data patches can also implement PatchRevertabieinterface to provide rollback functionality for their changes. The revert() method contains the instructions to undo the data modifications made by the patch. To ensure that the product attribute is removed when the module is uninstalled, the developer should make the data patch implement PatchRevertabieinterface and implement the revert method to remove the product attribute using EavSetupFactory or AttributeRepositoryInterface. Verified Reference: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/declarative-schema/data-patches.html


by Elenora at Sep 19, 2024, 02:27 AM

Limited Time Offer

25%

Off

Get Premium AD0-E716 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lenna
10 months ago
Can you really rely on the README for something like this? Seems risky.
upvoted 0 times
...
Dan
10 months ago
A is the way to go, no doubt about it!
upvoted 0 times
...
Gilberto
10 months ago
Wait, B? Seriously? Manual removal sounds like a nightmare!
upvoted 0 times
...
Christiane
10 months ago
I think C is better, it keeps everything clean and automated.
upvoted 0 times
...
Andra
10 months ago
Definitely A, that's the standard way to handle uninstalls!
upvoted 0 times
...
Peggie
11 months ago
I vaguely recall that using the uninstall method is the standard way to handle this, so I would lean towards option A as well.
upvoted 0 times
...
Nan
11 months ago
I feel like option B is not a good practice. Relying on users to manually remove attributes seems risky and could lead to leftover data.
upvoted 0 times
...
Donte
11 months ago
I'm not entirely sure, but I remember something about using the PatchRevertableInterface in similar questions. Could that be option C?
upvoted 0 times
...
Chun
11 months ago
I think option A sounds right since it mentions creating an Uninstall.php file, which is a common practice for cleanup during module uninstallation.
upvoted 0 times
...
Viki
11 months ago
Okay, I've got this. The best practice is to implement the Uninstall interface and handle the removal of the product attribute in the uninstall method. That way, the attribute will be properly cleaned up when the module is uninstalled. Option A is the way to go.
upvoted 0 times
...
Gearldine
11 months ago
Hmm, I'm a bit unsure about this one. Adding an Uninstall.php file sounds like the right approach, but I'm not totally confident. Maybe I should review the module uninstallation documentation again just to be sure.
upvoted 0 times
...
Lera
11 months ago
This seems like a straightforward question about best practices for module uninstallation. I think the key is to ensure the product attribute is properly removed, so option A looks like the way to go.
upvoted 0 times
...
Joaquin
11 months ago
I'm a little confused by this question. Wouldn't it be easier to just tell the merchants to manually remove the attribute if they uninstall the module? Option B seems like the simplest solution, but I'm not sure if that's considered best practice.
upvoted 0 times
...
Renay
2 years 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 years 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 years 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
2 years ago
User 4: Revertability is key in maintaining a clean and efficient system when working with modules in Adobe Commerce.
upvoted 0 times
...
Yong
2 years ago
User 3: It definitely simplifies the process and reduces the risk of forgetting to remove the attribute manually.
upvoted 0 times
...
Elsa
2 years 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 years ago
Option C sounds like the best approach for ensuring the product attribute is removed when uninstalling the module.
upvoted 0 times
...
...
Winifred
2 years 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 years 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 years ago
Absolutely, it's important to make the uninstall process as seamless as possible for merchants.
upvoted 0 times
...
Ocie
2 years ago
I agree, option C is the most efficient way to ensure proper cleanup.
upvoted 0 times
...
...
Vanda
2 years ago
I agree with Benton. That way, the uninstall method can be implemented to remove the product attribute.
upvoted 0 times
...
Benton
2 years ago
I think the best practice would be to add an Uninstall.php file to the module's Setup directory.
upvoted 0 times
...
Myra
2 years 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 years ago
Vi: Okay, I see the benefit of Option C now. Thanks for the insight.
upvoted 0 times
...
Pearlie
2 years ago
I agree with Pearlie, keeping the uninstall logic within the module is important.
upvoted 0 times
...
Vi
2 years ago
I disagree, I believe Option C is the best practice.
upvoted 0 times
...
Ronny
2 years ago
I think Option A is the way to go.
upvoted 0 times
...
...
Quentin
2 years 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 years ago
I agree, having the Data Patch implement the revert method is the cleanest solution.
upvoted 0 times
...
Deeanna
2 years ago
Option C is definitely the best choice. It ensures the attribute is removed properly.
upvoted 0 times
...
...

Save Cancel