Which of the following is a valid alternative method to locate PATH without using printenv?

• A. printenv PATH
• B. declare | grep PATH
• C. echo $PATH
• D. ls /proc/self/environ

Answer: (B)

Locating PATH can be done by inspecting the shell’s own variable declarations. In Bash, the declare builtin lists all declared variables along with their attributes. Piping that output to grep for PATH isolates the line that defines PATH, typically showing its value and offering a hint about whether it’s exported. For example, you might see a line like declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/bin:/bin" which reveals both the value and the export status. This method doesn’t call printenv, and it uses the shell’s own state to reveal how PATH is set. While echoing $PATH will display the directories in PATH, declare | grep PATH specifically demonstrates the variable’s declaration and export, which can be informative in contexts where you care about how the shell handles it. The other approaches either duplicate the value output in a simple way or delve into low-level environment representations, which aren’t as direct for understanding how PATH is defined in the shell.