Taxonomy is one of the most frequently misused features in Drupal. Acquia uses this module to test whether you understand classification vs content, and whether you can choose the correct Drupal tool for organizing information.
Many exam questions are phrased as simple requirements but actually test your architectural judgment.
What taxonomy means in Drupal
Taxonomy is Drupal’s system for classification and categorization.
Taxonomy is used when:
- Values come from a controlled list
- The same value is reused across many content items
- Content needs to be filtered, grouped, or faceted
Taxonomy terms are entities, but they are not content in the same sense as nodes.
Mental model for recall
Ask this first:
"Is this describing what the content is, or how the content is categorized"
- What the content is → content type
- How the content is categorized → taxonomy
This single question eliminates most wrong answers.
Vocabularies and terms
A vocabulary is a container.
A term is a value inside that container.
Examples:
Vocabulary: States
- California
- Nevada
- Texas
Vocabulary: OSHA Offices
- Region 1
- Region 2
- Area Office – Las Vegas
Vocabulary: Topics
- Fall Protection
- Electrical Safety
- Heat Illness
Site Builder perspective
Site builders use taxonomy to:
- Standardize classification
- Enable filtering in Views
- Support navigation and grouping
They focus on:
- Vocabulary design
- Term naming
- Hierarchies
- Editor usability
Frontend developer perspective
Frontend developers rely on taxonomy to:
- Build filters
- Display categories
- Style grouped content
They expect:
- Predictable term output
- Clean relationships
Taxonomy enables consistent UI patterns without hardcoding logic.
Backend developer perspective
Backend developers interact with taxonomy via:
- Entity references
- Entity queries
- Views relationships
They should avoid:
- Custom classification tables
- Storing categories as plain text
Using taxonomy keeps data structured and queryable.
Architect perspective
Architects evaluate taxonomy for:
- Scalability
- Reuse
- Multilingual support
- Future integrations
Well-designed taxonomies reduce refactoring and migration cost.
Taxonomy vs content types
This distinction is heavily tested.
Use taxonomy when:
- The list is controlled
- Values repeat across content
- The value has no complex lifecycle
Use a content type when:
- The item has multiple fields
- The item has its own page
- The item needs revisions or workflows
Taxonomy vs menus
Another common exam decision.
Use taxonomy when:
- Content is classified
- Filtering is required
Use menus when:
- You are building navigation
- Order matters more than classification
Menus are for navigation, taxonomy is for classification.
Hierarchical taxonomies
Taxonomy supports parent and child relationships.
Examples:
- Topic → Subtopic
- Country → State → City
Hierarchies are useful for:
- Nested filters
- Breadcrumb logic
- Progressive disclosure
Entity reference to taxonomy
Content types typically reference taxonomy terms using an entity reference field.
Example:
- Article references Topics
- Event references State
- Policy references OSHA Office
This creates a clean relationship without duplicating data.
Multilingual considerations
Taxonomy supports translation.
Important considerations:
- Term names may need translation
- Hierarchies must remain consistent
Acquia expects awareness of multilingual implications.
Common exam traps in Module 2.3
- Using taxonomy to store rich content
- Creating content types for fixed lists
- Using menus for classification
- Storing categories as free text
- Overloading taxonomy with business logic
Correct answers favor simplicity and reuse.
Real scenario walkthrough
Scenario:
A site needs to filter blog posts by US state.
Correct solution:
- Create States vocabulary
- Add State taxonomy reference field to Blog
Incorrect solution:
- Free text state field
- Separate content type per state
Key exam takeaways
- Taxonomy is for classification
- Content types represent real entities
- Menus are for navigation
- Entity references connect content
- Configuration comes before code
Practice check
- Controlled list reused across content: taxonomy
- Item with multiple fields and lifecycle: content type
- Navigation structure: menu
- Filtering requirement: taxonomy