Adobe AD0-E722 Exam - Topic 4 Question 34 Discussion

Actual exam question for Adobe's AD0-E722 exam

Question #: 34
Topic #: 4

An Architect is configuring the preload.keys for Redis on an Adobe Commerce on-premise instance.

The Architect discovers that the following cache keys are loaded on each frontend request: EAV_ENTITY_TYPES, GLOBAL_PLUGIN_LIST, DB_IS_UP_TO_DATE, SYSTEM_DEFAULT.

* The id_prefix of the frontend => page_cache is set to 063_.

* The id_pref ix of frontend => default is set to 762_.

* The Architect has enabled and configured Redis L2 caching.

How should the preload.keys be configured?

AOption A

BOption B

COption C

DOption D

Show Suggested Answer

Suggested Answer: C

Option C is correct because the developer did not check for an active content staging campaign and emulate the campaign state when retrieving product data. Content staging campaigns can modify the product data such as price, name, description, and so on, based on a schedule.To get the correct product data for a specific date and time, the developer needs to use the MagentoStagingModelVersionManager class to set the current version ID and emulate the campaign state1. Otherwise, the product data will be retrieved from the default store view without applying the campaign changes.

Option A is incorrect because retrieving product data directly from the database using the entity_id column is not necessarily wrong. It may not be the best practice, but it does not cause the feed output to be incorrect for products in the content staging campaign.The content staging campaigns are stored in separate tables with a version ID that links to the main product table2. The developer can still join these tables and query the product data based on the version ID and date.

Option B is incorrect because there is no such method as getContentStagingValue in Magento 2. The developer cannot use this method to retrieve the active campaign value of the product data. The correct way to get the product data for a specific campaign is to use the MagentoStagingModelVersionManager class as mentioned above.

1: Content Staging | Adobe Commerce Developer Guide

2: Content Staging | Adobe Commerce Developer Guide

by Jess at Jan 12, 2025, 02:45 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Rex

3 months ago

Definitely agree with B, it aligns with best practices!

upvoted 0 times

...

Annelle

3 months ago

Wait, are we really loading all those keys on every request?

upvoted 0 times

...

Kerrie

3 months ago

Not sure why GLOBAL_PLUGIN_LIST is included, seems unnecessary.

upvoted 0 times

...

Whitney

4 months ago

I think Option B is the best choice here!

upvoted 0 times

...

Alecia

4 months ago

Looks like EAV_ENTITY_TYPES is a must-have for preload.keys.

upvoted 0 times

...

Janna

4 months ago

I’m a bit confused about the id_prefixes. Do they affect how we set the preload.keys, or is it just about the cache keys themselves?

upvoted 0 times

...

Maurine

4 months ago

I feel like option C might be the right choice, but I can't recall the exact reasoning behind it.

upvoted 0 times

...

Barabara

4 months ago

I think we practiced a similar question where we had to configure cache keys for Magento. I wonder if the same logic applies here.

upvoted 0 times

...

Celeste

5 months ago

I remember that preload.keys should include the cache keys that are frequently accessed, but I'm not sure if all of them should be included.

upvoted 0 times

...

Larue

5 months ago

I'm feeling pretty confident about this one. The information provided gives me a clear path to determining the correct preload.keys setup.

upvoted 0 times

...

Alaine

5 months ago

This seems straightforward enough. I just need to analyze the cache key details and select the preload.keys configuration that best matches.

upvoted 0 times

...

Eileen

5 months ago

Okay, I think I've got a handle on this. The key is to match the preload.keys to the cache keys that are being loaded on each frontend request.

upvoted 0 times

...

Youlanda

5 months ago

Hmm, I'm a bit confused by all the different cache key prefixes. I'll need to make sure I understand how they relate to the preload.keys configuration.

upvoted 0 times

...

Shenika

5 months ago

This looks like a tricky Redis configuration question. I'll need to carefully review the details about the cache keys and prefixes to determine the best preload.keys setup.

upvoted 0 times

...

Layla

9 months ago

Redis caching, huh? I feel like I'm playing a game of 'Guess the Redis Key' here. Better not leave this one to chance!

upvoted 0 times

...

Dyan

9 months ago

This question really tests your understanding of Redis caching in Adobe Commerce. I better double-check my notes before I make a decision!

upvoted 0 times

...

Lachelle

9 months ago

Hmm, let me think about this... The cache keys mentioned suggest we need to preload some essential data, but the id_prefix settings also come into play. I'll have to carefully consider all the details.

upvoted 0 times

An

8 months ago

Laurel: Agreed, let's go with Option C then.

upvoted 0 times

...

Florinda

8 months ago

User 3: Option C looks like it includes the necessary preload.keys configuration for Redis L2 caching.

upvoted 0 times

...

Laurel

8 months ago

User 2: Yes, that's important. We also need to consider the id_prefix settings for frontend page_cache and default.

upvoted 0 times

...

Pura

9 months ago

User 1: I think we should configure the preload.keys based on the cache keys loaded on each frontend request.

upvoted 0 times

...

Lina

9 months ago

Oh, this is a tricky one! The preload.keys configuration is crucial for Redis caching on Adobe Commerce, but the correct answer isn't obvious at first glance.

upvoted 0 times