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 16 Discussion

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

The development of an Adobe Commerce website is complete. The website is ready to be rolled out on the production environment.

An Architect designed the system to run in a distributed architecture made up of multiple backend webservers that process requests behind a Load Balancer.

After deploying the system and accessing the website for the first time, users cannot access the Customer Dashboard after logging in. The website keeps redirecting users to the sign-in page even though the users have successfully logged in The Architect determines that the session is not being

saved properly.

In the "app/etc/env.php", the session is configured as follows:

What should the Architect do to correct this issue?

Show Suggested Answer Hide Answer
Suggested Answer: C, E

The issue here is that the Approval Rules tab does not appear in the Company section in the Customer Account Menu when the Architect logs in using the Company Administrator account. This is because the Approval Rules feature requires two settings to be enabled: the Purchase Orders feature and the Purchase Order payment method. The solution is to set 'Enable Purchase Orders' in the B2B Admin to TRUE and make sure that the 'Purchase Order' payment method is active. This will allow the Architect to create and manage Approval Rules for orders.


Contribute your Thoughts:

Virgina
5 days ago
Haha, 'increase the session size' - that's a classic IT solution, just throw more resources at the problem! But it's not going to help in this case. Definitely go with Option A.
upvoted 0 times
...
Jose
7 days ago
Ah, I see. The session configuration in the env.php file suggests that the issue is related to session storage. Option A seems like the best approach here.
upvoted 0 times
...
Simona
10 days ago
I believe option A is the best solution as it can ensure proper session handling across multiple backend webservers.
upvoted 0 times
...
Raymon
11 days ago
I agree with Zana. Using a shared Redis instance can help with session management.
upvoted 0 times
...
Zana
13 days ago
I think the Architect should update the session host value to a shared Redis instance.
upvoted 0 times
...
Buck
15 days ago
I believe option A is the best solution. It will ensure that sessions are properly saved and synchronized between the backend webservers.
upvoted 0 times
...
Doyle
16 days ago
I agree with Beata. Using a shared Redis instance can help solve the session saving issue.
upvoted 0 times
...
Mee
21 days ago
Hmm, the session is not being saved properly. Looks like we need to update the session host value to a shared Redis instance to ensure session synchronization across the servers.
upvoted 0 times
...
Beata
26 days ago
I think the Architect should update the session host value to a shared Redis instance.
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