New Year Sale 2026! 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 AD0-E704 Exam - Topic 2 Question 16 Discussion

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

Suppose you are asked to disable/remove the customer review related functionalities. You can not disable the review module directly because the customer module depends on it. What is the possible way to remove all HTML outputs of the review module, from the frontend and backend? :

Show Suggested Answer Hide Answer
Suggested Answer: A

by Kirk at Mar 01, 2023, 03:36 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Felicidad
4 months ago
B is definitely not the right choice here, just saying!
upvoted 0 times
...
Jani
4 months ago
I agree with C, it gives more control over the output.
upvoted 0 times
...
Jennie
4 months ago
Wait, can we really override those classes? Sounds risky!
upvoted 0 times
...
Lacey
4 months ago
I think D could work too, but not sure it's the most efficient.
upvoted 0 times
...
Annice
4 months ago
Option C seems like the best approach to me.
upvoted 0 times
...
Natalya
5 months ago
I feel like overriding isOutputEnabled() might be the safer option here, but I need to double-check how that interacts with the review module.
upvoted 0 times
...
Dulce
5 months ago
I think using a plugin to override the toHtml() method could work, but I’m not entirely confident about the implementation details.
upvoted 0 times
...
Dorothy
5 months ago
This question feels similar to one we practiced on disabling modules, but I can't recall if we used module.xml or config.xml for that.
upvoted 0 times
...
Vanesa
5 months ago
I remember something about extending config.xml, but I'm not sure if that's the right approach for this specific scenario.
upvoted 0 times
...
Iesha
5 months ago
I think the number of business objectives directly supported by security initiatives is the best answer here. That really gets at how well the security strategy is aligned with the overall business goals.
upvoted 0 times
...
Elbert
5 months ago
I'm a little confused by the "omega distribution" option. I don't think I've learned about that one before. I'll have to do some quick research to see if that's a real thing or just a distractor.
upvoted 0 times
...
Alecia
5 months ago
Okay, let's see. The routing table is fixed length, while the flow table can get longer. And the matching methods are different - the routing table looks at the destination network segment, while the flow table looks at the MAC and IP address. I think I've got it.
upvoted 0 times
...
Howard
5 months ago
I'm leaning towards the option stating that child domains can view but not edit ancestor dashboards; that sounds familiar.
upvoted 0 times
...
Pura
9 months ago
Ah, the joys of working with dependencies. I can't wait to spend hours trying to untangle this web of modules just to hide some customer feedback.
upvoted 0 times
Jesusita
9 months ago
I feel your pain. Dependencies can be a real headache sometimes.
upvoted 0 times
...
Dominga
9 months ago
B) Turn-off Review module output globally by extending /vendor/magento/module-backend/etc/module.xml
upvoted 0 times
...
Rueben
9 months ago
C) Create plugin or Override the class \Magento\Framework\View\Element\AbstractBlock and toHtml() method, and implement the logic to return empty data in case of review module's block instance is present.
upvoted 0 times
...
...
Julene
9 months ago
Wait, we're supposed to remove the customer reviews? But how will I know which products to avoid buying now? The horror!
upvoted 0 times
...
Felicitas
9 months ago
I think option A is a bit overkill. Disabling the entire module's output globally could have widespread implications. A more targeted approach would be better.
upvoted 0 times
Ranee
8 months ago
D) Create plugin or Override the class \\Magento\\Backend\\Block\\Template and isOutputEnabled() method, and implement the logic to return false value in case of review module's block instance is present.
upvoted 0 times
...
Sharan
9 months ago
C) Create plugin or Override the class \\Magento\\Framework\\View\\Element\\AbstractBlock and toHtml() method, and implement the logic to return empty data in case of review module's block instance is present.
upvoted 0 times
...
...
Karl
9 months ago
Option D looks interesting, but I'm not sure if overriding the isOutputEnabled() method is the best approach. It might be better to focus on the specific review module's blocks.
upvoted 0 times
Gerardo
8 months ago
I think focusing on the specific review module's blocks might be a better approach.
upvoted 0 times
...
Alaine
8 months ago
D) Create plugin or Override the class \\Magento\\Backend\\Block\\Template and isOutputEnabled() method, and implement the logic to return false value in case of review module's block instance is present.
upvoted 0 times
...
Lai
9 months ago
C) Create plugin or Override the class \\Magento\\Framework\\View\\Element\\AbstractBlock and toHtml() method, and implement the logic to return empty data in case of review module's block instance is present.
upvoted 0 times
...
...
Ellsworth
10 months ago
I'm not sure about option B. Extending the module.xml file to disable the output globally might have unexpected side effects on other parts of the system.
upvoted 0 times
Maile
9 months ago
D) Create plugin or Override the class \\Magento\\Backend\\Block\\Template and isOutputEnabled() method, and implement the logic to return false value in case of review module's block instance is present.
upvoted 0 times
...
Elvera
9 months ago
C) Create plugin or Override the class \\Magento\\Framework\\View\\Element\\AbstractBlock and toHtml() method, and implement the logic to return empty data in case of review module's block instance is present.
upvoted 0 times
...
...
Adela
10 months ago
Option C seems like the most direct approach. Overriding the toHtml() method gives us the control to remove the output without affecting the rest of the application.
upvoted 0 times
Venita
9 months ago
That sounds like a good solution. It allows us to specifically target the review module's output.
upvoted 0 times
...
Cassie
9 months ago
C) Create plugin or Override the class \Magento\Framework\View\Element\AbstractBlock and toHtml() method, and implement the logic to return empty data in case of review module's block instance is present.
upvoted 0 times
...
...
Ira
10 months ago
That makes sense. It's important to handle the dependency issue properly to ensure the customer module still functions correctly after disabling the review functionalities.
upvoted 0 times
...
Larue
11 months ago
I agree with Malcom. By implementing the logic to return empty data in case of review module's block instance is present, we can remove all HTML outputs of the review module.
upvoted 0 times
...
Malcom
11 months ago
I think the possible way is to create a plugin or override the class \Magento\Framework\View\Element\AbstractBlock and toHtml() method.
upvoted 0 times
...

Save Cancel