How does Yeoman determine which generator to run for a given namespace?

• A. It prompts the user to choose a generator
• B. It loads a hard-coded mapping
• C. It resolves the namespace to a generator package (often generator-<name>) and runs the generator registered under that namespace
• D. It uses the current working directory to locate a generator

Answer: (C)

The thing being tested is how Yeoman maps a user-provided namespace to the actual generator that will run. Yeoman keeps a registry of available generators and, when you invoke a namespace, it resolves that identifier to a Node module named generator-. It then loads that package, which registers a Generator class with Yeoman under that namespace, and Yeoman runs that generator.

This is why generators are published as packages like generator-—installing the package makes the generator available, and requiring that module lets Yeoman hook it into its execution flow. If the package isn’t found, Yeoman can’t proceed, because there’s no generator registered under that namespace.

So, the mechanism is dynamic loading of the generator package based on the namespace, rather than a fixed list or a directory-based discovery. Other options don’t fit because Yeoman doesn’t rely on prompting you to choose a generator, nor does it use a hard-coded mapping; and while local generators can exist, the standard behavior is still to resolve the namespace to a generator package via module loading.