When using ExplicitName, what is the recommended type of ModuleAttribute?

• A. A single, fixed ModuleAttribute.
• B. A generic ModuleAttribute that is generic and has multiple instances.
• C. A hidden ModuleAttribute not exposed to tests.
• D. A read-only ModuleAttribute that cannot be renamed.

Answer: (B)

Explicit naming relies on attaching a separate, flexible attribute instance to each module so you can assign and reference distinct names. Using a generic ModuleAttribute that is generic and has multiple instances gives you the right level of flexibility: you can create and link as many named module attributes as you need, one per module, each carrying its own explicit name. This keeps the design extensible and allows every module to be uniquely identified by its assigned name.

If you used a single fixed ModuleAttribute, all modules would share one attribute, making it impossible to distinguish them by name. A hidden ModuleAttribute would be invisible to the test designer and users, defeating the purpose of explicit naming. A read-only ModuleAttribute would prevent renaming or assigning explicit names in the test, again blocking the intended workflow.