ACP-Cloud1 Exam Dumps : ACP Cloud Computing Certification

ApsaraDB for RDS is a stable and reliable online database service that supports MySQL, SQL Server, PostgreSQL, MariaDB, and PPAS. ApsaraDB for RDS provides a read/write splitting feature that allows you to create read-only RDS instances, which can offload read requests from the primary RDS instance of your database system1. Read/write splitting is implemented by using a dedicated proxy endpoint, which routes read and write requests to different RDS instances based on the SQL statements and the read weights of the read-only instances2. By using ApsaraDB for RDS to implement read/write splitting, you can achieve the following benefits21:

Read requests are distributed to multiple instances. This can improve the read performance and availability of your database system, as well as balance the load among the read-only instances. You can specify the read weights of the read-only instances to control the distribution of read requests.

Read/write requests to the database are separated. This can reduce the pressure on the primary RDS instance and ensure the stability and security of the write operations. You only need to connect to the proxy endpoint, and the proxy will automatically route the read and write requests to the appropriate RDS instances.

The other statements are not correct, as write requests are not distributed to multiple instances, but only sent to the primary RDS instance2; and both read and write requests are not distributed to multiple instances, but separated by the proxy endpoint2. References: [ApsaraDB for RDS - Alibaba Cloud], Read/write splitting - - Alibaba Cloud Documentation Center, Use the read/write splitting feature to increase the processing capability of an ApsaraDB RDS instance

For Layer-4 SLB using TCP, the health check determines ECS instance availability based on the successful completion of a TCP 3-way handshake. This ensures that the backend server is reachable and can accept connections, which is critical for reliable TCP-based load balancing.

=================

 To execute a task at a specific time such as removing 1 ECS instance every night at 00:00, you need to perform two operations: create a scaling rule and create a scheduled task. A scaling rule is a set of instructions that defines how Auto Scaling scales computing resources in response to changes in business load. A scheduled task is a type of scaling task that can execute a specified scaling rule at a specified time. By creating a scaling rule that removes 1 ECS instance from the scaling group, and creating a scheduled task that executes this scaling rule every night at 00:00, you can achieve the desired result. You do not need to create a new scaling group, because you already have one scaling group created. You also do not need to create an event-triggered task, because this type of scaling task is triggered by events such as Cloud Monitor alarms or API calls, not by a specific time. References: 1, 2, and 3.