ACP-Cloud1 Exam Dumps : ACP Cloud Computing Certification

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.

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

A route table is a set of rules that determine how network traffic is routed within a VPC or between different network instances1. A VRouter is a hub that connects all VSwitches in the same VPC and enables communication between them2. When you create a VPC, a VRouter and a default route table are automatically created for the VPC1. The default route table contains system routes that are automatically generated by the system based on the network topology1. The system routes cannot be modified or deleted1.

However, you can also create custom route tables for your VPC and add custom routes to them1. Custom routes are manually configured by users to route traffic to specific destinations, such as other VPCs, VBRs, VPN Gateways, or NAT Gateways1. Custom routes can be modified or deleted as needed1. You can also associate VSwitches with different route tables to implement fine-grained routing control1.

Therefore, the statement that the routing entries of the route table can not be modified manually is not correct, as it only applies to system routes, not custom routes. The other statements are correct, as each VRouter may have multiple route tables, one default and several custom1; when a VPC is deleted, the corresponding route table is also deleted3; and the default route table cannot be deleted1. References: Route table overview - Virtual Private Cloud - Alibaba Cloud Documentation Center, VRouter overview - Virtual Private Cloud - Alibaba Cloud Documentation Center, Delete a VPC - Virtual Private Cloud - Alibaba Cloud Documentation Center

With a measurement cycle of 5 minutes and a requirement for five consecutive cycles where disk usage exceeds 80%, it would take 5×5=255 \times 5 = 255×5=25 minutes for CloudMonitor to confirm the condition. After confirmation, CloudMonitor typically processes and sends the alert, which may take an additional 5 minutes, totaling approximately 30 minutes before you receive the alert.