Adobe Exam AD0-E716 Topic 8 Question 35 Discussion

Actual exam question for Adobe's AD0-E716 exam

Question #: 35
Topic #: 8

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?

AAdd an Uninstall.php file extending \l1agento\Framework\Setup\UninstallInterface tO the module's Setup directory and implement the uninstall
method.

BAdd 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.

CMake the Data Patch implement \Magento\Framework\setup\Patch\PatchRevertabieinterface and implement the revert method to remove the product attribute.

Show Suggested 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:

Submit Cancel

Renay

1 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

1 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

1 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

Elsa

7 hours 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

14 days ago

Option C sounds like the best approach for ensuring the product attribute is removed when uninstalling the module.

upvoted 0 times

...

2 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

25 days ago

Vi: Okay, I see the benefit of Option C now. Thanks for the insight.

upvoted 0 times

...

Pearlie

26 days ago

I agree with Pearlie, keeping the uninstall logic within the module is important.

upvoted 0 times

...

Vi

1 months ago

I disagree, I believe Option C is the best practice.

upvoted 0 times

...

Ronny

1 months ago

I think Option A is the way to go.

upvoted 0 times

...

Quentin

2 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

1 months ago

I agree, having the Data Patch implement the revert method is the cleanest solution.

upvoted 0 times

...

Deeanna

1 months ago

Option C is definitely the best choice. It ensures the attribute is removed properly.

upvoted 0 times

...