AD0-E722: Adobe Commerce Architect Master

By Adobe · Question Mode

QuestionQ8

Design and implement optimal solutions for Adobe Commerce to meet business needs

A merchant uses a unified website that supports native Adobe Commerce B2B and B2C through one store view.

The merchant wants B2B account features, such as negotiable quotes and credit limits, displayed in the site header on every page for logged-in users who belong to a B2B company account.

Each B2B company has its own shared catalog and customer group, while many customer groups for non-B2B customers change. The merchant requires that this association not be tied to customer groups.

Which two solutions should the Architect recommend for consideration, accounting for public data and caching?

Choose two
Explanation

A custom HTTP context variable lets Adobe Commerce maintain distinct full-page-cache variants for B2B-company users and other users when the URL is the same. The header block can use company membership to render the applicable B2B account features. This preserves cacheability while preventing B2B-specific header output from being shared with non-B2B users. Adobe Commerce specifically recommends declaring a custom context variable when different public content must be shown for the same URL.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!