A company is running its production SAP HANA system on AWS. The SAP HANA system is hosted on an Amazon EC2 instance that runs SUSE Linux Enterprise Server 12. The operating system patch version is out

Question

Options

• AUse the SUSE Linux Enterprise Server patching update process and SUSE tools to apply the
• BUse AWS Systems Manager Patch Manager to automatically apply the patches to the existing
• CUse AWS Launch Wizard for SAP to provision a second SAP HANA instance with an AMI that
• DUse AWS Launch Wizard for SAP to provision a second SAP HANA instance with an AMI that

• A
  5% (1)
• B
  27% (6)
• C
  59% (13)
• D
  9% (2)

Explanation

The least-downtime approach is to provision a second SAP HANA instance using AWS Launch Wizard with an AMI that already contains the required patched OS (C). This 'build new, cut over' pattern means all patching work is done offline while the production system remains live. Only a brief cutover window is needed, significantly reducing downtime compared to patching in place. Patching in place with SUSE tools (A) requires applying many prerequisite patches sequentially, then a system restart - all during a maintenance window on the production instance. AWS Systems Manager Patch Manager (B) automates patch application but still requires restarting the production instance. Option D, while similar to C, likely describes provisioning without the pre-patched AMI, requiring patch application after launch and therefore more downtime.

No community discussion yet for this question.