Adobe Exam AD0-E704 Topic 6 Question 14 Discussion

Actual exam question for Adobe's AD0-E704 exam

Question #: 14
Topic #: 6

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?

Aint

Bvarchar

Cstatic

Dtext

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

3 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

Gerry

2 months ago

Definitely, int is the way to go for storing numeric identifiers.

upvoted 0 times

...

Edna

2 months ago

Agreed, int is the most efficient choice for performance.

upvoted 0 times

...

William

2 months ago

A) int

upvoted 0 times

...

Danica

3 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

3 months ago

User 3: Yeah, I'd go with A) int as well for performance reasons.

upvoted 0 times

...

Lenora

3 months ago

User 2: Agreed, integers are definitely faster for lookups.

upvoted 0 times

...

Alayna

3 months ago

User 1: I think I would choose A) int for the attribute backend type.

upvoted 0 times

...

Vonda

3 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

Stefania

1 months ago

True, we need a data type that can handle the global scope of the identifier.

upvoted 0 times

...

Nell

1 months ago

Option B, varchar, might not be efficient for storing a 3 byte integer.

upvoted 0 times

...

Delsie

1 months ago

I agree, using an integer type for the identifier attribute makes sense.

upvoted 0 times

...

Alpha

1 months ago

I think option A, int, would be the best choice for performance.

upvoted 0 times

...

Veta

1 months ago

I think varchar could work too, but int might be more efficient for this specific case.

upvoted 0 times

...

Mertie

2 months ago

B) varchar

upvoted 0 times

...

Marg

2 months ago

I agree, using an int type for the identifier attribute seems like the best choice for performance.

upvoted 0 times

...

Matthew

3 months ago

A) int

upvoted 0 times

...

Coral

3 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

4 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