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 Exam AD0-E706 Topic 11 Question 31 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 31
Topic #: 11
[All AD0-E706 Questions]

You need to disable a module on a Magento Commerce 2 3 Cloud project and remove its database tables The module uses the declarative schema system to manage its database changes

Which action do you take?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Darrin at May 01, 2024, 06:46 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Tori
20 days ago
Ah, the joys of Magento! Where every action is a potential minefield. I wonder if the developers have a special room just for throwing darts at the config.php file.
upvoted 0 times
...
Shannan
24 days ago
Removing the module line from the config.php file on the local environment and deploying it? Hmm, I'm not sure that's a good idea. Wouldn't that just hide the module rather than properly disabling it?
upvoted 0 times
...
Juan
1 months ago
Deleting the module from the git repository and leaving the record in config.php? That's a recipe for disaster! You'd end up with a mismatch between the code and the configuration, which could lead to all sorts of problems.
upvoted 0 times
Darrel
1 days ago
B) Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file
upvoted 0 times
...
Pauline
20 days ago
A) Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file
upvoted 0 times
...
...
Arlie
1 months ago
Disabling the module directly on the production environment? That's a bold move! I'd be worried about any potential data loss or compatibility issues. Better to test it out on the local environment first.
upvoted 0 times
Jose
3 days ago
B) That sounds like a good plan. Better safe than sorry when it comes to making changes on a live site.
upvoted 0 times
...
Paola
9 days ago
A) Once you've tested it and everything works fine, you can then deploy the changes to the production environment.
upvoted 0 times
...
Lemuel
17 days ago
B) Yeah, I agree. It's always safer to test it out on the local environment first before making changes on production.
upvoted 0 times
...
Judy
1 months ago
A) Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file
upvoted 0 times
...
...
Edda
2 months ago
Disabling the module on the local environment and committing the config.php file sounds like the right approach. That way, the change is deployed to the production environment without any database issues.
upvoted 0 times
Viva
14 days ago
B) Exactly, it's always best to follow the correct steps to avoid any potential problems.
upvoted 0 times
...
Noelia
20 days ago
B) Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file
upvoted 0 times
...
Harley
21 days ago
A) Yes, that way we can ensure the database tables are removed without causing any issues.
upvoted 0 times
...
Jani
22 days ago
B) Sounds good. It's important to make sure the changes are properly deployed to production.
upvoted 0 times
...
Thurman
23 days ago
A) Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file
upvoted 0 times
...
Kimberlie
1 months ago
A) Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file
upvoted 0 times
...
...
Allene
2 months ago
I'm not sure, but I think option D makes sense. We should remove the module line from the config file on the local environment.
upvoted 0 times
...
Anthony
2 months ago
I disagree, I believe option B is the way to go. We should disable the module on the production environment.
upvoted 0 times
...
Verlene
2 months ago
I think option A is the correct one. We should disable the module on the local environment first.
upvoted 0 times
...

Save Cancel