RCE study plan

Map the Data Resilience domain objectives to your own environment so you can name every backup, snapshot, and replication control you already operate

Define what 'resilience' means operationally for each data tier (RPO/RTO per application class) and write those targets down

Install or obtain lab access to the Agentic Cyber Resilience Platform and complete first-login, licensing, and role-assignment setup

Inventory existing data sources the platform can protect and record which are unmanaged today

Configure a protection policy in the lab that enforces immutability or object lock on a backup target and verify a delete attempt is blocked

Differentiate snapshot, image-level, and agent-based backup approaches and select the right one per data tier from week 1

Build a restore test for a file-level recovery and record actual recovery time against the RPO/RTO target

Explain to a non-technical stakeholder why immutable backups matter against ransomware encryption of production and backup stores

Map Identity Resilience objectives to your directory and identity provider landscape, noting hybrid vs cloud-only paths

Identify privileged accounts, service accounts, and non-human identities, then rank them by blast radius

Configure MFA or phishing-resistant authentication on a test privileged account and document the enrollment flow

Draft the identity recovery question set: how would you restore a deleted directory object, a compromised admin, and a corrupted identity store

Perform a directory or identity-store recovery in the lab and time how long it takes to restore a single object versus a full store

Design a break-glass procedure for when the identity provider itself is unavailable, and test at least one step of it

Define what 'clean' means for cyber recovery: how you validate that restored data is free of attacker persistence

Compare isolated recovery environment options and note which one your lab can actually exercise

Build an end-to-end recovery orchestration in the lab: detect, isolate, restore, validate, and return to production

Sequence recovery dependencies across at least three tiers (identity, data, application) and document the correct order

Write validation checks that confirm restored workloads are clean before they rejoin the network

Rehearse a ransomware scenario end to end and capture where the orchestration stalled

Inventory SaaS workloads and cloud accounts in scope and classify each by data sensitivity and recovery capability

Configure a SaaS backup or export for one workload and confirm you can restore a deleted item without vendor support

Map the shared responsibility model for your cloud provider and identify which resilience controls are yours to own

Test cross-account or cross-region recovery for one cloud resource and record the recovery point achieved

Configure alerting, reporting, and health monitoring in the platform so a failed protection job surfaces within your SLA

Set up role-based access control that separates platform administration from recovery operations

Review platform audit logs and confirm you can trace who restored what and when

Tune retention and storage settings to balance cost against the recovery points your week 1 targets demand

Run a full-scope mock exam under timed conditions and score each of the five domains separately

Re-study only the two lowest-scoring domains, focusing on objectives you could not explain aloud

Re-derive the RPO/RTO, immutability, identity recovery, and orchestration concepts from memory without notes

Assemble a one-page personal cheat sheet of facts you repeatedly missed