AD0-E718: Adobe Commerce Architect Master

By Adobe · Question Mode

QuestionQ2

Content, CMS, and Storefront

An Architect on a headless Adobe Commerce project creates a new customer attribute named my_attribute. Based on the customer’s attribute value, a plugin modifies the results of GraphQL queries. The frontend application communicates with Adobe Commerce through Varnish by Fastly, which already caches the queries that will be modified. The Adobe Commerce Fastly extension is installed, and no other changes are made to the application.

Which steps should the Architect take to ensure that Varnish’s vcl_hash function also takes the newly created attribute into account?

Explanation

Adobe Commerce calculates X-Magento-Cache-Id from registered cache-ID factors, and Fastly/Varnish uses that value to distinguish cached GraphQL responses for logged-in customers. Implementing CacheIdFactorProviderInterface to supply my_attribute as the factor name and its current customer value as the factor value, then registering it in CacheIdCalculator’s idFactorProviders DI argument, makes the cache identifier vary by that attribute. Cache identities control cache invalidation tags, while customer-data sections supply client-side private content and do not vary the Varnish GraphQL cache key.

Learn more

Community Discussion

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