Which command reveals how the shell will interpret a given command, including whether it's a built-in, alias, or function?

• A. which filename
• B. whereis filename
• C. type filename
• D. command -v filename

Answer: (C)

Understanding how the shell will interpret a command name is about discovering what kind of entity that name represents in the current shell session. The type command is the best tool for this because it tells you exactly how the shell would treat the name: whether it’s a builtin, an alias, a function, a keyword, or an external file found in the PATH. This helps you predict what will actually run when you type the name.

For example, if you have an alias like ll='ls -l', running type ll will show that ll is aliased to 'ls -l'. If you’ve defined a function named mycmd, type mycmd will reveal that it is a function and may print its body. If you try a builtin like cd, type will show that cd is a shell builtin. If it’s a regular external command, type will report something like ls is /bin/ls, indicating the actual executable path.

Other options don’t provide the same complete insight. Which only searches PATH and won’t reveal aliases or functions. Whereis is broader and not reliable for how the shell interprets a name. command -v can indicate availability and sometimes path, but it’s not as explicit about the exact interpretation as type.