A company with various departments wants to use tagging to improve search capability. Each department is restricted to use its own tags. How should an Architect organize the tags?

Question

Options

• ACreate a department sub-tag in each tag
• BUse department ID as a prefix of each tag
• CCreate a namespace for each department
• DCreate tags in "departmentName:tagName" format

• A
  23% (8)
• B
  11% (4)
• C
  60% (21)
• D
  6% (2)

Explanation

Creating a namespace for each department (C) is the architecturally correct approach because namespaces provide logical isolation - each department manages its own tag vocabulary without risk of naming conflicts, and access control can be enforced at the namespace boundary. This is a standard pattern in systems like AWS Resource Groups, Kubernetes, and tag management platforms.

Why the distractors fail:

• A - "Sub-tags" are not a standard tagging construct; the concept is informal and doesn't enforce department boundaries or prevent cross-department tag usage.
• B - A department ID prefix is just a naming convention, not a structural boundary; it relies on human discipline rather than enforced isolation, and breaks down as teams grow.
• D - departmentName:tagName format is tempting because it looks like namespacing, but it's still just a string convention - there's no enforcement, access control, or schema management behind it.

Memory tip: Think of namespaces like file system directories - you wouldn't store every file in one flat folder and rely on naming prefixes to organize them. Namespaces give you real structure, not just decoration on a string.

No community discussion yet for this question.