Practice English vocabulary for maintaining knowledge graphs: entity updates, refresh schedules, orphaned node cleanup, entity resolution, and graph health scores.
0 / 10 completed
1 / 10
What does 'the entity is updated when the source data changes' mean?
Knowledge graph freshness depends on change detection and propagation. This can be triggered by CDC (Change Data Capture) streams, periodic batch jobs comparing source hashes, or webhooks from source systems notifying the graph of updates.
2 / 10
What is 'the graph refresh schedule' for a knowledge graph?
Refresh schedules balance data freshness needs against the cost of re-ingestion. Critical entities (product prices, news articles) may refresh hourly; stable entities (historical facts, geographic data) may only need weekly updates.
3 / 10
What are 'orphaned nodes' and why are they cleaned up?
Orphaned nodes accumulate when source records are deleted but the graph cleanup job doesn't run, or when relationship data changes. They waste storage, distort graph metrics, and can surface in queries as seemingly valid entities with no useful connections.
4 / 10
What is 'entity resolution' that 'merges duplicates'?
Entity resolution (also called entity matching or deduplication) uses similarity algorithms, unique identifiers, and ML models to recognize that 'Apple Inc.', 'Apple Computer', and 'AAPL' all refer to the same entity — then merging them into one node with all related data.
5 / 10
What does 'the graph health score tracks data freshness and completeness' measure?
Graph health scores give operators a single number representing graph quality. Freshness measures how recently data was updated (e.g., % of entities updated in the last 7 days). Completeness measures how many required fields are populated. Low scores trigger investigation and remediation.
6 / 10
Sarah from the Data Engineering team sent you this Slack message: 'Just ran a full graph refresh. Seems like we're still seeing some inconsistencies with product categories – lots of 'Electronics' nodes pointing to different SKUs than what's in our main inventory database. Anyone know why this might be happening?' What is Sarah most likely referring to?
Sarah is describing a 'graph refresh', which is the automated process of updating the knowledge graph from its source systems. The message highlights inconsistencies *after* the refresh, indicating that not all changes were successfully propagated and resolved – a common issue requiring investigation into data mapping or transformation logic. Option A is possible but doesn't explain the context of the Slack conversation.
7 / 10
You're reviewing a PR description for a change to the knowledge graph schema. The description reads: 'Adding new 'Variant' entity type to allow for more granular product representation. This will require updating existing mappings and potentially triggering a full graph refresh to ensure consistency.' What does the phrase 'triggering a full graph refresh' imply?
'Triggering a full graph refresh' signifies a complete rebuild process. This is necessary because adding a new entity type (like 'Variant') likely affects relationships and mappings across the entire knowledge graph. A targeted update wouldn't guarantee consistency with the newly introduced data; options A, C, and D represent more localized actions. Full refreshes are typically scheduled or triggered when significant schema changes occur.
8 / 10
Ben, a senior developer, is explaining the concept of 'entity resolution' to a junior colleague during a standup update. He says: 'Entity resolution is like finding all the different ways someone might refer to the same thing – think about customer IDs or product SKUs. We use it to merge duplicates and create a single, authoritative representation in our knowledge graph.' What's Ben's primary focus regarding entity resolution?
Ben correctly describes entity resolution as the process of merging duplicate entities based on shared attributes (like customer IDs or SKUs). The goal isn't just to have unique identifiers but to create a single, consistent record. Option A discusses optimization, while options B and D represent related, but distinct, aspects of knowledge graph management.
9 / 10
You're analyzing the API response from the Knowledge Graph Service. The response includes this JSON snippet: {'status': 'success', 'changes': [{'entity_id': 'product_123', 'new_attributes': {'color': 'red', 'size': 'M'}}]}. What does the 'changes' array indicate?
The 'changes' array lists entities that have been modified within the knowledge graph. Each object contains the entity's ID and the newly added or updated attributes. This reflects the fundamental operation of updating an existing entity – a core function of maintaining the knowledge graph. Options A, C, and D represent different types of API responses.
10 / 10
During a code review discussion, another developer points out that your PR description for updating the 'Customer' entity lacks detail about how changes to customer addresses are handled. You respond: 'We'll need to ensure the graph health score accurately reflects data freshness and completeness after this update.' What does the 'graph health score' primarily measure in this context?
The 'graph health score' is designed to measure data freshness and completeness – essentially, how current and accurate the knowledge graph is. While address accuracy is important (option A), it's only one factor contributing to overall graph health. The refresh schedule (option B) influences health but isn't the primary metric itself; option D focuses on update volume.
What will I practise in "Knowledge Graph Maintenance Vocabulary"?
Practice English vocabulary for maintaining knowledge graphs: entity updates, refresh schedules, orphaned node cleanup, entity resolution, and graph health scores.
How many exercises are in this module?
This module has 10 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Knowledge Graph Vocabulary exercises?
Browse the full Knowledge Graph Vocabulary hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.