QuestionQ18

Store Operations and Admin

An Adobe Commerce system is set up in a multi-tier architecture that includes:

  • A cache server with Varnish installed
  • A backend web server with Adobe Commerce installed
  • A database server with MySQL installed

When an Adobe Commerce Architect attempts to clean the cache from Store Admin by selecting Flush Magento Cache in Cache Management, the Full Page Cache is not cleared.

Which two actions should the Architect take to ensure the Full Page Cache works correctly?

Choose two
  • A Set the backend destination host to the frontend server’s address in the Store AdminStores > Configuration > Advanced > System > Full Page Cache > Varnish Configuration > Backend Host
  • B Set the backend port destination to the frontend server’s Varnish port in the Store AdminStores > Configuration > Advanced > System > Full Page Cache > Varnish Configuration > Backend Port
  • C Set the cache type to “Varnish Caching” in the Store Admin.Stores > Configuration > Advanced > System > Full Page Cache > Caching Application
  • D Use “Flush Cache Storage” instead of “Flush Magento Cache”
  • E Set the cache destination host using magento CLIbin/magento_setup:config:set -–http-cache-hosts=<cache_server>:<varnish_port>
Explanation

Adobe Commerce must use Varnish Caching as the full-page caching application. It also purges remote Varnish instances during a cache clean only after their host and listen port have been configured with bin/magento setup:config:set --http-cache-hosts=<cache_server>:<varnish_port>. The Admin Varnish Backend Host and Backend Port settings instead identify the origin web server that Varnish accelerates.

Learn more

Community Discussion

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