Information Architecture Practice Exam

Question 1 Information Architecture

What is "card sorting"?

Grouping related items into meaningful clusters — improves comprehension and memory. Navigation present on every page — supports orientation throughout the site. A user-research technique where participants group topics into categories — surfaces intuitive structure. Labels should match the words users would use — not internal jargon or product naming.

Question 2 Information Architecture

What is "tagging strategy"?

Splitting a multi-step task across screens — wizard pattern; supports complex flows but adds clicks. The plan for how content is tagged: vocabulary source, tagger roles, frequency of audit, governance. A scoring scheme assessing IA against criteria — surfaces weak areas for improvement. Search UI letting users narrow results by selecting facet values — e.g., e-commerce product filters.

Question 3 Information Architecture

What is "Nielsen's 10 usability heuristics"?

More linguistically accurate stemming using grammatical knowledge — slower but higher quality. Multiple ways to navigate the same content (by topic, by audience, by format) — supports diverse user needs. A metric (often Jaccard index) measuring how consistently participants grouped items together. Jakob Nielsen's classic principles (visibility of status, match real world, user control, etc.) — adapted to IA.

Question 4 Information Architecture

What is "skim reading"?

Studying where participants click first on a page; first clicks correlate strongly with task success. Users scan, not read; IA should support skimming through headings, bullets, and clear hierarchy. If labels are vague or internally focused, users cannot tell where to click next. Whether users can find links that exist — links not visible during normal flow effectively don't exist.

Question 5 Information Architecture

What is "spelling tolerance"?

Links within content area pointing to related content — supports lateral discovery. Search returning results despite typos — essential as small misspellings shouldn't cause zero results. The plan for how content is tagged: vocabulary source, tagger roles, frequency of audit, governance. Experts reviewing IA against known principles — finds many issues cheaply without users.

Question 6 Information Architecture

What is "path-based breadcrumb"?

A scoring scheme assessing IA against criteria — surfaces weak areas for improvement. Shows the actual sequence of pages the user visited — historical, not hierarchical. Users picking the first acceptable option rather than the best — IA labels should clearly signal best matches. A navigation hierarchy is the structure of categories, sections, and pathways users move through to reach content.

Question 7 Information Architecture

What is the "three-click rule" critique?

A large drop-down panel exposing many sub-options at once — useful for large IAs but hides items behind hover. Good IA reduces confusion, improves discoverability, and makes interfaces feel easier to use. The old "users will leave after 3 clicks" rule is largely a myth — depth matters less than clarity. A plan for what content gets published when — supports IA by avoiding gaps and pile-ups.

Question 8 Information Architecture

What is "the IA governance plan"?

A navigation hierarchy is the structure of categories, sections, and pathways users move through to reach content. Decisions about who can add categories, change labels, retire content — keeps IA from drifting. Specific governance for UI patterns and navigation components — usually owned by the design system team. The ease with which users can effectively use what they've found — IA supports but doesn't ensure it.

Question 9 Information Architecture

What is "directness" in tree testing?

A visual of the user's full experience over time — informs IA by showing what content is needed when. Whether participants reached the answer without backtracking — high directness = clear paths. A diagrammatic site structure used during design — different from XML sitemaps for SEO. Labels should match the words users would use — not internal jargon or product naming.

Question 10 Information Architecture

What are the four IA components (Morville/Rosenfeld)?

System should use familiar concepts and conventions, not internal jargon — directly applies to IA. Organization systems, labeling systems, navigation systems, search systems — each addresses a different findability dimension. Overlapping categories create ambiguity and make people second-guess every navigation choice. Navigation organized around what users want to do — strong when tasks are clear.

Question 11 Information Architecture

What is the "affinity diagram"?

Each level contains the next, with no cross-links — purely hierarchical, often too rigid for modern content. Content grouping is the practice of clustering related material into sections that make sense to users. Eye-tracking pattern showing users skim down the left and across the top — IA should put critical info in that path. Grouping ideas or research findings by similarity to surface themes — useful for synthesizing IA inputs.

Question 12 Information Architecture

What is "mental-model alignment"?

Reducing words to a root form (running → run) so different forms match — built into most search engines. IA succeeds when navigation matches how users think — not how the organization thinks. A trailing path showing the user's location in the hierarchy — supports orientation and lateral navigation up the tree. Grouping related items into meaningful clusters — improves comprehension and memory.

Question 13 Information Architecture

What is "local navigation"?

Decisions about who can add categories, change labels, retire content — keeps IA from drifting. Navigation specific to a section or page — supports deep exploration within a topic. Findable, Accessible, Interoperable, Reusable — foundational for data IA, increasingly adopted broadly. A schema describing content types, their fields, and their relationships — foundation for CMS and rendering.

Question 14 Information Architecture

What is "mega menu"?

Organization systems, labeling systems, navigation systems, search systems — each addresses a different findability dimension. A large drop-down panel exposing many sub-options at once — useful for large IAs but hides items behind hover. A hierarchical classification system organizing content into categories and subcategories. The current click should match the user's prediction; misalignment erodes trust.

Question 15 Information Architecture

What is labeling in information architecture?

Eye-tracking pattern for simpler pages — users scan top-left to top-right, diagonal down, then left to right. The mobile screen area easily reached by a thumb — primary nav should land there. The old "users will leave after 3 clicks" rule is largely a myth — depth matters less than clarity. Labeling is the naming of menus, sections, links, and content so users can predict what they will find.

Question 16 Information Architecture

What is "the curse of knowledge" in labeling?

Navigation by alphabetical order — useful when users know exact names (employee directory, glossary). Pre-defined categories with an option to add new ones — balances discovery and validation. Insiders pick labels obvious to them but cryptic to users — research prevents this. A trailing path showing the user's location in the hierarchy — supports orientation and lateral navigation up the tree.

Question 17 Information Architecture

What is a "thesaurus" in IA?

A controlled vocabulary that records relationships (synonyms, broader, narrower, related) between terms. Comparing two label variants to measure click-through or task success — sometimes only data settles the debate. Site-wide controls (login, language, search) — distinct from content navigation, typically top-right. A diagrammatic site structure used during design — different from XML sitemaps for SEO.

Question 18 Information Architecture

What is a sitemap?

Labels with the most important word first — easier to scan in long lists. Primary navigation at the bottom of mobile screens — within thumb reach, easier than top. A predefined set of terms used to consistently describe and tag content — reduces ambiguity in tagging and search. A sitemap is a high-level map of the pages or content areas in a website or product.

Question 19 Information Architecture

What is "accordion navigation"?

Jakob Nielsen's classic principles (visibility of status, match real world, user control, etc.) — adapted to IA. Expandable sections collapsing siblings — saves space but can hide content from search and reduce discoverability. A sitemap is a high-level map of the pages or content areas in a website or product. Cross-links help users move laterally when content belongs to more than one journey or use case.

Question 20 Information Architecture

What is "content" in the three-circle model?

The actual material being organized — its volume, type, format, ownership, and freshness. Business goals, technology constraints, culture, resources, and politics shaping the design. A button explicitly loading more results — balances browsing flow and footer access. Whether participants reached the answer without backtracking — high directness = clear paths.

Question 21 Information Architecture

What is the "hamburger menu" debate?

A hierarchical classification system organizing content into categories and subcategories. The stages content moves through: planning, creation, review, publishing, maintenance, archive, removal. Evaluating content quality, voice, and relevance — slower than inventory but reveals what should change. Concealing primary nav behind an icon reduces clutter but hurts discoverability — generally worse for engagement on desktop.

Question 22 Information Architecture

What is "continuous metadata"?

Numeric or temporal values (date, price) — best for sorting and range filtering. A word in a label that triggers user recognition that they're close to their goal. Eye-tracking pattern for simpler pages — users scan top-left to top-right, diagonal down, then left to right. System should use familiar concepts and conventions, not internal jargon — directly applies to IA.

Question 23 Information Architecture

What is "structured content"?

Content broken into reusable fields (title, summary, body, image) — enables omnichannel publishing. Labels with the most important word first — easier to scan in long lists. Shows the user's place in the site hierarchy — most common type. Digital Asset Management — system for storing, tagging, and reusing media assets.

Question 24 Information Architecture

What is a strong IA principle?

Percentage of participants who chose the correct destination on the first try. Insiders pick labels obvious to them but cryptic to users — research prevents this. Organize information around user tasks and expectations, not around internal org charts. People find things faster when the structure matches how they naturally think about the content.

Question 25 Information Architecture

What is "the 1-second rule" in IA?

URL structure communicates hierarchy to users and search engines — should mirror navigation. If users can't get a sense of where they are within 1 second of arrival, IA needs work. Navigation organized around subjects — common in publishing and reference content. Conventions for tone, formatting, capitalization, terminology — keeps content coherent across authors.

Question 26 Information Architecture

What is "Dublin Core"?

A predefined set of terms used to consistently describe and tag content — reduces ambiguity in tagging and search. The top-level navigation visible across the site — usually 4–9 main sections. Sub-navigation within a section — gives access to related content without crowding the primary nav. A core metadata standard (15 elements: title, creator, subject, etc.) widely used in libraries and digital archives.

Question 27 Information Architecture

Why is clear labeling important?

More linguistically accurate stemming using grammatical knowledge — slower but higher quality. A word in a label that triggers user recognition that they're close to their goal. Allowing items to be described by multiple independent attributes (color, size, brand) for flexible filtering. If labels are vague or internally focused, users cannot tell where to click next.

Question 28 Information Architecture

What is "synonym expansion"?

Navigation by alphabetical order — useful when users know exact names (employee directory, glossary). Designing for mobile constraints first, then expanding to larger screens — prevents desktop-bloat. Labels using verbs ("Get help") rather than nouns ("Help center") — better for task-oriented IA. Search treating different terms (e.g., "car", "auto") as equivalent — helps when user vocabulary differs from content vocabulary.

Question 29 Information Architecture

What is "ranking" in search?

Navigation by place — common for maps, locations, multi-region content. Algorithm deciding which results appear first — based on relevance, recency, popularity, personalization. Site-wide controls (login, language, search) — distinct from content navigation, typically top-right. An IA anti-pattern is a structure that looks neat internally but forces users to guess where things belong.

Question 30 Information Architecture

What is "navigation analytics"?

Tracking which navigation paths users actually use — exposes labels and structures that work or don't. People find things faster when the structure matches how they naturally think about the content. Users picking the first acceptable option rather than the best — IA labels should clearly signal best matches. Pre-defined categories with an option to add new ones — balances discovery and validation.

Question 31 Information Architecture

What is the recommended sample size for card sorting?

Usually 15–30 participants per audience segment — diminishing returns beyond ~30. A content inventory is a list of existing pages or assets used to understand what exists before reorganizing it. A file listing all URLs for search engines to crawl — improves SEO but doesn't replace good navigation. A visual of the user's full experience over time — informs IA by showing what content is needed when.

Question 32 Information Architecture

What is a "human-readable URL"?

URL using words instead of IDs — improves shareability and search ranking. Digital Asset Management — system for storing, tagging, and reusing media assets. Labels with the most important word first — easier to scan in long lists. A tree diagram visualizing card-sort results showing how items cluster — primary card sort output.

Question 33 Information Architecture

What is "faceted search"?

Search UI letting users narrow results by selecting facet values — e.g., e-commerce product filters. Deep IA has fewer items per level but more levels; broad IA has many items per level but few levels. A hierarchical classification system organizing content into categories and subcategories. If labels are vague or internally focused, users cannot tell where to click next.

Question 34 Information Architecture

What is "context" in the three-circle model?

Discrete tag values (e.g., topic, status) — best for filtering and faceted browse. Business goals, technology constraints, culture, resources, and politics shaping the design. A trailing path showing the user's location in the hierarchy — supports orientation and lateral navigation up the tree. Eye-tracking pattern for simpler pages — users scan top-left to top-right, diagonal down, then left to right.

Question 35 Information Architecture

What is "polyhierarchy"?

When an item legitimately belongs in multiple categories — IA must handle this without creating chaos. Surfacing facets and suggestions in search UI — search becomes the primary way to navigate. If labels are vague or internally focused, users cannot tell where to click next. Searches returning no results — gold mine for IA improvements (synonyms, content gaps, label fixes).

Question 36 Information Architecture

What is card sorting?

The actual underlying structure of the content or business — often differs from users' mental models. Cross-links help users move laterally when content belongs to more than one journey or use case. A button explicitly loading more results — balances browsing flow and footer access. Card sorting is a research method where users group topics or items to reveal intuitive category structures.

Question 37 Information Architecture

What is "personalized search ranking"?

Use platform conventions to leverage existing user knowledge — applies to navigation patterns. Tailoring results to the individual user's history — improves relevance but risks filter bubbles. A navigation hierarchy is the structure of categories, sections, and pathways users move through to reach content. Users choose the path requiring the least cognitive effort — IA should make the right path the easiest.

Question 38 Information Architecture

What is a faceted navigation system?

Deliberate cross-linking among related content — supports both wayfinding and SEO. Faceted navigation lets users filter content across multiple attributes such as topic, date, or level. Tree testing checks whether users can find information inside a proposed navigation structure without visual design distractions. Studying where participants click first on a page; first clicks correlate strongly with task success.

Question 39 Information Architecture

What is the IA "three-circle" model?

Experts reviewing IA against known principles — finds many issues cheaply without users. The intersection of users, content, and context — IA decisions must respect all three. A comprehensive page covering a broad topic, linked from many related cluster pages. How many clicks users take to reach goal pages — deep paths often indicate structural problems.

Question 40 Information Architecture

What is "the most important factor in IA success"?

A more complex semantic structure capturing entities, attributes, and relationships between them. Insiders pick labels obvious to them but cryptic to users — research prevents this. Conventions for tone, formatting, capitalization, terminology — keeps content coherent across authors. Validation with real users — internal logic almost never matches user expectations precisely.

Question 41 Information Architecture

What is "wayfinding"?

Create Once, Publish Everywhere — structured content powering multiple surfaces from one source. A predefined set of terms used to consistently describe and tag content — reduces ambiguity in tagging and search. The cognitive process of orienting and navigating — covers "Where am I?", "Where can I go?", "How do I get back?" Search UI letting users narrow results by selecting facet values — e.g., e-commerce product filters.

Question 42 Information Architecture

What is "the chronological IA"?

Concealing primary nav behind an icon reduces clutter but hurts discoverability — generally worse for engagement on desktop. Navigation by time — natural for news, blogs, and historical archives. Depth means more nested levels; breadth means more choices per level, and good IA balances the trade-off. A controlled vocabulary that records relationships (synonyms, broader, narrower, related) between terms.

Question 43 Information Architecture

What is "a 301 redirect"?

Designing IA to manipulate users (hidden cancel, deceptive labels) — short-term gain, long-term trust damage. A permanent redirect — tells browsers and search engines the page has moved permanently. Logical grouping reduces search effort and helps users build a clearer picture of the system. A short statement guiding all IA decisions in a project — used to resolve edge cases consistently.

Question 44 Information Architecture

What is "contextual navigation"?

Links within content area pointing to related content — supports lateral discovery. Navigation organized around what users want to do — strong when tasks are clear. Surfacing the same content piece in multiple contexts — IA must support without creating duplicates. The current click should match the user's prediction; misalignment erodes trust.

Question 45 Information Architecture

What is "discoverability"?

When an item legitimately belongs in multiple categories — IA must handle this without creating chaos. A CMS exposing structured content via API — separates content from presentation, supports COPE. Inventorying every content type, its fields, and how it's used — surfaces redundancy and gaps. The likelihood a user encounters content they didn't know to look for — separate from findability.

Question 46 Information Architecture

What is information scent?

Counting pages, types, traffic, age — fast picture of scale and patterns. Information scent is the degree to which navigation cues suggest that the right answer is nearby. A visual of the user's full experience over time — informs IA by showing what content is needed when. The top-level navigation visible across the site — usually 4–9 main sections.

Question 47 Information Architecture

What is "link discoverability"?

Specific governance for UI patterns and navigation components — usually owned by the design system team. Whether users can find links that exist — links not visible during normal flow effectively don't exist. Decisions about who can add categories, change labels, retire content — keeps IA from drifting. Algorithm deciding which results appear first — based on relevance, recency, popularity, personalization.

Question 48 Information Architecture

What is "hybrid card sorting"?

Navigation by place — common for maps, locations, multi-region content. A button explicitly loading more results — balances browsing flow and footer access. Findability is how easily users can locate the information or action they need. Pre-defined categories with an option to add new ones — balances discovery and validation.

Question 49 Information Architecture

What is "the pillar page"?

A diagram showing all pages, content types, and their relationships — used to communicate structure. Business goals, technology constraints, culture, resources, and politics shaping the design. A comprehensive page covering a broad topic, linked from many related cluster pages. Organization systems, labeling systems, navigation systems, search systems — each addresses a different findability dimension.

Question 50 Information Architecture

What is "the content style guide"?

Conventions for tone, formatting, capitalization, terminology — keeps content coherent across authors. A large drop-down panel exposing many sub-options at once — useful for large IAs but hides items behind hover. Organize information around user tasks and expectations, not around internal org charts. Organizing content around pillar topics with cluster pages linking to them — both IA and SEO benefit.