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-E706 Exam - 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:

0/2000 characters
Submit Cancel
Flo
4 months ago
I'm surprised there's no mention of clearing cache after disabling!
upvoted 0 times
...
Jerry
5 months ago
Wait, can you really just delete it from git?
upvoted 0 times
...
Helene
5 months ago
C sounds risky, you shouldn't leave it in config.php.
upvoted 0 times
...
Javier
5 months ago
I think B is better for production.
upvoted 0 times
...
Ronnie
5 months ago
Option A is the way to go!
upvoted 0 times
...
Michel
6 months ago
I don't think deleting the module from the git repository is the right approach. It seems like we should keep the config.php file updated instead.
upvoted 0 times
...
Trina
6 months ago
I feel like we discussed the importance of committing the config.php file after disabling a module, but I can't recall if that applies to all environments.
upvoted 0 times
...
Delfina
6 months ago
I think option A sounds familiar, but I’m a bit confused about whether we need to remove the database tables manually or if that happens automatically.
upvoted 0 times
...
Paris
6 months ago
I remember we practiced disabling modules, but I'm not sure if it's best to do it locally or directly on production.
upvoted 0 times
...
Lachelle
6 months ago
I'm leaning towards option D. Removing the module line from config.php on the local environment and then deploying seems like the safest way to fully remove the module and its database tables.
upvoted 0 times
...
Joye
6 months ago
Option C seems risky to me. Deleting the module from the repo while leaving the config.php record intact could cause issues. I'd want to make sure the module is fully removed, so I'd lean towards A or D.
upvoted 0 times
...
Chantay
6 months ago
I think the key here is that the module uses declarative schema. That means the database changes are managed through the module's setup scripts, not manually. So I'd go with option A - disable the module and let Magento handle the rest.
upvoted 0 times
...
Evan
6 months ago
Hmm, I'm a bit unsure about this one. The question mentions the module uses declarative schema, so I'm not sure if just disabling it will remove the database tables. Maybe option B or D would be safer?
upvoted 0 times
...
Alethea
6 months ago
This seems straightforward. I'd go with option A - disable the module on the local environment and then commit and deploy the config.php file.
upvoted 0 times
...
Joanne
7 months ago
I'm a bit confused by this question. Is there a specific setting or configuration I need to change to make the "Interesting field" a selected field? The options don't seem very clear to me.
upvoted 0 times
...
Rasheeda
7 months ago
Ah, I remember learning about this in class. gRPC is designed for efficient data transfer, so it supports binary formats like ProtoBuf rather than text-based ones like XML or YAML. I'll go with ProtoBuf and JSON as my two choices.
upvoted 0 times
...
Tori
11 months 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
11 months 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
Deonna
10 months ago
C) Delete the module from the git repository leaving the record in app/etc/config.php Intact and deploy the changes
upvoted 0 times
...
Lera
10 months 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
...
Ivan
10 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
...
...
Juan
11 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
Tonette
10 months ago
C) 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
10 months 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
11 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
...
...
Arlie
12 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
10 months 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
11 months 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
11 months 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
11 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
1 year 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
11 months ago
B) Exactly, it's always best to follow the correct steps to avoid any potential problems.
upvoted 0 times
...
Noelia
11 months 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
11 months ago
A) Yes, that way we can ensure the database tables are removed without causing any issues.
upvoted 0 times
...
Jani
11 months ago
B) Sounds good. It's important to make sure the changes are properly deployed to production.
upvoted 0 times
...
Thurman
11 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
...
Kimberlie
12 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
1 year 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
1 year 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
1 year ago
I think option A is the correct one. We should disable the module on the local environment first.
upvoted 0 times
...

Save Cancel