Adobe AD0-E704 Exam - 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

Kathryn

7 months ago

No way, text is not the right choice here.

upvoted 0 times

...

Annelle

7 months ago

Unsigned 3 byte integer? That’s surprising!

upvoted 0 times

...

Christiane

8 months ago

static might be a good option, right?

upvoted 0 times

...

Janna

8 months ago

I think varchar could work too, but int seems better.

upvoted 0 times

...

Helene

8 months ago

Definitely going with int for performance!

upvoted 0 times

...

Lisandra

8 months ago

I feel like 'text' is too heavy for this use case. It should be something more efficient like 'int' or 'static'.

upvoted 0 times

...

Tijuana

8 months ago

I practiced a similar question where performance was key, and I believe 'static' could be a good option for faster queries.

upvoted 0 times

...

Roselle

8 months ago

I'm not entirely sure, but I remember something about using 'varchar' for string data. This seems like a numeric ID though.

upvoted 0 times

...

Johnna

8 months ago

I think the best choice might be 'int' since it's an unsigned 3 byte integer, which should fit well.

upvoted 0 times

...

Kati

8 months ago

Ah, this is tricky. I'm not too familiar with the different Marketing Cloud features and capabilities. I'll need to review my notes and maybe ask the instructor for some guidance.

upvoted 0 times

...

Izetta

9 months ago

Hmm, this seems like a tricky one. I'll need to think carefully about the concept of "highest and best use" and how that relates to the asset providing maximum value to market participants.

upvoted 0 times

...

Lorenza

9 months ago

Hmm, I'm a bit unsure about this one. I know Netstat can show network connections, but I'm not sure if it shows the port states in real-time. Maybe TCPView would be a better option?

upvoted 0 times

...

Kris

9 months ago

Wait, I'm confused. How do I use the total asset turnover ratio to calculate the sales level? I'm not sure I fully understand the connection there.

upvoted 0 times

...

Darci

1 year 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

1 year ago

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

upvoted 0 times

...

Edna

1 year ago

Agreed, int is the most efficient choice for performance.

upvoted 0 times

...

William

1 year ago

A) int

upvoted 0 times

...

Danica

1 year 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

1 year ago

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

upvoted 0 times

...

Lenora

1 year ago

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

upvoted 0 times

...

Alayna

1 year ago

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

upvoted 0 times

...

Vonda

1 year 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

12 months ago

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

upvoted 0 times

...

Nell

12 months ago

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

upvoted 0 times

...

Delsie

12 months ago

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

upvoted 0 times

...

Alpha

12 months ago

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

upvoted 0 times

...

Veta

12 months ago

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

upvoted 0 times

...

Mertie

1 year ago

B) varchar

upvoted 0 times

...

Marg

1 year ago

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

upvoted 0 times

...

Matthew

1 year ago

A) int

upvoted 0 times

...

Coral

1 year 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

1 year 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