C#.NET — Attributes: identify the correct statement about custom attributes and runtime behavior.

Introduction / Context:
Attributes are classes that carry metadata and, in many scenarios, drive runtime or framework behavior (serialization, remoting, interop, security, binding, etc.). This question distinguishes true facts from common misconceptions.

Given Data / Assumptions:

• Custom attribute naming convention: “XAttribute” class can be used via [X] or [XAttribute].
• Attributes are reference types deriving from System.Attribute.
• Constructors define required positional parameters; zero-argument constructors are optional.

Concept / Approach:
Only classes (not structs) derive from System.Attribute to create custom attributes. There is no IAttribute interface to implement. The runtime and frameworks often read attributes to change behavior (e.g., [Serializable], [NonSerialized], [DllImport], [Obsolete] affects compilation).

Step-by-Step Solution:

Verification / Alternative check:
Declare a custom attribute deriving from System.Attribute and observe reflection and framework behaviors.

Why Other Options Are Wrong:
They contradict the attribute class model and naming conventions.

Common Pitfalls:
Assuming an interface-based attribute model or that parameterless constructors are mandated.

Final Answer:
The CLR can alter behavior based on the attributes applied to code.