Legit CAP-C01 Exam Download

Simple Log Service (SLS) is the appropriate logging platform for an ACK Serverless environment. Serverless Kubernetes removes much of the node-management responsibility, so the logging architecture should follow the same managed-service model rather than introduce dedicated log-processing infrastructure.

Alibaba Cloud provides native SLS integration for ACK Serverless. SLS can collect container standard output and application log files and then provide centralized search, analysis, dashboards, alerting, and downstream shipping. Alibaba documentation specifically states that ACK Serverless provides managed SLS capabilities and supports collecting container logs directly into SLS.

ARMS is primarily an application performance monitoring and observability platform; it does not replace SLS as the core centralized log-ingestion service. Option C is incorrect because SLS supports near-real-time collection and analysis. Option D also misunderstands serverless logging: scaling events do not inherently require dedicated logging servers.

The architecture should therefore preserve the operational advantages of serverless compute by using SLS as a fully managed, elastic logging layer capable of handling workload fluctuations without requiring the organization to provision and administer separate logging infrastructure.

Study Guide reference: Core Infrastructure Deep Dive — ACK, serverless container architecture, observability, and Simple Log Service.

Function Compute and Simple Message Queue form an appropriate serverless, event-driven backend for bursty mobile workloads.

Function Compute is fully managed and automatically allocates elastic compute resources when functions are invoked. Alibaba Cloud bills Function Compute primarily according to actual configured resources and execution duration, allowing the startup to avoid maintaining continuously running application servers. This is particularly suitable for APIs and backend handlers experiencing unpredictable request spikes.

SMQ provides managed asynchronous messaging for decoupling backend components. It supports queue-based processing and publish-subscribe topics, making it suitable for notification events, background jobs, workflow messages, and traffic buffering. Alibaba Cloud explicitly identifies load leveling during sudden traffic spikes as an SMQ use case.

SMQ can also directly trigger Function Compute through queue or topic integrations, creating an event-driven design without dedicated message-consumer servers.

ECS requires persistent server resources and management, which conflicts with the requested serverless operating model. MaxCompute is a large-scale data warehouse and batch analytics platform rather than the application ' s transactional API or messaging layer.

Therefore, Function Compute supplies elastic execution while SMQ provides reliable asynchronous communication and notification-event handling.

Study Guide reference: Delivering Services and Content on Alibaba Cloud — Function Compute, serverless architectures, SMQ, event-driven integration, and elastic application services.

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

The public web tier needs an inbound security-group rule permitting TCP 443 from Internet clients. Therefore, Option E is required. Security groups act as virtual firewalls and should expose only application ports required by the workload. Alibaba Cloud recommends allowing public access only to necessary web-service ports such as HTTPS 443 while keeping internal services inaccessible from the Internet.

For the database tier, access should be limited to ECS instances belonging to the web-server security group. Alibaba Cloud RDS for MySQL supports associating an ECS security group with an RDS instance, allowing ECS instances in that group to connect without adding every server address individually to an IP whitelist. This is particularly useful when application-server membership changes dynamically.

Option B is overly broad because every resource within the public vSwitch ' s CIDR could potentially be authorized rather than only the approved web tier. Option C would prevent legitimate database traffic. Option D is unnecessary because RDS access behaves as an allow-list model: only explicitly authorized addresses or associated security-group members should be granted database access.

Thus, Internet clients reach the web tier only over HTTPS, while MySQL accepts access only from the authorized application servers.

Study Guide reference: Securing Workloads on Alibaba Cloud — Security Groups, RDS access control, least privilege, and tiered network segmentation.

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