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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E722 Exam - 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
Suggested Answer: A

The group property determines which section of the customer account the attribute belongs to. By setting the group property to 1, the reward_card_number attribute will be assigned to the default group, which is the Account Information section.This will make the attribute available in the My account/My rewards page template.Reference: https://experienceleague.adobe.com/docs/commerce-admin/customers/customer-accounts/attributes/attribute-properties.html?lang=en#group1


by Lynsey at Mar 20, 2025, 05:36 PM

Limited Time Offer

25%

Off

Get Premium AD0-E722 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dorian
3 months ago
Option C seems like a solid fix, worth a try!
upvoted 0 times
...
Julieta
4 months ago
I think educating the merchant is a good idea, but it won't fix the root problem.
upvoted 0 times
...
Jettie
4 months ago
Sounds like a Redis config issue, definitely check env.php.
upvoted 0 times
...
Leandro
4 months ago
I feel like option A makes the most sense since it directly addresses the configuration issue that could lead to session loss.
upvoted 0 times
...
Ernest
4 months ago
I disagree, flushing cache is sometimes necessary for updates.
upvoted 0 times
...
Delpha
4 months ago
Wait, flushing the cache loses session data? That's surprising!
upvoted 0 times
...
Kenny
5 months ago
I practiced a similar question where changing session settings in the admin panel helped, but I can't recall if that was the best solution here.
upvoted 0 times
...
Soledad
5 months ago
I'm not entirely sure, but I think educating the merchant about cache flushing might not be enough if the underlying configuration is wrong.
upvoted 0 times
...
Florencia
5 months ago
I remember reading that using the same Redis database for both cache and session data can cause issues, so checking the env.php file sounds like a good first step.
upvoted 0 times
...
Elouise
5 months ago
Setting the 'Store Session Data Separately' option could be worth a try, but I'm not sure if that's the best approach here. I'd want to verify the Redis configuration first before going that route.
upvoted 0 times
...
Jules
6 months ago
Educating the merchant not to flush the cache storage seems like a good temporary fix, but it doesn't really address the root cause. I'd want to dig deeper and find a more permanent solution.
upvoted 0 times
...
Anastacia
6 months ago
Ah, I think I've got it. The key is to check the Redis configuration and make sure the caches and session data are using different database numbers. That should help isolate the issue.
upvoted 0 times
...
Glendora
6 months ago
Hmm, this seems like a tricky one. I'll need to carefully review the details and think through the potential causes and solutions.SarahSmith: Okay, let's see. Flushing the cache causes the session data to be lost, but refreshing the caches doesn't. That's an interesting clue. I wonder if the Redis configuration could be the issue.MichaelJohnson: Ah, I think I've got it. The key is to check the Redis configuration and make sure the caches and session data are using different database numbers. That should help isolate the issue.EmilyRichards: Educating the merchant not to flush the cache storage seems like a good temporary fix, but it doesn't really address the root cause. I'd want to dig deeper and find a more permanent solution.JamesWilson: Setting the 'Store Session Data Separately' option could be worth a try, but I'm not sure if that's the best approach here. I'd want to verify the Redis configuration first before going that route.
upvoted 0 times
...
Maryanne
6 months ago
Okay, let's see. Flushing the cache causes the session data to be lost, but refreshing the caches doesn't. That's an interesting clue. I wonder if the Redis configuration could be the issue.
upvoted 0 times
...
Shawn
6 months ago
Hmm, this seems like a tricky one. I'll need to carefully review the details and think through the potential causes and solutions.
upvoted 0 times
...
Charolette
11 months ago
Well, I guess the merchant just really likes a good ol' cache flush! Seriously though, this sounds like a tricky one. I'd definitely check the Redis config first before trying anything else.
upvoted 0 times
Dortha
11 months ago
Yeah, definitely worth checking the Redis config first. That could be the root cause of the session data loss.
upvoted 0 times
...
Larae
11 months ago
C) Set the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.
upvoted 0 times
...
Zoila
11 months ago
A) Check app/etc/env.php and make sure that the Redis configuration for caches and session data use different database numbers.
upvoted 0 times
...
...
Taryn
11 months ago
Setting the 'Store Session Data Separately' option might be a good idea, but it feels like a band-aid. We should really get to the bottom of why the session data is being lost when the cache is flushed.
upvoted 0 times
...
Lavina
12 months 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
12 months 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
Anthony
10 months ago
C) Set the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.
upvoted 0 times
...
Elbert
11 months ago
B) Educate the merchant to not flush cache storage and only refresh the caches in future.
upvoted 0 times
...
Shaquana
11 months ago
A) Check app/etc/env.php and make sure that the Redis configuration for caches and session data use different database numbers.
upvoted 0 times
...
...
Peggie
1 year 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
1 year 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
1 year 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