Oracle NoSQL Database for Administrators — Lesson 2: Cluster Administration, Topology Changes, Capacity, and Availability

Technical Scope

• administration CLI, plans, services, parameters, and configuration state
• adding or removing storage nodes, shards, replicas, and zones
• rebalancing, failover behavior, quorum, durability, and consistency trade-offs
• capacity expansion, maintenance windows, rollback, and post-change checks

Instructor Demonstration

Demonstrate administration CLI, plans, services, parameters, and configuration state within a resilient Oracle NoSQL cluster deployed across availability zones, secured for application access, monitored under load, and tested for node failure and recovery, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering adding or removing storage nodes, shards, replicas, and zones and rebalancing, failover behavior, quorum, durability, and consistency trade-offs, then test a failure, exception, or business-control scenario involving capacity expansion, maintenance windows, rollback, and post-change checks.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The Cluster Administration, Topology Changes, Capacity, and Availability result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in administration CLI, plans, services, parameters, and configuration state, adding or removing storage nodes, shards, replicas, and zones, rebalancing, failover behavior, quorum, durability, and consistency trade-offs, or capacity expansion, maintenance windows, rollback, and post-change checks without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for Cluster Administration, Topology Changes, Capacity, and Availability and defend the result with documented evidence.