A. Before starting the Launch Wizard deployment create the underlying Amazon Elastic Block Store (Amazon EBS) volume types to use for SAP HANA data and log volumes based on the performance requirements

B. Use a value for the PaceMakerTag parameter that is not used by any other Amazon EC2 instances in the AWS Region where the system is being deployed

C. Ensure that the virtual hostname for the SAP HANA database that is used for the SUSE Linux Enterprise High Availability Extension configuration is not used in any other deployed accounts

D. Ensure that the Virtual Address parameter is outside the VPC CIDR and is not being used in the route table that is associated with the subnets where primary and secondary SAP HANA instances will be deployed

E. Before starting the Launch Wizard deployment set up the SUSE Linux Enterprise High Availability Extension network configuration and security group

A. Before the migration window build a new installation of the SAP system on AWS by using SAP Software Provisioning Manager

B. Before the migration window build a new installation of the SAP system on AWS by using SAP Software Provisioning Manager Back up the Oracle database by using native Oracle tools Copy the backup of the Oracle database to AWS through the Direct Connect connection Import the Oracle database to me SAP system on AWS Configure Oracle Data Guard to begin replication on-premises database log changes from the SAP system to the new AWS system During the migration window use Oracle to replicate any remaining changes to the Oracle database hosted on AWS Switch over to the SAP system on AWS

C. Before the migration window build a new installation of the SAP system on AWS by using SAP Software Provisioning Manager Create a staging Oracle database on premises to perform Cross Platform Transportable Tablespace (XTTS) conversion on the Oracle database Take a backup of the convened staging database Copy the converted backup to AWS through the Direct Connect connection import the Oracle database backup to the SAP system on AWS Take regularly scheduled incremental backups and XTTS conversions of the staging database Transfer these backups and conversions to the AWS target database During the migration window, perform a final incremental Oracle backup Convert the final Oracle backup by using XTTS Replay the logs in the target Oracle database hosted on AWS Switch over to the SAP system on AWS

D. Before the migration window launch an appropriately sized Amazon EC2 instance on AWS to receive the migrated SAP database Create an AWS Server Migration Service (AWS SMS) job to take regular snapshots of the on-premises Oracle hosts Use AWS SMS to copy the snapshot as an AMI to AWS through the Direct Connect connection Create a new SAP on Oracle system by using the migrated AMI During the migration window take a final incremental SMS snapshot and copy the snapshot to AWS Restart the SAP system by using the new up-to-date AMI Switch over to the SAP system on AWS

A. General Purpose SSD (gp3) Amazon Elastic Block Store (Amazon EBS) volumes

B. Amazon Elastic File System (Amazon EFS) Standard-Infrequent Access (Standard-IA) storage class

C. Amazon FSx for Windows File Server

D. Provisioned IOPS SSD (io2) Amazon Elastic Block Store (Amazon EBS) volumes

A. Use SAP Software Provisioning Manager to perform a system export/import for SAP S/4HANA SAP BW

B. Use backup and restore tor SAP S'4HANA

C. Use backup and restore for SAP S’4 HAN A and SAP BW 4HANA Use SAP Software Provisioning Manager to perform a system export import for SAP Solution Manager Reinstall SAP Web Dispatcher on AWS with the necessary configuration

D. Use SAP HANA system replication to replicate the data between the source system and the target AWS system for SAP S 4HANA and SAP BW 4HANA Use SAP Software Provisioning Manager to perform a system export import for SAP Solution Manager Reinstall SAP Web Dispatcher on AWS with the necessary configuration

B. AWS Application Migration Service (CloudEndure Migration) C

A. Install a new SAP Solution Manager instance and a new SAP router instance m the AWS environment Connect the POC systems to these new instances Use these new instances m parallel with the on-premises SAP Solution Manager instance and the on-premises SAP router instance

B. Install a new SAP Solution Manager instance and a new SAP router instance in the AWS environment install the Amazon CloudWatch agent on all on-premises instances Push the monitoring data to the new SAP Solution Manager instance Connect ail on-premises systems and POC systems on AWS to the new SAP Solution Manager instance and the new SAP router instance Remove the onpremises SAP Solution Manager instance and the on-premises SAP router instance Use the new instances on AWS C

A. Use AWS CloudFormation StackSets to apply SCPs to multiple accounts in multiple Regions

B. Use an AWS Elastic Beanstalk blue green deployment to create 1AM policies and apply them to multiple accounts together Use an Amazon CloudWatch dashboard to check the applied policies in the accounts

C. Implement guardrails by using AWS CodeDeploy and AWS CodePipeline to deploy SCPs into each account Use the CodePipeline deployment dashboard to check the applied policies in the accounts

D. Apply SCPs through AWS Control Tower Use the AWS Control Tower integrated dashboard to check the applied policies in the accounts

A. Create an AWS Transit Gateway in a central networking account Attach the transit gateway to the AWS accounts Set up routing and a network ACL to establish communication

B. Set up VPC peering between the accounts Configure routing in each VPC to use the VPC peering links

C. Create a transit VPC that uses the hub-and-spoke model set up routing to use the transit VPC for communication between the SAP systems

D. Create a VPC link for each SAP system Use the VPC links to connect the SAP systems

A. Reduce the global_allocation_limit parameter to i 120 GiB

B. Migrate the SAP HANA database to an EC2 High Memory instance with a larger number of available vCPUs C

E. Change to a supported compute optimized instance type for SAP HANA

A. Maintain persistence by using session cookies Enable session stickiness (session affinity) on the SAP Web Dispatchers by setting the wdisp/HTTP/esid_support parameter to True

B. Maintain persistence by using session cookies Enable session stickiness (session affinity) on the ALB

C. Turn on host-based routing on the ALB to route traffic between the SAP Web Dispatchers

D. Turn on URL-based routing on the ALB to route traffic to the application based on URL

A. Set up SAP Solution Manager to call Amazon CoudWatch and Amazon EC2 endpoints with RESTbased calls to populate SAPOSCOL details Use SAP transaction ST06N to monitor CPU and memory utilization on each EC2 instance

B. Install the AWS Data Provider for SAP on the Amazon EC2 instances that host SAP Allow access to the Amazon CloudWatch and EC2 endpoints through a NAT gateway Create an IAM policy that allows the ec2 Describeinstances action the cloudwatch

A. Ensure mat AWS Backint agent is configured to send the backups to an Amazon S3 bucket over the internet Ensure that the EC2 instance is configured to access the internet through a NAT gateway

B. Check the UploadChanneiSize parameter for AWS Backint agent increase this value in the awsbackint- agent-config yaml configuration file based on the EC2 instance type and storage configurations

C. Check the MaximumConcurrentFilesForRestore parameter tor AWS Backint agent Increase the parameter from 5 to 10 by using the aws-backint-agent-config yaml configuration file

D. Ensure that the backups are compressed if necessary configure AWS Backint agent to compress the backups and send them to an Amazon S3 bucket

A. Set up AWS CloudFormation to automatically launch a new EC2 instance for the SAP HANA database in a second Availability Zone from backups that are stored in Amazon S3 When the SAP HANA database is operational perform a database restore by using the standard SAP HANA restore process

B. Launch a secondary EC2 instance for the SAP HANA database on a less powerful EC2 instance type in a second Availability Zone Configure SAP HANA system replication with the preload option turned off

C. Launch a secondary EC2 instance tor the SAP HANA database o wn an equ wivalent E wC2 inst

D. Set up AWS CloudFormation to automatically launch a new EC2 instance for the SAP HANA database in a second Availability Zone from backups that are stored in Amazon Elastic Block Store (Amazon EBS) When the SAP HANA database is operational perform a database restore by using the standard SAP HANA restore process

A. Perform a lift-and-shift migration of all the systems to AWS Migrate the ERP system that is not from SAP to SAP ECC Convert all three systems to SAP S/4HANA by using SAP Software Update Manager (SUM) Database Migration Option (DMO) Consolidate all three SAP S4HANA systems into a final SAP &4HANAsystem Decommission the other systems

B. Perform a lift-and-shift migration of an the systems to AWS Migrate the enterprise's initial system to SAP HANA, and then perform a conversion to SAP S/4HANA Consolidate the two systems from the acquired companies with this SAP S4HANA system by using the Selective Data Transition approach with SAP Data Management and Landscape Transformation (DMLT)

C. Use SAP Software Update Manager (SUM) Database Migration Option (DMO) with System Move to re-architect the enterprise initial system to SAP S'4HANA and to change the platform to AWS Consolidate the two systems from the acquired companies with this SAP S 4HANA system by using the Selective Data Transition approach with SAP Data Management and Landscape Transformation (DMLT)

D. Use SAP Software Update Manager (SUM) Database Migration Option (DMO) with System Move to re-architect all the systems to SAP S/4HANA and to change the platform to AWS Consolidate all three SAP S-4HANA systems two a final SAP S/4HANA system Decommission the other systems

A. Write an rsync script Schedule the script through cron for four times each day in the on-premises VMware servers to transfer the data from on premises to AWS

B. Install an AWS DataSync agent on the on-premises VMware platform Use the DataSync endpoint to synchronize between the on-premises NFS server and Amazon EFS on AWS C

A. Create an AWS Transit Gateway Attach the VPCs to the transit gateway Add the appropriate routes m the subnet route tables

B. Establish a VPC peering connection between the two VPCs Add the appropriate routes in the subnet route tables C

A. Download the SAP HANA software

B. Download the AWS CloudFormation template for the SAP HANA deployment

C. Download and extract the SAP HANA software upload the SAP HANA software to an FTP server that Launch Wizard can access

D. Upload the unextracted SAP HANA software to an Amazon S3 destination bucket Follow the S3 file path syntax for the software in accordance with Launch Wizard recommendations

E. Bring the operating system AMI by using the Bring

F. Create the SAP file system by using Amazon Elastic Block Store (Amazon EBS) before the deployment

A. Install the CloudWatch agent on the servers before installing the AWS Data Provider tor SAP

B. Download the AWS Data Provider for SAP installation package from AWS Marketplace Use an operating system super user to install the agent manually or through a script C

A. Use SAP Software Provisioning Manager to perform an export ofw the systwems Cowpy the ex

B. Use SAP Software Provisioning Manager to perform parallel export import of the systems to migrate the systems to SUSE Linux Enterprise Server and Oracle Database on AWS

C. Use SAP Software Provisioning Manager to perform parallel export/import of the systems to migrate the systems to Oracle Enterprise Linux and Oracle Database on AWS

D. Use SAP Software Provisioning Manager to perform an export of the systems Copy the export to Amazon S3 Use SAP Software Provisioning Manager to perform an import of the systems to Oracle Enterprise Linux and Oracle Database on AWS

A. Install the tier 1 primary system and the tier 2 secondary system in eu-central-1 Configure the tier 1 system m Availability Zone 1 Configure the tier 2 system m Availability Zone 2 Configure SAP HANA system replication between tier 1 and tier 2 by using ASYNC replication mode install the OR tier 3 secondary system m eu-west-1 by using SYNC replication mode

B. Install the tier 1 primary system and the tier 2 secondary system in eu-central-1 Configure the tier 1 system in Availability Zone 1 Configure the tier 2 system m Availability Zone 2 Configure SAP HANA system replication between tier 1 and tier 2 by using SYNC replication mode Install the OR her 3 secondary system n eu-west-1 by using ASYNC replication mode

C. Install the tier 1 primary system and the tier 2 secondary system in eu-central-1 Configure the tier 1 system in Availability Zone 1 Configure the tier 2 system in Availability Zone 2 Configure SAP HANA system replication between tier 1 and tier 2 by using SYNC replication mode Install the OR tier 3 secondary system n eu-west-1 Store daily backups from tier 1 m an Amazon S3 bucket m eu-central-1 Use S3 Cross-Region Replication to copy the daily backups to eu-west- i where they can be restored if needed

D. install the tier 1 primary system in eu-central-1 install the tier 2 secondary system and the DR tier 3 secondary system m eu-west-1 Configure the tier 2 system in Availability Zone 1 Configure the tier 3 system in Availability Zone 2 Configure SAP HANA system replication between all tiers by using ASYNC replication mode

E. Install the tier 1 primary system and the tier 2 secondary system in eu-central-1 Configure the tier 1 system m Availability Zone 1 Configure the tier 2 system m Availability Zone 2 Configure SAP HANA system replication between tier 1 and tier 2 by using SYNCMEM replication mode Install the DR tier 3 secondary system in eu-west-1 by using ASYNC replication mode