Pass the Alibaba Cloud Computing ACP-Cloud1 Questions and answers with ValidTests

Auto Scaling in Alibaba Cloud supports event-triggered tasks based on CPU workload, memory utilization rate, inbound and outbound traffic, and Disk IOPS as key metrics for scaling decisions. Average system workload (option C) is not a directly supported metric, making options A, B, D, and E correct. These metrics allow Auto Scaling to respond to real-time performance needs.

Elastic Computing on Alibaba Cloud ECS includes features that allow users to quickly start or release multiple instances, upgrade bandwidth without downtime, adjust CPU and memory configurations, and perform horizontal scaling in conjunction with Server Load Balancer (SLB). However, option E is incorrect as there is a limit to the number of disks that can be attached to an ECS instance.

 Changing an instance’s operating system requires creating a custom image or using a public image, and then replacing the system disk of the instance. This process will cause the instance to restart. Therefore, this statement is false. References: ECS User Guide: Replace the system disk (non-public image) and ECS User Guide: Replace the system disk (public image)

The safest response to a seldom-used IP alert connecting to ApsaraDB for RDS is to adjust the IP whitelist to allow only trusted IP addresses. By limiting the IP addresses in the whitelist, unauthorized or unfamiliar IP addresses cannot access the database. This approach provides direct control over access to RDS and minimizes potential security risks. Checking SQL audit logs (as suggested in option D) is useful but not sufficient on its own for a comprehensive security response.

In Alibaba Cloud, a scaling group can be associated with multiple SLB instances as long as they are in the same region, allowing distributed load handling across multiple load balancers. However, there is no requirement for SLB instances or scaling configurations to be in the same zone, making it region-specific instead of zone-specific.

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

After stopping an Alibaba Cloud Elastic Compute Service (ECS) instance, you will not be charged for the instance usage fee or the public bandwidth fee (if applicable) until you start the instance again. However, you will still be charged for the disk usage fee and the snapshot usage fee (if applicable) regardless of which region the instance is located in. This is because the disks and snapshots are still occupying the storage space and need to be billed accordingly. Therefore, the statement is false. References: 1 - Billing FAQ - Alibaba Cloud Document Center - What fees do I need to pay after I stop a Pay-As-You-Go instance?

Alibaba Cloud RDS uses a master-slave or primary-replica architecture to provide high availability. In the event of a master database failure, automatic failover to the standby instance generally occurs within 30 seconds, helping to minimize downtime and maintain service continuity.

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

ECS instance monitoring provides a process monitoring feature that allows you to check the status of specific processes, such as a Python process, and set alerts for automatic notifications if the process terminates unexpectedly. This method is quicker and more efficient than writing a custom script or manually logging in to the console.

When changing the specifications of an RDS instance, service interruptions can occur during some upgrade and downgrade operations, depending on the RDS instance type and the complexity of the change. While upgrades are generally supported, certain modifications may result in brief downtime as the system reconfigures resources. This is contrary to option B. Additionally, database version downgrades are restricted, and MySQL 5.1 can indeed be upgraded directly to MySQL 5.6 in Alibaba Cloud RDS.

Active/standby server groups are a feature of Server Load Balancer (SLB) that allows you to configure a primary ECS instance and a secondary ECS instance for the backend of an SLB instance1. When the primary instance is working properly, the traffic is only forwarded to the primary ECS. When the primary instance is down, traffic is switched to the standby instance1. This feature is supported by TCP and HTTPS listeners, but not by HTTP and UDP listeners1. TCP and HTTPS listeners support session persistence, which ensures that requests from the same client are always forwarded to the same backend server2. HTTP and UDP listeners do not support session persistence, and they use round-robin or weighted round-robin algorithms to distribute traffic among the backend servers2. References: 1: Create an active/standby server group 2: [Configure a listener]