Alibaba Cloud CAP-C01 Exam With Confidence Using Practice Dumps

The existing architecture has two important bottlenecks: a single ECS compute node and files stored on storage attached to that individual ECS instance. Option E eliminates the compute single point of failure. A custom image allows identical ECS instances to be created, while Auto Scaling maintains multiple instances and ALB distributes requests across healthy backends. This provides horizontal scalability and significantly stronger application availability.

Option D addresses shared application storage. File Storage NAS is a managed, POSIX-compatible shared filesystem that multiple ECS instances can mount concurrently. All web servers therefore see the same files, while NAS handles storage scalability and consistency independently from the ECS lifecycle.

Option A improves performance by moving cacheable website content toward users. CDN serves static resources from nearby POPs and reduces requests and bandwidth reaching the origin infrastructure.

Although OSS is excellent for native object-storage workloads, mounting OSS through ossfs does not provide the same filesystem semantics and consistency characteristics as NAS for a traditional application requiring minimal modification. Global Accelerator primarily optimizes network paths and does not eliminate the application ' s compute or storage single points of failure.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — ALB, Auto Scaling, NAS shared storage, and CDN.

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

This is fundamentally a lift-and-shift filesystem workload. The applications already depend on standard operating-system file interfaces, and the requirement explicitly states that application code should not be changed. ECS therefore preserves the existing Linux and Windows execution environments, while File Storage NAS supplies managed shared filesystem semantics.

Alibaba Cloud NAS supports NFS and SMB protocols and is designed specifically for workloads migrating from traditional file servers. Alibaba documentation describes NAS as appropriate for lift-and-shift applications because existing applications can continue using standard filesystem calls, path structures, and file-locking behavior without rewriting file I/O logic.

For cross-operating-system sharing, Alibaba Cloud recommends SMB when Linux and Windows clients must access the same filesystem, and Linux ECS can mount SMB when cross-platform data sharing is required.

OSS would change the storage interface from filesystem semantics to object APIs, normally requiring application changes. Message Queue changes the application ' s data exchange architecture. ACK introduces unnecessary containerization complexity.

Therefore, Linux ECS + Windows ECS + managed NAS most closely preserves the existing application model while eliminating the operational problems associated with manually synchronized on-premises file systems.

Study Guide reference: Core Infrastructure Deep Dive — ECS migration, File Storage NAS, NFS/SMB, and lift-and-shift architecture.

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.