Quiz: Designing Ontologies from Scratch for Business Domains

Quiz Summary

0 of 3 Questions completed

Questions:

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Results

Quiz complete. Results are being recorded.

Results

0 of 3 Questions answered correctly

Your time:

You have reached 0 of 0 point(s), (0)

Question 1 of 3

1. Question

A finance ontology answers every competency question correctly through SPARQL. What does that establish?

That the taxonomy is structurally sound, since a passing CQ suite is a proof of logical correctness.
Correct Incorrect Correct answer

Only that coverage is adequate: a model can satisfy every CQ and still contain taxonomic errors, for example making Employee a subclass of Department rather than a member of it.
Correct Incorrect Correct answer

That the CQ set can now be frozen, because revising requirements after modelling invalidates the ontology.
Correct Incorrect Correct answer

That the formal CQs were written before the informal ones, which is the prescribed order of work.
Correct Incorrect Correct answer

Correct / 1 Points

Incorrect / 1 Points
Question 2 of 3

2. Question

Each tenant of a shared triplestore has its data in a tenant-specific named graph. What is the danger of running a SPARQL query with no GRAPH or FROM clause?

The query fails to parse, because a graph must always be named in a quad store.
Correct Incorrect Correct answer

The query is restricted to the default graph, so tenant data can never be exposed.
Correct Incorrect Correct answer

The engine selects one named graph at random, producing non-deterministic but still isolated results.
Correct Incorrect Correct answer

Engines commonly default to the union of all named graphs, which exposes other tenants; queries must be scoped with an explicit GRAPH block or rewritten at the API layer.
Correct Incorrect Correct answer

Correct / 1 Points

Incorrect / 1 Points
Question 3 of 3

3. Question

Tenant A operates where a :taxID is legally mandatory on every :Transaction, while Tenant B operates where it is optional. What is the correct architecture?

Keep one shared OWL core defining :Transaction and enforce the requirement with per-tenant SHACL shapes using sh:minCount, because OWL under the Open World Assumption treats an absent :taxID as unknown rather than as an error.
Correct Incorrect Correct answer

Add an owl:minCardinality 1 restriction on :taxID to the shared :Transaction class, so the reasoner rejects any transaction that omits it.
Correct Incorrect Correct answer

Let each tenant edit the shared OWL ontology directly, so that tenant rules live alongside the semantics they constrain.
Correct Incorrect Correct answer

Assert rdfs:domain on :taxID, which makes the reasoner validate the property for Tenant A only.
Correct Incorrect Correct answer

Correct / 1 Points

Incorrect / 1 Points

Quiz: Designing Ontologies from Scratch for Business Domains

Quiz Summary

Information

Results

Results

Categories

1. Question

2. Question

3. Question