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-E722 Topic 4 Question 12 Discussion

Actual exam question for Adobe's AD0-E722 exam
Question #: 12
Topic #: 4
[All AD0-E722 Questions]

An Architect agrees to improve company coding standards and discourage using Helper classes in the code by introducing a new check with PHPCS.

The Architect creates the following:

* A new composer package under the AwesomeAgency\CodingStandard\ namespace

* The ruleset. xml file extending the Magento 2 Coding Standard

What should the Architect do to implement the new code rule?

A)

B)

C)

Show Suggested Answer Hide Answer
Suggested Answer: C

Option C is correct because adjusting the ruleset.xml file with the new rule is the simplest and most effective way to implement the new code rule. The ruleset.xml file defines the coding standards that are applied by PHP_CodeSniffer. By extending the Magento 2 Coding Standard and adding a new rule, the Architect can customize the code analysis and enforce the company coding standards.The new rule can use the Magento2.Namespaces.ForbiddenNamespaces sniff to check for any usage of Helper classes in the code and report them as errors or warnings1.

Option A is incorrect because creating a new composer package under the AwesomeAgencyCodingStandard namespace is not enough to implement the new code rule. The composer package is just a way to distribute and install the coding standard, but it does not define the rules themselves.The Architect still needs to create a ruleset.xml file and register it with PHP_CodeSniffer2.

Option B is incorrect because creating a new class AwesomeAgencyCodingStandardRulesetForbiddenNamespaces and specifying the rule inside the process method is unnecessary and complicated. The Architect does not need to create a new class or a new sniff for this rule, as there is already an existing sniff in the Magento 2 Coding Standard that can be used for this purpose.The Magento2.Namespaces.ForbiddenNamespaces sniff can be configured with an include-pattern element to specify which namespaces are forbidden1.


1: Magento 2 Coding Standards | Adobe Commerce Developer Guide

2: How to create a custom coding standard | PHP_CodeSniffer Documentation

by Karl at Mar 20, 2024, 11:27 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Louvenia
8 months ago
That's an interesting point, I can see how Option C could be a good choice as well.
upvoted 0 times
...
Alita
8 months ago
Option C might provide more flexibility in customizing the new code rule.
upvoted 0 times
...
Queenie
8 months ago
What makes you think Option C is better than Option A?
upvoted 0 times
...
Alita
8 months ago
I disagree, I believe Option C would be the best choice.
upvoted 0 times
...
Louvenia
8 months ago
Option A seems like the most straightforward solution for implementing the new code rule.
upvoted 0 times
...
Queenie
8 months ago
Why do you think Option A is the best choice?
upvoted 0 times
...
Louvenia
9 months ago
I think the Architect should choose Option A.
upvoted 0 times
...
Mee
9 months ago
Finally, the Architect should choose one of the options provided (A, B, or C) to complete the implementation.
upvoted 0 times
...
Walker
9 months ago
Yes, that file will define the standards that should be followed in the code.
upvoted 0 times
...
Marquetta
10 months ago
After that, the Architect should create the ruleset.xml file extending the Magento 2 Coding Standard.
upvoted 0 times
...
Cristal
10 months ago
I agree, that would be the first step in implementing the new code rule.
upvoted 0 times
...
Mozelle
10 months ago
I think the Architect should start by creating a new composer package.
upvoted 0 times
...

Save Cancel