A company is planning to migrate its SAP Content Server from on premises to Amazon EC2 instances. The SAP Content Server stores data in a MaxDB database. The on-premises servers run the SUSE Linux…

Question

Options

• AConfigure Amazon Elastic File System (Amazon EFS) file systems for the MaxDB permanent
• BConfigure Amazon FSx for Lustre file systems for the MaxDB permanent storage. Create the
• CConfigure General Purpose SSD (gp2 or gp3) or Provisioned IOPS SSD (io1 or io2) Amazon
• DConfigure Amazon S3 buckets for the MaxDB permanent storage. Create an IAM instance profile
• EConfigure Amazon Elastic Container Service (Amazon ECS) volumes for the MaxDB permanent

• A
  77% (24)
• B
  6% (2)
• D
  3% (1)
• E
  13% (4)

Explanation

For rehosting SAP Content Server with MaxDB on AWS with high availability and resilient storage, two storage layers are needed. Amazon EFS (Option A) is a managed, Multi-AZ NFS file system suitable for SAP shared file systems; it provides built-in redundancy and high availability across Availability Zones without additional configuration. Amazon EBS gp2/gp3/io1/io2 volumes (Option C) are the AWS-recommended block storage types for SAP database persistent storage, offering the IOPS and throughput required by MaxDB. Option B (FSx for Lustre) is a high-performance parallel file system designed for HPC, not SAP database storage. Option D (S3) is object storage and cannot be used as a block device for MaxDB. Option E (ECS volumes) are not appropriate for persistent database storage outside of containerized workloads.

No community discussion yet for this question.