For an AppSource app, enable the CodeCop, UICop, and AppSourceCop code analyzers in settings.json and avoid adding PerTenantExtensionCop
Short answer
ABE For an AppSource app use CodeCop, UICop, and AppSourceCop; do not add PerTenantExtensionCop because it conflicts with AppSourceCop.
Question
Key Takeaways
You enable analyzers in the al.codeAnalyzers setting in settings.json, not by writing a custom rule set. Enabling both PerTenantExtensionCop and AppSourceCop for the same project is invalid.
When building an app for Microsoft AppSource, the required code analyzers are CodeCop (general AL coding guidelines), UICop (web client UI rules), and AppSourceCop (marketplace submission rules). PerTenantExtensionCop is for per-tenant extensions and conflicts with AppSourceCop, so you enable only one of them.
Common mistake: Do not select a custom rule set as one of the three built-in analyzers, and do not mix PerTenantExtensionCop with AppSourceCop. Choose the analyzer that matches your deployment target.
Expert Analysis
Why the Answer Is Correct
Option A (CodeCop), Option B (UICop), and Option E (AppSourceCop) are the three analyzers that must be activated for an AppSource app, as confirmed by the 94 community votes and the official code-analysis documentation. These analyzers enforce the AL coding guidelines, UI best practices, and AppSource submission rules respectively. The scenario explicitly targets an AppSource-published app, so AppSourceCop is mandatory.
Why the Other Options Are Wrong
Option C (a custom rule set) is not one of the three built-in analyzers; analyzers are enabled via the al.codeAnalyzers setting, not a custom ruleset entry. Option D (PerTenantExtensionCop) enforces rules for per-tenant extensions and conflicts with AppSourceCop, so it must not be enabled alongside AppSourceCop for a marketplace app. The official guidance is to enable either PerTenantExtensionCop or AppSourceCop based on the deployment target, never both.
Community Comment Notes
VPin explains that PerTenantExtensionCop and AppSourceCop conflict and that for AppSource you do not need PerTenantExtensionCop, and 5e11cb9 confirms A, B, E as the answer.
Official Reference
This link opens the official vendor documentation in a new tab.
Community Votes
100% of anonymous learners picked answer ABE. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 4
-
VPin 👍 15PerTenantExtensionCop and AppSourceCop conflicts with each other. Code is for Appsource, so no need for PerTenantExtensionCop.
-
5e11cb9 👍 3Correct answer should be A, B, E
-
javieroto 👍 1PerTenantExtensionCop is an analyzer that enforces rules that must be respected by extensions meant to be installed for individual tenants.
-
Rebe 👍 1correct anser is ABE
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.