With simplicity in mind, which two steps should the Architect take to implement these requirements?

An Adobe Commerce store owner sets up a custom customer attribute "my.attribute".

An Architect needs to display additional content on the home page, which should display only to Customers with "my.attribute" of a certain value and be the same content for all of them. The website is running Full Page Cache.

With simplicity in mind, which two steps should the Architect take to implement these requirements? (Choose two.)
A . Add a new context value of "my_attribute" to MagentoFrameworkAppHttpContext
B . Create a Customer Segment and use ‘my.attribute’ in the conditions
C . Add a custom block and a pHTML template with the content to the cmsjndexjndex.xml layout
D . Add a dynamic block with the content to the Home Page
E . Use customer-data JS library to retrieve "my.attribute" value

View Answer

Answer: AD

Explanation:

To display additional content on the home page based on a custom customer attribute, the Architect needs to do the following steps:

Add a new context value of “my_attribute” to MagentoFrameworkAppHttpContext. This will allow the Full Page Cache to generate different versions of the page for customers with different values of “my.attribute”. The context value can be set using a plugin on the MagentoCustomerModelContext class.

Add a dynamic block with the content to the Home Page. A dynamic block is a type of content block that can be configured to display only to specific customer segments or conditions. The Architect can use the ‘my.attribute’ in the conditions of the dynamic block and assign it to the Home Page in the Content > Blocks section of the Admin Panel.

Reference: Private content | Magento 2 Developer Documentation Dynamic Blocks | Adobe Commerce 2.3 User Guide – Magento