You are working on a module MyCompany_MyModule which adds a select attribute with a few options using the \Magento\Eav\Setup\EavSetup: :addAttribute() method in data in data install script.
There is no uninstall script. While debugging, you have uninstalled the module with the command:
bin magento module:uninstall MyCompany_MyModule
Then you reinstalled the module. What will be the effect on the attribute?

• A. The attribute is updated when attribute options differ
• B. The attribute is deleted and created again
• C. The attribute remains the same but the attribute options will be duplicated
• D. A duplicate attribute will be created with a different attribute code

Suppose in the product rest API in Magento, you added a new attribute. But this attribute can be accessed by API consumers only when they have access permission. How do you create the attributes following the above condition:

• A. New attributes must be created as custom_attribute to restrict the access using ACL
• B. We can't create access permission for REST API, it's only applicable for entity and repository.
• C. New attributes must be created by extending the product API interface, to restrict access using ACL.
• D. New attribute must be created as extension_attribute to restrict the access using ACL

You are working on a new feature to allow multiple vendors for various products. To display vendors you add a custom fieldset component and select with the name myCompanyVendors. It will be shown if the number of vendors is more than one.
To do this you implement a custom method on your component:

How do you cause the method to be called when the value of options change?
A)

B)

C)

D)

• A. Option D
• B. Option A
• C. Option C
• D. Option B

When your class will be instantiated all the dependencies injected in your class constructor will also get instantiated, and it will trigger a chain reaction of object creation, this can really slow down the process. What could be the solution of above problem?

• A. Use Proxy classes with help of di.xml
• B. Use factory classes instead of Model.
• C. Use Dependecy Injection with help of di.xml
• D. Use VitualType classes with help of di.xml

After enable the content security policy in a magento site, you see below warnings/errors in the browser console. "[Report Only] Refused to load the script 'https://cdn.jquery.com/jquery.js' because it violates the following Content Security Policy directive: "script-src assets.adobedtm.com".What could be the standard fix of this problem?

• A. Add etc/config.xml in a custom module and set report only to 1, to let the browser load all script urls without error.
• B. Disable the module Magento_Csp to let the browser load all script urls without error.
• C. Add etc/csp_whitelist.xml in a custom module and whitelist it under policy id="link-src"
• D. Add etc/csp_whitelist.xml in a custom module and whitelist it under policy id="script-src"