Study guide
14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication
OCI 2026 Architect Professional 1Z0-997-26
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Architecture Foundations
1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs
2 Chapter 2: High Availability & Resilient Design
2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)
3 Chapter 3: Full Stack Disaster Recovery
3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness
4 Chapter 4: Container Instances, OCIR & OCI DevOps
4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies
5 Chapter 5: OCI Kubernetes Engine (OKE)
5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage
6 Chapter 6: Serverless Functions & API Gateway
6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans
7 Chapter 7: Messaging & Event-Driven Design
7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out
8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager
8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints
9 Chapter 9: Identity & Multi-Tenancy Governance
9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas
10 Chapter 10: Security Posture with Cloud Guard & Security Zones
10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning
11 Chapter 11: Secure Access & Network Protection
11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT
12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault
12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation
13 Chapter 13: Base Database Service & Autonomous AI Database
13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database
14 Chapter 14: Recovery Service, Global Distribution & OCI Cache
14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication
15 Chapter 15: Monitoring, Alarms & Notifications
15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery
16 Chapter 16: Logging, Audit, Connector Hub & Search
16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability
14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication
Key Takeaways Explain This Topic AI
OCI Cache is a managed service for memory-based Valkey and Redis clusters that are reached only through a private endpoint in your VCN.
A non-sharded OCI Cache cluster has one to five nodes: one primary node and up to four replica nodes with the same data.
A sharded OCI Cache cluster has an odd number of shards from 3 to 99, with one to five nodes per shard.
OCI Cache requires TLS for client connections and an ingress rule for port 6379 in the cluster's subnet or NSG.
OCI Cache cross-region replication asynchronously copies data from a read-write primary cluster to a read-only secondary cluster in another region.
Last updated: October 2026
Why Add a Cache
Many architectures put a cache in front of the database to reduce latency and database load. OCI Cache is a managed service that builds and operates memory-based Valkey and Redis clusters. OCI manages the compute nodes, patching, and replication, so teams use the familiar Valkey or Redis commands without running their own cache servers.
Common patterns:
Pattern How it works Example
Cache-aside The application checks the cache first; on a miss it reads the database and writes the result to the cache with a time to live (TTL) Product catalog pages
Session store User sessions live in the cache so any application node can serve any user Stateless web tier on OKE
- Leaderboards and counters Sorted sets and atomic counters Gaming scores, rate counters
- Message fan-out Publish/subscribe channels for lightweight notifications Live dashboards
A cache improves performance but is not the system of record. Durable data still belongs in a database such as Autonomous AI Database.
Cluster Modes
Mode Structure Scaling Endpoints
Non-sharded 1 to 5 nodes : one primary plus up to four replicas , all holding the same data More replicas add read capacity and availability Primary endpoint for writes and replica endpoint for reads
Sharded An odd number of shards from 3 to 99 , each shard with 1 to 5 nodes (one primary plus up to four replicas) More shards add write capacity and memory; more nodes per shard add read capacity Private endpoints per shard plus a discovery endpoint ; clients must support cluster mode with hostnames
For a non-sharded cluster, Oracle recommends one primary and two replicas , because a cluster with at least three nodes is more reliable. If the primary fails, a replica is promoted. Node memory can be sized from 2 GB to 500 GB per node.
OCI Cache manages the cluster's compute nodes itself; you cannot attach your own compute instances to a cluster.
Networking and Security
A cluster is reached only through a private endpoint in a subnet of your VCN, typically a private subnet . Applications in other VCNs or on premises connect through peering, a DRG, VPN, or FastConnect.
Add an ingress rule for TCP port 6379 in the subnet's security list or in an NSG attached to the cluster.
Connections require TLS , for example valkey-cli --tls or redis-cli --tls .
Cache users provide access control lists ( ACLs ) that restrict commands and keys per user, and cache users can use IAM authentication , so applications avoid static passwords.
OCI Cache clusters support Zero Trust Packet Routing (ZPR) security attributes, so ZPR policies can control which workloads may connect.
Configuration Sets
OCI Cache exposes only a limited set of engine parameters through configuration sets , such as maxmemory-policy (what to evict when memory is full) and reserved-memory-percentage . You can use the default configuration set or create a custom one and attach it to clusters. Choosing an eviction policy is a design decision: a cache-aside cache usually evicts least recently used keys, while a session store may prefer to reject writes rather than silently drop sessions.
Backups and Recreating Clusters
You can take manual (on-demand) backups of a cluster and create a new cluster from a backup , for example to seed a test environment or recover after accidental deletion of keys.
Monitoring
Cluster metrics are published per node in the oci_redis namespace of OCI Monitoring and can drive alarms and notifications (Chapter 15). Useful ones include MemoryUtilization (Oracle suggests a typical alarm threshold of 85%), CPUUtilization (typical threshold 90%), ConnectedClients , KeyspaceHits and KeyspaceMisses , EvictedKeys , ReplicationLag for replicas, and CrossRegionReplicationLag and CrossRegionMasterLinkStatus for a secondary cluster. A rising miss count often means TTLs are too short or the cache is too small, and growing evictions mean memory is full.
Cross-Region Replication
OCI Cache cross-region replication asynchronously copies data from a primary cluster in one region to a secondary cluster in another region:
The primary supports reads and writes; the secondary is read-only and continuously receives updates. Readers of the secondary must tolerate eventual consistency .
After an initial full synchronization, only changes are sent. If replication is interrupted and the history is no longer available, a new full synchronization runs.
Replication traffic is encrypted and uses private OCI networking.
Planned switchover reverses the roles. Both clusters and regions must be available, and you should stop application writes first.
Disaster recovery: if the primary region is down, switchover is not possible. You convert the secondary to standalone and update applications to use its endpoint. When the original region returns, you set up a new replication relationship.
Putting It Together
A typical web architecture places OKE or Compute application tiers in private subnets, an OCI Cache cluster with one primary and two replicas in the same VCN, and Autonomous AI Database behind it. NSGs allow port 6379 only from the application NSG, cache users restrict what each application can do, and a cross-region secondary cluster supports the disaster recovery plan alongside Autonomous Data Guard.