Magento allows you to specify custom values per store for product attributes created in the admin panel.
Which architectural pattern makes it possible?
A. Store Manager
B. Extension Attribute
C. Entity Attribute Value
D. Dependency Injection
|
Download Printable PDF. VALID exam to help you PASS. |
 |
Correct Answer: C
Correct Answer : C
Answer : C
Answer:- C. Entity Attribute Value
refer:
https://blog.magestore.com/entity-attribute-value-in-magento/
2.1. How Entity Attribute Value data storage work in Magento
The answer is C. Even in the provided reference the opening paragraph states:
Custom and Entity-Attribute-Value (EAV) attributes—Custom attributes are those added on behalf of a merchant. For example, a merchant might need to add attributes to describe products, such as shape or volume. A merchant can add these attributes in the Magento Admin panel. See the merchant documentation for information about managing custom attributes.
Extension Attribute CANNOT be created via the Admin panel like the question suggests
According to me Correct answer is B. As eav architecture just makes the complexity of storing data easier by storing data in different tables.
answer is B, Because Attribute already created in admin panel and pass only custom values store wise
Correct answer is B. According to documentation
https://devdocs.magento.com/guides/v2.4/extension-dev-guide/attributes.html: Explanation
So which do u conclude based on the explanation shared by you..I am unable to conclude between B or C
My answer is C
Correct is C
Correct is C
Extension Attribute can’t be created in admin