Adobe AD0-E717 Exam - Topic 8 Question 54 Discussion

Actual exam question for Adobe's AD0-E717 exam

Question #: 54
Topic #: 8

A developer found a bug inside a private method of a third party module class. How can the developer override the method?

ACreate a custom class with corrected logic, and define the class as preference in the preferences.xml.

BCreate a custom class with the corrected logic, and define the class as a preference for original one in the di xml.

CCreate a plugin, implement correct logic in the after' method, and then define the plugin in the di.xml.

Show Suggested Answer

Suggested Answer: B

To override a private method in a third-party module class, the most effective approach is to use a preference. This involves creating a custom class with the corrected logic and then defining this class as a preference for the original one in the di.xml file. Plugins cannot be used to override private methods, final methods, final classes, or classes created without dependency injection. Therefore, the preference mechanism, which allows for the substitution of the entire class, becomes the viable method to override a private method and modify its behavior.

by Cordelia at Oct 28, 2025, 06:17 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Tabetha

2 months ago

Yeah, but A is simpler for quick fixes.

upvoted 0 times

...

Amber

2 months ago

Option B seems good too, but I’m unsure about the di xml part.

upvoted 0 times

...

Omer

2 months ago

I prefer option C. Plugins are powerful for this.

upvoted 0 times

...

Esteban

2 months ago

Not sure if any of these will actually fix the bug.

upvoted 0 times

...

Rosamond

2 months ago

Wait, can you really override third-party methods like that?

upvoted 0 times

...

Tricia

2 months ago

C sounds complicated, but it could work.

upvoted 0 times

...

Hester

3 months ago

I think B is better for clarity.

upvoted 0 times

...

Rossana

3 months ago

Option B, because who doesn't love a good ol' di.xml override? It's the developer's version of a magic trick!

upvoted 0 times

...

Clarinda

3 months ago

Option A seems like a hack. I'd rather not touch the preferences.xml if I can avoid it.

upvoted 0 times

...

Nobuko

3 months ago

I remember that creating a plugin is a common way to modify behavior, especially with the "after" method. That might be the best choice here.

upvoted 0 times

...

Vallie

3 months ago

I’m a bit confused about the difference between preferences.xml and di.xml. I thought both could be used for overriding, but I can't recall the specifics.

upvoted 0 times

...

Cheryl

3 months ago

I feel like we practiced a similar question where we had to override a method. I think the plugin option might be the right approach here.

upvoted 0 times

...

Tonja

4 months ago

I agree, Option B is the cleanest solution. Modifying the third-party code directly is a big no-no.

upvoted 0 times

...

Ricki

4 months ago

Option B is the way to go. Overriding a private method in a third-party module is the best approach.

upvoted 0 times

...

Avery

4 months ago

Option A is the way to go!

upvoted 0 times

...

Annamae

4 months ago

Option C sounds like a lot of work. Why not just create a custom class and override the method? Simple and effective.

upvoted 0 times

...

Tabetha

4 months ago

I think option A is the best choice. It’s straightforward.

upvoted 0 times

...

Glory

5 months ago

I think I remember something about using a custom class, but I'm not sure if it's in preferences.xml or di.xml.

upvoted 0 times

...

Hollis

5 months ago

Overriding a private method can be tricky, but I believe option B is the cleanest solution. Creating a custom class and defining it as a preference in the di.xml file should allow me to replace the original implementation without too much hassle.

upvoted 0 times

...

Melynda

5 months ago

I think the key here is to create a custom class with the corrected logic. From there, it seems like defining it as a preference in either the preferences.xml or the di.xml file would work. I'll need to double-check the specifics, but that's the general strategy I'm leaning towards.

upvoted 0 times

...

Brittni

5 months ago

Option C sounds interesting, but I'm not sure I fully understand how to implement the "after" method in a plugin. I'll need to do some research on that approach.

upvoted 0 times

...

Annice

5 months ago

Hmm, I'm a bit confused on the best way to approach this. Should I be looking at the preferences.xml or the di.xml file? I'm not sure which one would be the right place to define the custom class.

upvoted 0 times

...

Christoper

6 months ago

I think option B is the way to go here. Overriding the private method directly in the third party module seems like the most straightforward approach.

upvoted 0 times