You and an associate named Frank administer a Solaris server. Frank will be responsible for monitoring system resource usage, so you set up a project entry for his account. Consider the following…

Question

Exhibit

Options

• Adefault
• Bclockfix
• Cuser.frank
• Dgroup.staff

• A
  88% (22)
• B
  4% (1)
• D
  8% (2)

Explanation

Option A is correct because Solaris determines a user's default project through a specific lookup order: first user.<username>, then group.<primary-group>, then the system default project. Since the command output shows no user.frank or group.staff project entries that Frank qualifies for, he falls back to the built-in default project.

Option C (user.frank) is wrong because, while it would be Frank's default if that entry existed in /etc/project, the output indicates no such entry is present. Option D (group.staff) is wrong for the same reason - it would only apply if user.frank didn't exist but group.staff did, and the output shows neither applies here. Option B (clockfix) is a distractor representing a custom project that may appear in the output but is not Frank's default since it's not selected through the lookup process.

Memory tip: Think of the lookup order as "personal → group → default" - Solaris always tries the most specific match first (user-level), then broader (group-level), then gives up and uses default. If you don't see a user.frank or group.staff entry, the answer is always default.

No community discussion yet for this question.