Drag and Drop Question A company uses Dynamics 365 Finance. You must implement three classes with the following requirements: - Variables in ClassA must be accessible from ClassA and its child…

Question

Exhibit

Answer Area

Explanation

X++ Variable Modifiers - Explanation

The Three Modifiers

Placement 1: ClassA → Protected

Requirement: Variables must be accessible from ClassA and its child classes, but not from unrelated classes.

This is precisely what protected does. ClassB inherits from ClassA, so protected variables on ClassA are visible inside ClassB automatically - no separate declaration needed for ClassB. Using public would fail because it would expose the variables to every class, violating the "not from other classes" constraint. Using private would fail because ClassB (a child) couldn't access them.

Placement 2: ClassC → Private

Requirement: Variables must only be accessible within ClassC itself.

This is precisely what private does - it locks access to the declaring class only. Since ClassC has no parent or child relationship, there's nothing to inherit to or from, making private the correct and only appropriate choice.

Why ClassB Has No Answer

ClassB is not listed as requiring its own variable modifier. It's a consumer of ClassA's protected variables, not a source of new access-controlled variables in this scenario.

Common Misconceptions

• Confusing protected with private: A common mistake is thinking "restricted = private," but protected is the right "restricted-but-inheritable" choice.
• Using public for ClassA: Public satisfies the "child class can access it" part but breaks the "not from other classes" requirement.
• Thinking ClassB needs an answer: ClassB inherits; it doesn't redeclare. The question is about where variables are defined, not where they're used.

No community discussion yet for this question.