The core dump configuration for your system is: A user is running a process in the global zone and the process crashes. The process information is: User1 2663 2618 0 17:46:42 pts/2 0:00…

Question

Exhibit

Options

• Acore.bash.2663.global
• Bcore.bash.2663.zeus
• C/var/core/core.bash.2663
• D/var/core/core.bash.2663.global

• A
  77% (20)
• B
  8% (2)
• C
  12% (3)
• D
  4% (1)

Explanation

Option A is correct because in Solaris coreadm, the per-process core file pattern uses the zone name (%z token = "global") - not the hostname - and it is written to the process's current working directory with no path prefix, yielding the format core.<name>.<pid>.<zone>.

Why the distractors are wrong:

• B substitutes the server hostname ("zeus") for the zone name; hostnames appear with the %h token, which is not part of this per-process pattern.
• C uses the /var/core/ directory, which is the global (system-wide) core file path, and it omits the zone suffix entirely.
• D mixes both mistakes by combining the global path prefix (/var/core/) with the correct zone suffix - it describes neither the per-process format nor the global format exactly.

Memory tip: Think "per-process = no path, zone not host." If you see /var/core/ in the answer, it's the global core pattern. If you see the hostname instead of the zone name, it's a distractor swapping %h for %z.

No community discussion yet for this question.