Cyber Monday 2024! 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 7 Question 32 Discussion

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

A merchant is using a unified website that supports native Adobe Commerce B2B and B2C with a single store view.

The merchant's objective is to display the B2B account features, such as negotiable quotes and credit limits, in the header of the site on every page for logged-in users who belong to a B2B company account.

Each B2B company possesses its unique shared catalog and customer group, while numerous customer groups for non-B2B customers undergo changes. The merchant insists that this association should not be linked to customer groups.

Which two solutions should the Architect recommend for consideration, taking into account public data and caching? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Option B is a valid solution because creating a new HTTP Context variable can allow for differentiating the public content cache for users who belong to a B2B company account.The HTTP Context variable can be used to modify the output of the header block accordingly, without affecting the performance or scalability of the site1

Option D is also a valid solution because creating a new custom condition for customer segments can enable targeting users who are part of a B2B company account. The customer segment can be used to modify the output of the header block accordingly, using layout updates or dynamic blocks.This solution can also leverage the existing customer segment functionality and avoid custom coding2

Option A is not a valid solution because switching the theme based on a virtual type can cause performance issues and increase the complexity of the site maintenance.Moreover, switching the theme can affect the entire site appearance, not just the header block3

Option C is not a valid solution because using the customer session data directly to modify the output of the header block can prevent the public content cache from working properly.The customer session data is private and cannot be cached, so this solution can negatively impact the performance and scalability of the site4

Option E is not a valid solution because checking if the current user is part of a B2B company within a block class can also prevent the public content cache from working properly.The block class logic is executed on every request, so this solution can negatively impact the performance and scalability of the site5


1: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html?lang=en#http-context2: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/marketing/customer-segments.html?lang=en3: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/design/themes.html?lang=en4: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html?lang=en#private-content5: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html?lang=en#public-content

Contribute your Thoughts:

Jennifer
11 days ago
D is an interesting approach, but I'm not sure I'd want to rely on customer segments for this. B and E are my picks.
upvoted 0 times
Alex
2 days ago
I agree, using a new HTTP Context variable for caching public content for B2B users sounds like a good solution.
upvoted 0 times
...
...
Alisha
14 days ago
I'm leaning towards option D as well, creating a custom condition for customer segments could provide more flexibility in modifying the output.
upvoted 0 times
...
Madonna
15 days ago
I agree with Celestine, option C seems like a straightforward solution to modify the output for B2B company users.
upvoted 0 times
...
Francis
19 days ago
I'm not a fan of modifying the theme just to change the output. That sounds like a maintenance nightmare. B and C get my vote.
upvoted 0 times
...
Tequila
21 days ago
B and C seem like the best options. Keeping the logic in the session and using a custom HTTP context makes the most sense for caching and performance.
upvoted 0 times
Earleen
9 days ago
I agree, having separate public content cached for B2B users would definitely improve performance.
upvoted 0 times
...
Ezekiel
10 days ago
B and C seem like the best options. Keeping the logic in the session and using a custom HTTP context makes the most sense for caching and performance.
upvoted 0 times
...
...
Celestine
25 days ago
I think option C is a good choice because it directly uses the data from the customer session.
upvoted 0 times
...

Save Cancel