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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe Exam AD0-E704 Topic 6 Question 14 Discussion

Actual exam question for Adobe's AD0-E704 exam
Question #: 14
Topic #: 6
[All AD0-E704 Questions]

You are integrating an external system from which products and categories will be synchronized with Magento.

To keep the category tree synchronized, an identifier attribute needs to be added to the catalog_category entity. The identifier value is generated by the external system as an unsigned 3 byte integer and is global in scope. Your code will run many concurrent queries to select categories based on this ID in order to synchronize changes.

Keeping performance in mind, what attribute backend type do you choose when creating the EAV attribute?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Christiane at Jan 05, 2023, 12:07 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Darci
1 months ago
Option A, definitely. Unless you're storing the entire Encyclopaedia Britannica in your category IDs, int is the way to go.
upvoted 0 times
Edna
4 days ago
Agreed, int is the most efficient choice for performance.
upvoted 0 times
...
William
10 days ago
A) int
upvoted 0 times
...
...
Danica
1 months ago
I'd have to go with A as well. Can't go wrong with a nice, compact integer when you need fast lookups.
upvoted 0 times
Joana
19 days ago
User 3: Yeah, I'd go with A) int as well for performance reasons.
upvoted 0 times
...
Lenora
24 days ago
User 2: Agreed, integers are definitely faster for lookups.
upvoted 0 times
...
Alayna
28 days ago
User 1: I think I would choose A) int for the attribute backend type.
upvoted 0 times
...
...
Vonda
1 months ago
Option C, static, could work too. But since the identifier is global, an int type makes more sense to me.
upvoted 0 times
Marg
9 days ago
I agree, using an int type for the identifier attribute seems like the best choice for performance.
upvoted 0 times
...
Matthew
28 days ago
A) int
upvoted 0 times
...
...
Coral
1 months ago
I agree, A is the way to go. The external system is already using a 3-byte integer, so keeping it that way will make the integration smoother and faster.
upvoted 0 times
...
Carmela
2 months ago
Hmm, I'd go for option A. An unsigned 3-byte integer should be more efficient than a larger data type like varchar or text, especially for the number of concurrent queries.
upvoted 0 times
Fanny
22 days ago
User 2: Yeah, using an int for the identifier attribute makes sense with all those concurrent queries.
upvoted 0 times
...
Craig
1 months ago
User 1: I agree, option A seems like the best choice for performance.
upvoted 0 times
...
...
Quiana
2 months ago
That's a good point, but wouldn't using A) int still be faster for querying large amounts of data?
upvoted 0 times
...
Yuki
2 months ago
I disagree, I believe B) varchar would be a better choice as it allows for more flexibility in case the ID format changes in the future.
upvoted 0 times
...
Quiana
2 months ago
I think the best option would be A) int because it is more efficient for querying by ID.
upvoted 0 times
...

Save Cancel