You are trying to determine why a product is not appearing in a category. What table does Magento on the frontend to locate the relationship between a category and its products?

• A.catalog_category_product
• B.catalog_category_product_relationship
• C.catalog_category_product_index
• D.catalog_product_parent

Comment: *

Name: *

Email: *

Verification: *

During a code review of a module MyCompany_PaymentCurrencies you see a configuration field declared in the file etc/adminhtml/system.xml:

What is the consequence of the attribute showInStore being set to 0?

• A.The input field will be disabled if a store view scope is selected in the system configuration
• B.The field value will not be accessible on the store front by calling ScopeConfigInterface::getValue() with a $scopeType argument of 'store'.
• C.The input field will only be visible if a website's default store scope is selected in the system configuration
• D.The input field will not be visible if a store view scope is selected in the system configuration

Comment: *

Name: *

Email: *

Verification: *

What is the connection between product attribute sets and categories?

• A.Categories have no connection to product attribute sets, and any product can be assigned to any category
• B.Categories can be connected to multiple product attribute sets, and only products from one of those sets are allowed in the category
• C.Each category is linked to a single product attribute set, and only products from that attribute set are allowed in the category
• D.Each category is linked to a single product attribute set, and only products from that category's set or any of its parent categories'

Comment: *

Name: *

Email: *

Verification: *

You are making some major adjustments to a core Magento class (ClassA). These adjustments are only necessary when utilized from a specific Magento class (ClassB). You have created MyClass that contains the needed customizations.
Keeping upgradeability in mind, how do you configure di.xml to make the substitution happen?

• A.Create a rewrite node that injects MyClass into ClassB.
• B.Ensure that MyClass extends ModuleA and set the <argument/>, for ModuleB to point to your new class in di.xml.
• C.Create a virtual type that extends ModuleB, specifying an <argument/> for MyClass.
• D.Set a <preference/> for ModuleA to be replaced by MyClass

Comment: *

Name: *

Email: *

Verification: *

In a custom module you implement the interface \Magento\Framework\App\Config\DataInterface.

What version constraint for magento/framework do you add to your module's composer.json file?

• A.stable
• B.major
• C.patch
• D.minor

Comment: *

Name: *

Email: *

Verification: *