Adobe AD0-E722 Exam - Topic 4 Question 16 Discussion

Actual exam question for Adobe's AD0-E722 exam

Question #: 16
Topic #: 4

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?

AUpdate the session host value to a shared Redis instance

Bincrease the session size with the command config:set system/security/max_session_size_admin

CUtilize the Remote Storage module to synchronize sessions between the servers

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

by Nikita at May 13, 2024, 11:02 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Julian

3 months ago

Increasing session size won't solve the redirect problem.

upvoted 0 times

...

Val

3 months ago

Wait, is Redis really necessary for this?

upvoted 0 times

...

Lenna

3 months ago

Not sure about that, C could work too.

upvoted 0 times

...

Nickolas

4 months ago

I think option A is the best fix!

upvoted 0 times

...

Ryan

4 months ago

Sounds like a session storage issue for sure.

upvoted 0 times

...

Willodean

4 months ago

I vaguely recall that using a shared Redis instance can help with session persistence, but I’m not completely confident about that.

upvoted 0 times

...

Mariko

4 months ago

I feel like increasing the session size might not solve the redirect issue. It seems more related to how sessions are stored.

upvoted 0 times

...

Vivienne

4 months ago

I think I saw a similar question about session storage in our practice tests. Could it be that we need to synchronize sessions across servers?

upvoted 0 times

...

Nancey

5 months ago

I remember something about session handling in distributed systems, but I'm not sure if Redis is the right choice here.

upvoted 0 times

...

Katy

5 months ago

Ah, I see. The session is currently set to file-based storage, which won't work in a distributed setup. Updating to a shared Redis instance sounds like the best approach to ensure the session is accessible across all the backend servers.

upvoted 0 times

...

Cyril

5 months ago

I'm a bit confused here. The question mentions a distributed architecture, but the session configuration in the image doesn't seem to indicate any kind of shared storage. Maybe the Remote Storage module is the way to go to synchronize sessions across the servers.

upvoted 0 times

...

Reena

5 months ago

Okay, let's see. The question says the session is not being saved properly, so I'm guessing the session configuration is the issue. Updating the session host to a shared Redis instance seems like the most straightforward solution.

upvoted 0 times

...

Odelia

5 months ago

Hmm, this looks like a tricky one. I think the key is to figure out how the session is being stored and make sure it's accessible across the distributed servers.

upvoted 0 times

...

Sherrell

5 months ago

Hmm, increasing the session size doesn't seem like it would fix the issue of the session not being saved properly. I think the Redis or Remote Storage options are more likely to resolve the problem here.

upvoted 0 times

...

Goldie

5 months ago

This question seems straightforward. I think the key is to focus on the network requirements for the client and storage networks.

upvoted 0 times

...

Carry

5 months ago

I'm a little confused by this question. The "sphere of experience" doesn't seem like a super common term, so I'm not sure exactly what it's referring to. I'll have to read through the options carefully and see if I can figure out the best definition.

upvoted 0 times

...

Melynda

5 months ago

Hmm, I'm a bit unsure about this one. I think I'd lean towards meeting with the team lead to see if we can get things back on track, but I'm not totally confident that's the best move.

upvoted 0 times

...

Wilson

10 months ago

I bet the Architect is scratching their head, wondering how they missed the fact that a distributed architecture requires a shared session storage solution. Option A is the clear winner here.

upvoted 0 times

Lelia

9 months ago

User 3: That should solve the issue with the session not being saved properly.

upvoted 0 times

...

Freeman

9 months ago

User 3: That should solve the issue of users being redirected to the sign-in page.

upvoted 0 times

...

Shelia

9 months ago

User 2: Yeah, they should update the session host value to a shared Redis instance.

upvoted 0 times

...

Brynn

9 months ago

User 2: Yeah, they should update the session host value to a shared Redis instance.

upvoted 0 times

...

Michel

9 months ago

User 1: Looks like the Architect forgot to set up a shared session storage solution.

upvoted 0 times

...

Chandra

10 months ago

User 1: Looks like the Architect forgot to set up a shared session storage solution.

upvoted 0 times

...

Andrew

10 months ago

You know, if this was a real-world scenario, I bet the Architect would be tempted to just turn it off and on again. But in this case, Option A is the way to go.

upvoted 0 times

...

Daniela

10 months ago

Wait, a 'Remote Storage module'? Sounds like someone's trying to overcomplicate things. The straightforward solution is to use a shared Redis instance, as mentioned in Option A.

upvoted 0 times

...

Virgina

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

Lazaro

9 months ago

Selma: Alright, let's update the session host value to a shared Redis instance then.

upvoted 0 times

...

Kiley

9 months ago

User 3: Agreed, increasing the session size won't fix the issue. Let's go with Option A.

upvoted 0 times

...

Selma

9 months ago

User 2: Yeah, that sounds like the right solution. Option A is the way to go.

upvoted 0 times

...

Cory

10 months ago

User 1: I think we should update the session host value to a shared Redis instance.

upvoted 0 times

...

Jose

10 months 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 months ago

I believe option A is the best solution as it can ensure proper session handling across multiple backend webservers.

upvoted 0 times

...

Raymon

10 months ago

I agree with Zana. Using a shared Redis instance can help with session management.

upvoted 0 times

...

Zana

10 months ago

I think the Architect should update the session host value to a shared Redis instance.

upvoted 0 times

...

Buck

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

11 months ago

I agree with Beata. Using a shared Redis instance can help solve the session saving issue.

upvoted 0 times

...

Mee

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