Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E722 Topic 4 Question 38 Discussion

Actual exam question for Adobe's AD0-E722 exam
Question #: 38
Topic #: 4
[All AD0-E722 Questions]

An Architect is investigating a merchant's Adobe Commerce production environment where all customer session data is randomly being lost. Customer session data has been configured to be persisted using Redis, as are all caches (except full page cache, which is handled via Varnish).

After an initial review, the Architect is able to replicate the loss of customer session data by flushing the Magento cache storage, either via the Adobe Commerce Admin Panel or running bin/magento cache: flush on the command line. Refreshing all the caches in the Adobe Commerce Admin Panel or running bin/magento cache: clean on the command line does not cause session data to be lost.

What should be the next step?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Lavina
1 days ago
I'd go with educating the merchant first. If they're randomly flushing the cache, that's likely the root cause. Changing the configuration should be a last resort.
upvoted 0 times
...
Sylvie
6 days ago
Hmm, the key seems to be ensuring the Redis configuration for caches and session data use different database numbers. Flushing the cache shouldn't be causing session data loss, so this is likely the issue.
upvoted 0 times
...
Peggie
18 days ago
I think option A makes sense. It's crucial to have the caches and session data stored separately to avoid any issues with data loss.
upvoted 0 times
...
Carin
20 days ago
I agree with Tina. It's important to ensure the Redis configuration is correct to prevent further loss of customer session data.
upvoted 0 times
...
Tina
27 days ago
I think the next step should be to check app/etc/env.php and make sure Redis configuration for caches and session data use different database numbers.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77