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-E706 Topic 9 Question 29 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 29
Topic #: 9
[All AD0-E706 Questions]

You are reviewing a third party extension for Magento Commerce Cloud compatibility Which pattern makes a module incompatible with Magento Commerce Cloud?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Rebecka at Apr 14, 2024, 03:29 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Doretha
3 months ago
I'm going with C. Configuration referencing generated Proxy classes in the module's etc/frontend/di.xml file seems like the way to go for compatibility.
upvoted 0 times
Kenneth
2 months ago
Definitely, following that pattern will ensure smooth integration with the platform.
upvoted 0 times
...
Lorrine
2 months ago
I agree, that's the best practice for compatibility with Magento Commerce Cloud.
upvoted 0 times
...
Reena
3 months ago
I think C is the correct choice. It's important to reference generated Proxy classes in the di.xml file.
upvoted 0 times
...
...
Izetta
3 months ago
Ha! Looks like the key is to avoid the object manager like the plague. Magento Commerce Cloud is all about that DI, baby!
upvoted 0 times
Thad
2 months ago
C) Configuration referencing generated Proxy classes In the modules erc/frontend/di.xml file
upvoted 0 times
...
Sabrina
2 months ago
B) Direct instantiation by the objectManager In non-constructor methods with the class also being referenced in the constructor signature
upvoted 0 times
...
Wai
2 months ago
A) Direct instantiation by the objectManager of non-generated classes in .phtml template files
upvoted 0 times
...
...
Hester
4 months ago
I'm not sure, but B seems like a reasonable answer. Direct instantiation by the objectManager in non-constructor methods with the class also being referenced in the constructor signature could be an issue.
upvoted 0 times
Argelia
3 months ago
A and D could also cause compatibility issues, but B seems to be the most likely scenario.
upvoted 0 times
...
Mozell
3 months ago
But what about A or D?
upvoted 0 times
...
Carin
3 months ago
I agree, direct instantiation in non-constructor methods could cause compatibility issues.
upvoted 0 times
...
Angelica
3 months ago
I think B is the correct answer.
upvoted 0 times
...
...
Eleonore
4 months ago
I think the correct answer is D. Direct instantiation of generated classes by the objectManager without the class being referenced in the constructor is a pattern that makes a module incompatible with Magento Commerce Cloud.
upvoted 0 times
Alyce
2 months ago
Yes, you are correct! Direct instantiation of generated classes by the objectManager without the class being referenced in the constructor is a pattern that makes a module incompatible with Magento Commerce Cloud.
upvoted 0 times
...
Nadine
2 months ago
D
upvoted 0 times
...
Desirae
2 months ago
No, that's not the correct answer. Try again.
upvoted 0 times
...
Iraida
3 months ago
A
upvoted 0 times
...
...
Karl
4 months ago
But doesn't direct instantiation by the objectManager of non-generated classes in .phtml template files make a module incompatible?
upvoted 0 times
...
Giuseppe
4 months ago
I disagree, I believe the correct answer is C.
upvoted 0 times
...
Karl
4 months ago
I think the answer is A.
upvoted 0 times
...

Save Cancel