Quiz: Knowledge Representation and Management
Test your understanding of knowledge graphs, ontologies, taxonomies, and enterprise knowledge management with graph databases.
1. What is a concept dependency graph?
- A graph showing financial dependencies
- A directed graph showing prerequisite relationships between learning concepts, indicating which concepts must be learned before others
- A backup system
- A type of relational database
Show Answer
The correct answer is B. A concept dependency graph is a directed graph representing prerequisite relationships between learning concepts—an edge from A to B means "concept A depends on understanding B first." This creates a pedagogical roadmap ensuring concepts are learned in optimal order, foundational concepts before advanced ones.
Concept Tested: Concept Dependency Graphs
See: Concept Graphs
2. What is an ontology in the context of knowledge representation?
- A medical specialty
- A formal representation of knowledge domains defining concepts, relationships, and logical rules governing their interactions
- A type of graph database
- A programming language
Show Answer
The correct answer is B. An ontology is a formal representation of a knowledge domain that defines concepts, their properties, relationships, and logical rules. For example, a medical ontology defines diseases, symptoms, treatments with formal relationships like "diabetes hasSymptom frequent_urination" and reasoning rules, enabling AI systems to understand and infer knowledge.
Concept Tested: Ontologies
See: Ontology Modeling
3. What is SKOS and what is it used for?
- A type of database
- Simple Knowledge Organization System, a W3C standard for representing controlled vocabularies and taxonomies as linked data
- A programming framework
- A network protocol
Show Answer
The correct answer is B. SKOS (Simple Knowledge Organization System) is a W3C standard for representing controlled vocabularies, taxonomies, and thesauri as linked data. It defines relationships like broader/narrower (category hierarchies), preferred/alternate labels (synonyms), and related terms, enabling semantic interoperability across systems.
Concept Tested: SKOS
See: SKOS Standard
4. What distinguishes a glossary from a taxonomy?
- They are the same thing
- A glossary provides term definitions, while a taxonomy organizes terms hierarchically from general to specific
- Glossaries are always longer
- Taxonomies cannot be represented in graphs
Show Answer
The correct answer is B. A glossary provides definitions of terms (alphabetically organized reference), while a taxonomy organizes terms hierarchically showing parent-child (broader-narrower) relationships. For example, a glossary defines "automobile" but a taxonomy shows "vehicle > motorized vehicle > automobile > sedan." Both are valuable knowledge organization tools, often used together.
Concept Tested: Glossaries, Taxonomies
5. How do personal knowledge graphs differ from enterprise knowledge graphs?
- They use different database technologies
- Personal knowledge graphs organize individual notes and concepts for personal use, while enterprise knowledge graphs capture organization-wide information
- Personal knowledge graphs are always smaller
- There is no difference
Show Answer
The correct answer is B. Personal knowledge graphs organize an individual's notes, concepts, research, and insights for personal knowledge management (tools like Obsidian or Roam). Enterprise knowledge graphs capture organization-wide knowledge—business processes, project information, expert knowledge, documented procedures—for enterprise-scale knowledge management and decision support.
Concept Tested: Personal Knowledge Graphs, Enterprise Knowledge
6. What is knowledge capture and why is it important?
- Backing up databases
- The systematic recording and structuring of expertise, decisions, and insights for organizational preservation and reuse
- Deleting old knowledge
- Encrypting data
Show Answer
The correct answer is B. Knowledge capture is the systematic process of recording and structuring expert knowledge, decisions, insights, and lessons learned. This transforms tacit knowledge (in people's heads) into codifiable knowledge (documented in systems), preventing knowledge loss when experts leave, enabling knowledge sharing across teams, and supporting organizational learning.
Concept Tested: Knowledge Capture
See: Knowledge Management
7. Given a requirement to model a company's organizational knowledge including projects, documents, experts, and concepts, how would you structure a graph?
- Use a single table
- Create nodes for each entity type (Project, Document, Person, Concept) with relationships like AUTHORED, WORKED_ON, RELATES_TO capturing connections
- Store everything in text files
- Don't use a graph
Show Answer
The correct answer is B. An enterprise knowledge graph would have nodes for Projects, Documents, People, Concepts, and Departments with rich relationships: (Person)-[:AUTHORED]->(Document), (Person)-[:EXPERT_IN]->(Concept), (Document)-[:RELATES_TO]->(Project), (Concept)-[:DEPENDS_ON]->(Concept). This structure enables semantic search ("find experts who worked on projects related to AI"), knowledge discovery, and insight extraction.
Concept Tested: Enterprise Knowledge, Knowledge Management
8. What distinguishes tacit knowledge from codifiable knowledge?
- Tacit knowledge is experiential and difficult to document, while codifiable knowledge can be explicitly documented and transferred
- They are the same thing
- Tacit knowledge is always better
- Codifiable knowledge cannot be stored
Show Answer
The correct answer is A. Tacit knowledge is experiential, intuitive knowledge difficult to codify (expert troubleshooting intuition, judgment calls). Codifiable knowledge can be explicitly documented (procedures, specifications, facts). Knowledge graphs excel at capturing codifiable knowledge and some tacit knowledge (by linking documented cases, expert decisions, and contextual factors), though true experiential tacit knowledge requires mentorship.
Concept Tested: Tacit Knowledge, Codifiable Knowledge
See: Knowledge Types
9. How can controlled vocabularies improve data quality in knowledge graphs?
- By deleting data
- By ensuring consistent terminology through standardized lists of approved terms, preventing synonyms and ambiguity
- By encrypting vocabulary
- By making vocabularies random
Show Answer
The correct answer is B. Controlled vocabularies provide standardized lists of approved terms ensuring consistent terminology across an organization. For example, mandating "myocardial infarction" instead of varying terms like "heart attack" or "MI" prevents ambiguity, improves searchability, and enables better analytics. This is especially critical in domains like healthcare, law, and science.
Concept Tested: Controlled Vocabularies
10. Why are knowledge graphs increasingly important for AI and large language models?
- They're not important for AI
- Knowledge graphs provide structured context, facts, and relationships that ground AI responses in verified information and enable reasoning
- AI doesn't use knowledge
- Knowledge graphs replace AI
Show Answer
The correct answer is B. Knowledge graphs provide structured, verified knowledge that AI systems can use for grounding (connecting language to facts), reasoning (following logical relationships), and context (understanding domain-specific information). When combined with language models, knowledge graphs reduce hallucinations, enable fact-checking, support multi-hop reasoning, and provide explainable AI by tracing inference paths through the graph.
Concept Tested: Knowledge Representation, Enterprise Knowledge
Quiz Complete!
Questions: 10 Cognitive Levels: Remember (2), Understand (4), Apply (2), Analyze (2) Concepts Covered: Concept Dependency Graphs, Ontologies, SKOS, Glossaries, Taxonomies, Controlled Vocabularies, Personal Knowledge Graphs, Enterprise Knowledge, Knowledge Capture, Tacit Knowledge, Codifiable Knowledge, Knowledge Management
Next Steps: - Explore Chapter Content for knowledge graph examples - Practice designing knowledge representation schemas - Continue to Chapter 9: Modeling Patterns and Data Loading