PAS-C01 · Question #87
A company is running an SAP Commerce application in a development environment. The company is ready to deploy the application to a production environment on AWS. The company expects the production app
The correct answer is B. Use an Amazon Aurora MySQL database that runs on serverless DB instance types.. SAP Commerce (formerly Hybris) supports MySQL-compatible databases, making Amazon Aurora MySQL a valid backend. Aurora Serverless v2 automatically scales compute (ACUs) and memory up during peak sales/promotional traffic and scales back down during idle periods, directly minimizi
Question
A company is running an SAP Commerce application in a development environment. The company is ready to deploy the application to a production environment on AWS. The company expects the production application to receive a large increase in transactions during sales and promotions. The application's database must automatically scale the storage, CPU, and memory to minimize costs during periods of low demand and maintain high availability and performance during periods of high demand. Which solution will meet these requirements?
Options
- AUse an SAP HANA single-node deployment that runs on burstable performance Amazon EC2
- BUse an Amazon Aurora MySQL database that runs on serverless DB instance types.
- CUse a HyperSQL database that runs on Amazon Elastic Container Service (Amazon ECS)
- DUse an Amazon RDS for MySQL DB cluster that consists of high memory DB instance types.
How the community answered
(24 responses)- A17% (4)
- B75% (18)
- C4% (1)
- D4% (1)
Explanation
SAP Commerce (formerly Hybris) supports MySQL-compatible databases, making Amazon Aurora MySQL a valid backend. Aurora Serverless v2 automatically scales compute (ACUs) and memory up during peak sales/promotional traffic and scales back down during idle periods, directly minimizing cost during low demand. It also provides Multi-AZ high availability natively. Option A (SAP HANA on burstable EC2) is an uncommon and unsupported configuration for SAP Commerce. Option C (HyperSQL on ECS) is an in-memory/embedded database not suited for production-scale workloads. Option D (RDS for MySQL on fixed high-memory instances) does not auto-scale compute or memory and overprovisioning would increase costs during low demand.
Topics
Community Discussion
No community discussion yet for this question.