You are developing a module and need to add another column to a table introduced by another module MyCompany_MyModule via db schema.
How do you do that?

• A.Run a command: bin/magento setup:db-schema:upgrade <table> <column definition>
• B.Create a etc/db_schema.xml file in your module, add the column and run bin/magento setup:upgrade
• C.Create a etc/db_schema_whitelist.json file in your module, add the column and run bin/magento setup:upgrade
• D.Create a etc/db.xml file in your module, add the column and run bin/magento setup:db-schema:upgrade

Comment: *

Name: *

Email: *

Verification: *

You are implementing a customization of the sales management within a module MyCompany_MySalesProcess. You have created several event observers to add the custom functionality. Each observer is a separate class, but they require some common functionality.
How do you implement the common functionality in the event observers, keeping maintainability and testability in mind?

• A.You create a regular class implementing the common functionality as public methods and use constructor injection to make them available to the observers.
• B.You create a regular class implementing the common functionality as public static methods and call those from the observers.
• C.You create a trait with the common methods and use the trait in the observer classes.
• D.You create an abstract class AbstractObserver with the common methods and extend the observer classes from it.

Comment: *

Name: *

Email: *

Verification: *

You are building CLI that use the console to create a customer account with our custom command as like php bin/magento customer:user:create --customer-firstname="Mahin" --customer-lastname="Rahman" --customer-email="[email protected]" --customer-password="mahin@123" --website="1"
using: protected function configure() { $this->setName('customer:user:create') - >setDescription('Create new customer') ->setDefinition($this->getOptionsList()); } protected function getOptionsList(){ return [
------------------]; } Which below Option are not required in blank? (Choose 2)

• A.new InputOption(Customer::KEY_LASTNAME, null, InputOption::VALUE_REQUIRED, '(Required) Customer last name'),
• B.new InputOption(Customer::KEY_FIRSTNAME, null, InputOption::VALUE_REQUIRED, '(Required) Customer first name'),
• C.new InputOption(Customer::KEY_PASSWORD, null, InputOption::VALUE_REQUIRED, '(Required) Customer password'),
• D.new InputOption(Customer::KEY_WEBSITE, null, InputOption::VALUE_REQUIRED, '(Required) Website ID'),
• E.new InputOption(Customer::KEY_EMAIL, null, InputOption::VALUE_REQUIRED, '(Required) Customer email'),
• F.new InputOption(Customer::KEY_SENDEMAIL, 0, InputOption::VALUE_OPTIONAL, '(1/0) Send email? (default 0)')
• G.new InputOption(Customer::KEY_STORE, null, InputOption::VALUE_REQUIRED, '(Required) Store ID'),

Comment: *

Name: *

Email: *

Verification: *

A module you are developing requires the addition of new routes that should be accessible in the store front.
Where do you define your module's frontName?

• A.etc/frontend/config.xml
• B.etc/frontend/routes.xml
• C.etc/config.xml
• D.etc/routes.xml

Comment: *

Name: *

Email: *

Verification: *

The developer is required to convert a modules database scripts from old install/upgrade setup files to a data patches format and does not want to apply database changes that were already done by install/upgrade scripts.
The current module version is 1.5A
What would be the recommended solution to skip changes that were already applied via old format (install/upgrade scripts)?

• A.Implement PatchVersioninterface and return 1.5.4 on the getversion() method.
• B.Inside apply() method, check for module version and run the code it version is less than 134,
• C.This is not possible. A module cannot implement both data patch and install scripts.

Comment: *

Name: *

Email: *

Verification: *