Adobe Exam AD0-E722 Topic 4 Question 38 Discussion

Actual exam question for Adobe's AD0-E722 exam

Question #: 38
Topic #: 4

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?

ACheck app/etc/env.php and make sure that the Redis configuration for caches and session data use different database numbers.

BEducate the merchant to not flush cache storage and only refresh the caches in future.

CSet the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.

Show Suggested 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:

Submit Cancel

Charolette

1 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

15 days ago

Yeah, definitely worth checking the Redis config first. That could be the root cause of the session data loss.

upvoted 0 times

...

Larae

22 days ago

C) Set the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.

upvoted 0 times

...

Zoila

23 days 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

1 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

1 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

1 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

3 days ago

C) Set the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.

upvoted 0 times

...

Elbert

8 days ago

B) Educate the merchant to not flush cache storage and only refresh the caches in future.

upvoted 0 times

...

Shaquana

19 days 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

2 months 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

2 months 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

2 months 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

...