Oracle NoSQL Database for Administrators Ed 2 — Lesson 2: Tables, Keys, Data Modeling, Indexes, Consistency, and Durability

Learning Objectives

• Explain the purpose and operating context of key-value and table APIs, primary keys, shard keys, and data distribution.
• Apply JSON and table data modeling, hierarchy, evolution, and schema choices and secondary indexes, query access, selectivity, and maintenance in a controlled environment.
• Validate outcomes and troubleshoot risks involving consistency, durability, timeouts, versioning, and application trade-offs.

Detailed Topics

• key-value and table APIs, primary keys, shard keys, and data distribution
• JSON and table data modeling, hierarchy, evolution, and schema choices
• secondary indexes, query access, selectivity, and maintenance
• consistency, durability, timeouts, versioning, and application trade-offs

Instructor Demonstration

Demonstrate key-value and table APIs, primary keys, shard keys, and data distribution for a distributed key-value and table workload deployed, secured, expanded, and recovered across storage nodes; capture the exact configuration, code, command, transaction, query, dashboard, model, schedule, or report evidence that proves the expected result.

Hands-On Exercise

Complete a controlled Oracle NoSQL Database for Administrators Ed 2 exercise covering JSON and table data modeling, hierarchy, evolution, and schema choices and secondary indexes, query access, selectivity, and maintenance; introduce an exception involving consistency, durability, timeouts, versioning, and application trade-offs, diagnose it from evidence, apply the smallest reversible correction, and rerun acceptance checks.

1. Confirm scope, prerequisites, identities, dependencies, data, risks, and expected outcome.
2. Perform the course-specific configuration, development, administration, analysis, or business-process workflow.
3. Capture commands, settings, records, logs, screenshots, reports, metrics, or test results.
4. Compare the observed result with acceptance criteria and document corrective or preventive action.

Scenario Analysis

• Identify the technical or business decision and the stakeholders affected by it.
• Compare security, performance, reliability, compliance, cost, usability, and support trade-offs.
• Define rollback, recovery, communication, evidence, ownership, and escalation requirements.

Troubleshooting Guidance

Diagnose issues involving key-value and table APIs, primary keys, shard keys, and data distribution, JSON and table data modeling, hierarchy, evolution, and schema choices, secondary indexes, query access, selectivity, and maintenance, consistency, durability, timeouts, versioning, and application trade-offs without making an unverified production change. Separate symptoms from causes, gather time-correlated evidence, test a reversible hypothesis, validate the correction, and record recurrence controls.

Validation Checklist

• The requirement, environment, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by product-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, support actions, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply Tables, Keys, Data Modeling, Indexes, Consistency, and Durability in a realistic Oracle NoSQL Database for Administrators Ed 2 scenario and defend the result with documented evidence.