Overview
Declared default and page-cache frontend backends use supported Redis configuration; an explicit Varnish page-cache setting may replace an absent page-cache backend declaration. No assessed declared backend is file-based. This checks deployed configuration declarations, not live cache service health.
Why it Matters
A multi-node deployment needs a cache design appropriate to its topology and performance needs. Unintended backend choices can make nodes behave inconsistently or overload application workers.
Redis and Varnish are distinct services with different roles. Their names in configuration do not establish availability, security or cache correctness.
Verification Steps
Manual Verification
- Inspect the deployed default and page-cache backend declarations without printing credentials.
- Check supported Redis configuration, or explicit Varnish page-cache selection where that branch applies.
- Assess service health and cache behavior independently.
Command / Review Sample
php bin/magento config:show system/full_page_cache/caching_application
# Inspect cache.frontend backend names in env.php; redact connection secrets.
Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.
Remediation / Fix Guidance
- Review the exact declared backend/key in app/etc/env.php against the intended deployment baseline. If Redis is used, verify authentication and network/ACL access separately before changing the backend.
- Test cache/session correctness and effective access with the deployed worker configuration. A declaration alone does not prove runtime enforcement.
- Rerun MB-0038 against the same release, profile and relevant file/key/package scope; compare the new evidence and inspect any independent collection gaps.
Examples
Illustrative examples only. Interpret them within the current revision criterion above; missing collection evidence is unresolved, never PASS.
Fail Example
A collected assessed cache frontend declares a file backend.
Pass Example
Assessed frontend declarations use supported Redis settings; an explicit Varnish selection accounts for its page-cache branch.
Scope and Evidence Limits
Rule revision: 5. Target modes: LOCAL.
Declared default and page-cache frontend backends use supported Redis configuration; an explicit Varnish page-cache setting may replace an absent page-cache backend declaration. No assessed declared backend is file-based. This checks deployed configuration declarations, not live cache service health.
This check covers only the collected observation. Missing collection scope, external controls and runtime behavior require separate evidence.
Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.