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

Comment: *

Name: *

Email: *

Verification: *

A merchant asks you to create a module that is able to process URLs with a custom structure that can contain any combination of a product type code, a partial name, and a 4-digit year in any order. The request path will look like this: /product/:type-code/:name-part/:year.
Which layer in the Magento request processing flow is suited for this kind of customization?

• A.HTTP Response
• B.Action controller
• C.Router
• D.Front controller

Comment: *

Name: *

Email: *

Verification: *

You have to install a new module on the production environment. All the module is adding a new product attribute. You enabled maintenance mode, copied the module code, run bin/magento setup:upgrade and disabled maintenance mode.
What two risks does this process pose? (Choose two.)

• A.It will clean static assets from the pub/static folder
• B.It will clean all caches which will cause a performance degradation
• C.It will void all active sessions
• D.The new attribute will be invisible on the storefront until the cache is cleaned manually

Comment: *

Name: *

Email: *

Verification: *

The constructor function for \Magento\Catalog\Model\Category contains this excerpt:

With the automatic dependency injection that Magento provides, how is the StoreManagerInterface resolved?

• A.Magento finds all classes that implement \Magento\Store\Model\StoreManagerInterface (ordered alphabetically) and injects the first class.
• B.Magento throws an exception because you cannot instantiate an interface
• C.If no $storeManager is provided, Magento's code generator creates a shell concrete class based on \Magento\Store\Model\StoreManagerInterface
• D.Magento looks to the di.xml files in the entire system for a preference node for \Magento\Store\Model\StoreManagerInterface. This class is constructed and injected

Comment: *

Name: *

Email: *

Verification: *

You are working on a project that contains a million SKUs. The merchant has requested the product view page to have a custom color schema and page layout depending on the product price range.
How do you implement this, keeping simplicity in mind?

• A.Create a custom block which will dynamically choose the appropriate template
• B.Enable the dynamic product page UI component and configure it to use a different layout per price range
• C.Specify custom layout update XML in the admin panel for every product
• D.Write a Data Patch which will set the appropriate layout update XML for every product record

Comment: *

Name: *

Email: *

Verification: *