Azure AZ-120 study plan

Map each on-premises SAP component (ASCS, ERS, PAS/AAS, database, SAProuter) to its target Azure resource type and justify the choice in writing.

Compare SAP-certified Azure VM families for the target database and application tiers, and record the sizing rationale for each tier.

Identify which SAP notes, certification lists, and support prerequisites must be verified before any migration begins, and build a checklist.

Draft a migration cutover timeline that sequences database export, data transfer, and application bring-up with owner names.

Size Azure disks and throughput for the database tier using SAP storage KPIs, and document the calculation for data, log, and backup volumes.

Design the network topology for the migration, including hub-spoke peering, subnets, and required egress paths.

Select a data transfer method for the database volume and justify it against the available bandwidth and downtime window.

Write the rollback procedure for a failed cutover, including decision points and validation checks.

Build a landing zone checklist covering subscription design, resource groups, tagging, and policy assignments for SAP workloads.

Configure Azure Monitor and the SAP solution extension so that SAP application and database metrics land in one workspace.

Deploy a non-production SAP system end to end in a lab subscription to validate the design assumptions from weeks 1 and 2.

Document every deviation between the planned design and what actually deployed, with the reason for each.

Design the identity and access model, including managed identities, role assignments, and separation of duties for SAP administrators.

Define the backup and restore configuration for the database and file shares, and state the recovery point objective each setting supports.

Implement Azure Backup or a native database backup strategy in the lab and verify a restore completes.

Produce a cost estimate broken down by compute, storage, network, and licensing for the target architecture.

Design the high availability topology for ASCS/ERS and the database, naming the clustering technology and the Azure infrastructure features each depends on.

Explain how Azure load balancers, proximity placement groups, and availability zones interact in the chosen HA design, and note the constraints of each.

Provision the HA cluster in the lab and demonstrate a failover of the central services instance.

Write the failure scenario matrix mapping each single point of failure to its detection method and automated response.

Design the disaster recovery strategy, choosing the replication mechanism for the database and the region pairing for the target.

Set recovery time and recovery point objectives per tier and show how each design decision meets them.

Document the DR runbook with ordered steps, validation gates, and the authority to declare a disaster.

Test a partial DR exercise, such as a database replica promotion in an isolated network, and record the outcome.

Define the patching and maintenance cadence for the OS, database, and SAP kernel, including how Azure maintenance windows are coordinated with SAP downtime.

Build a monitoring and alerting baseline that covers host health, SAP application availability, and backup success.

Automate one recurring operational task, such as start/stop scheduling or disk expansion, and document the runbook.

Draft an incident response procedure for a production outage that names escalation contacts and diagnostic data to collect.

Complete a timed practice assessment across all four domains and record the score per domain.

Review every missed objective and write a corrective summary tying it back to the relevant design decision.

Re-verify the weakest two domains by rebuilding the affected configuration in the lab without referring to notes.

Consolidate the eight weeks of deliverables into a single architecture and operations portfolio for reference.