When should system status be preferred over group status?

Question

Options

• AWhen standardizing system-wide workflows
• BWhen setting permissions for a single department
• CWhen customizing reports for group-specific data
• DWhen applying a unique approval process for a team

• A
  70% (45)
• B
  9% (6)
• C
  16% (10)
• D
  5% (3)

Explanation

System status is the right choice when consistency across the entire system is the goal - standardizing system-wide workflows requires a uniform setting that applies to all users and groups, which is exactly what system status is designed for (Option A).

Option B is wrong because setting permissions for a single department is a group-level concern - scope is narrow, not system-wide. Option C is wrong because customizing reports for group-specific data inherently calls for group status, since the output varies by group. Option D is wrong because a unique approval process for a team signals differentiation, not standardization - that's a group status use case.

Memory tip: Use the phrase "System = Same for all, Group = Granular for few." Whenever the question hints at organization-wide uniformity or standardization, system status wins; whenever it mentions a specific team, department, or unique customization, think group status.

No community discussion yet for this question.