Q51 — AWS SAA-C03 第3章
第 51/65 题 | ← 返回第3章
Q181.一家公司正在开发一个电子商务应用程序,该应用程序将由一个负载平衡的前端. 一个基于容器的应用程序和一个关系数据库组成.解决方案架构师需要创建一个高度可用的解决方案,该解决方案的运行需要尽可能少的人工干预.哪些解决方案满足这些要求? (选择两个.)
- A. 在多可用区模式下创建一个 Amazon RDS 数据库实例. ✓
- B. 在另一个可用区中创建一个 Amazon RDS 数据库实例和一个或多个副本.
- C. 创建一个基于 Amazon EC2 实例的 Docker 集群来处理动态应用程序负载.
- D. 创建一个具有 Fargate 启动类型的 Amazon Elastic Container Service (Amazon ECS) 集群来处理动态应用程序负载. ✓
- E. 创建一个具有 Amazon EC2 启动类型的 Amazon Elastic Container Service (Amazon ECS) 集群来处理动态应用程序负载.
正确答案: A. 在多可用区模式下创建一个 Amazon RDS 数据库实例., D. 创建一个具有 Fargate 启动类型的 Amazon Elastic Container Service (Amazon ECS) 集群来处理动态应用程序负载.
解析
To create a highly available solution for an ecommerce application that consists of a load-balanced front-end, a container-based application, and a relational database that operates with as little manual intervention as possible, the recommended solutions are options A and D: Option A, creating an Amazon RDS DB instance in Multi-AZ mode, helps to ensure high availability and reduces the need for manual intervention. In Multi-AZ mode, Amazon RDS automatically provisions and maintains a synchronous standby replica in another Availability Zone (AZ), hence providing automatic failover functionality in case of a primary database instance failure. The standby replica is promoted automatically to become the new primary instance when needed without manual intervention. Option D, creating an Amazon Elastic Container Service (Amazon ECS) cluster with a Fargate launch type to handle the dynamic application load, also helps to ensure high availability with minimal manual intervention. Fargate is a serverless compute engine for containers that enables developers to run containers without having to manage servers or clusters. By utilizing Fargate to deploy containerized applications, developers can focus on building and scaling their applications without worrying about infrastructure management. Fargate automatically scales the underlying infrastructure based on application demand, making it easier to achieve high availability. Option B, creating an Amazon RDS DB instance and one or more replicas in another Availability Zone, is a valid option for ensuring high availability but requires more manual intervention than Option A. While having read replicas in another AZ can help improve read performance and increase availability, automatic failover functionality is not guaranteed in this scenario. In addition, managing multiple read replicas across different AZs can be complex and require additional monitoring and maintenance. Option C, creating an Amazon EC2 instance-based Docker cluster to handle the dynamic application load, involves manual intervention to manage the underlying infrastructure. This approach requires the creation and management of EC2 instances, network settings, load balancing, and other components of the infrastructure, which increases the complexity of the solution. Option E, creating an Amazon Elastic Container Service (Amazon ECS) cluster with an Amazon EC2 launch type to handle the dynamic application load, is a valid option but requires more manual intervention than Option D. With this approach, developers need to manage the underlying infrastructure for the EC2 instances, including scaling and availability. The use of Fargate in Option D helps to automate many of these tasks and reduce the need for manual intervention.要为一个由负载均衡前端、基于容器的应用程序和关系数据库组成的电子商务应用程序创建一个高可用性的解决方案,该解决方案的操作尽可能少地需要人工干预,建议的解决方案是选项a和D: 选项A,在Multi-AZ模式下创建一个Amazon RDS DB实例,有助于确保高可用性并减少人工干预的需要。在Multi-AZ模式下,Amazon RDS在另一个可用区(Availability Zone, AZ)中自动提供和维护一个同步备用副本,从而在主数据库实例发生故障时提供自动故障转移功能。当需要时,备用副本将自动提升为新的主实例,而无需人工干预。 选项D,使用Fargate启动类型创建Amazon Elastic Container Service (Amazon ECS)集群来处理动态应用程序负载,也有助于以最少的人工干预确保高可用性。Fargate是一个用于容器的无服务器计算引擎,它使开发人员无需管理服务器或集群就可以运行容器。通过使用Fargate来部署容器化的应用程序,开发人员可以专注于构建和扩展他们的应用程序,而不必担心基础设施管理。Fargate根据应用程序需求自动扩展底层基础设施,使其更容易实现高可用性。 选项B(在另一个可用区中创建一个Amazon RDS DB实例和一个或多个副本)是确保高可用性的有效选项,但比选项a需要更多的人工干预。虽然在另一个可用区中拥有读取副本有助于提高读取性能和增加可用性,但在此场景中不能保证自动故障转移功能。此外,管理跨不同az的多个读副本可能很复杂,需要额外的监控和维护。 选项C,创建一个基于Amazon EC2实例的Docker集群来处理动态应用程序负载,涉及到手动干预来管理底层基础设施。这种方法需要创建和管理EC2实例、网络设置、负载平衡和基础设施的其他组件,这增加了解决方案的复杂性。 选项E,使用Amazon EC2启动类型创建Amazon Elastic Container Service (Amazon ECS)集群来处理动态应用程序负载,是一个有效的选项,但比选项d需要更多的人工干预。使用这种方法,开发人员需要管理EC2实例的底层基础设施,包括可伸缩性和可用性。在选项D中使用Fargate有助于自动化许多这些任务,并减少人工干预的需要。