Magento-2-Certified-Associate-Developer Sample Questions Answers

By adding the attribute like customer_address_billing2 and customizing both My Account and Checkout functionality to use that new attribute

By changing the System Configuration setting: Customer>Allow multiple billing addresses to Yes

By altering the customer_entity table, adding the field billing_address2, and customizing both My Account and Checkout functionality to use that new field

This is out-of-the box functionality

Specify a preference in di.xml to map SearchCriteriaBuilder to SearchCriteriaInterface

Use dependency injection to load an instance of the SearchCriteria class

Change the getList parameter to: $searchCriteriaBuilder->addFilter(‘state’, ‘processing’)->create()

Clear generated code to get a new version of SearchCriteriaBuilder

Specify item XML in the file etc/adminhtml/menu/marketing/seo/menu.xml

Specify parent=”Magento_Sitemap::catalog_sitemap”

Specify parent=”Magento_Backend::marketing_seo”

Specify sortOrder=”100”

Register my_module route for the AdminRouter in MyCompany/MyModule/etc/adminhtml/di.xml

Create a new menu item in MyCompany/MyModule/etc/adminhtml/menu.xml

Specify the my_module/custom_entity URL using a @route annotation in the action controller execute() method

Register my_module route in MyCompany/MyModule/etc/adminhtml/routes.xml

Create the etc/db_schema.xml file and specify disable=”true” on the column

Modify the original etc/db_schema.xml file and remove the column from there

Create a SchemaPatch file and remove the column programmatically

Copy the etc/db_schema.xml file into your module and remove the column from your copy

Create a view model and specify an OrderRepositoryInterface argument in the _construct method

In your template, add the following:$orderRepository=ObjectManager::getInstance()->get(OrderRepositoryInterface::class);

In your block, add a method with the following:return ObjectManager::getInstance()->get(OrderRepositoryInterface::class);

In your template, add the following:$orderRepository = new OrderRepository();

etc/webapi_rest/events.xml

etc/adminhtml/events.xml

etc/webapi/rest_events.xml

etc/events.xml

Customer password reset

Clearing cache

Codebase deployment from developer machine to staging server

Administrator account creation

Implement \MyCompany\MyModule\Cron\NewsLetterSender::execute and register it in etc/crontab/di.xml

Implement \MyCompany\MyModule\Cron\NewsLetterSender::execute and register it in etc/crontab/.xml

Make sure bin/magento cron:run is added to the system crontab

Register the plugin for \Magento\Customer\Model\Customer::authenticate in etc/crontab.xml

There is no risk posed as long as each event observer specifies a correct sortOrder. Nothing needs to be changed.

Event observers are fired in alphabetical order of the observer name. There is no risk here.

Magento only supports one observer per event. These observers will need to be combined into a single point of customization.

Order of listener execution cannot be guaranteed, resulting in a fragile implementation. This code should be re-worked using plugins

Create an entry in etc/di.xml and add the argument eventPrefix with the value of vendor

Declare the $_eventPrefix property in your vendor model and set it to vendor

You must implement all appropriate methods and fire the events manually

Ensure that the primary key in the corresponding table is named vendor_id

Option A

Option B

Option C

Option D