Pass the Alibaba Cloud Computing CAP-C01 Questions and answers with ExamsMirror

The application needs asynchronous decoupling between high-volume ingestion and database writes. Simple Message Queue provides exactly this load-leveling pattern. The first Function Compute function can acknowledge incoming requests quickly and place each item into SMQ. A second function consumes the queued messages and writes them to RDS at a rate the database can sustain.

SMQ is a distributed managed messaging service specifically designed to decouple producers and consumers. Alibaba Cloud identifies traffic-spike buffering, asynchronous processing, and independent component scaling as core SMQ use cases. Queue messages are delivered at least once during their validity period, significantly improving durability compared with directly coupling every incoming API request to a database write.

Function Compute also integrates directly with SMQ queues and topics as event sources, reducing custom integration and infrastructure management.

Kafka could also provide durable asynchronous messaging, but it is a more elaborate streaming platform than necessary for this workload and therefore carries additional configuration complexity. Moving to ECS reintroduces server administration, while replacing RDS does not solve the ingestion decoupling problem.

Study Guide reference: Core Infrastructure Deep Dive — Function Compute, messaging architectures, asynchronous processing, and scalable application integration.

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

Tair (Redis OSS-Compatible) is the appropriate centralized session-state layer for an elastic, distributed application. When ECS instances frequently scale in and out, application sessions must not depend on the lifecycle of any individual compute node. By storing session tokens and session state in Tair, every ECS instance can retrieve the same session information, making the web/application tier effectively stateless and compatible with Auto Scaling.

Alibaba Cloud Tair is a fully managed Redis-compatible database designed for high throughput, low latency, elastic scalability, and high availability. Alibaba Cloud also documents session-oriented Tair use cases in which session tokens are stored as Redis/Tair data structures with TTL values, demonstrating precisely why the service fits distributed session management.

Session stickiness is weaker because it attempts to keep a user on a specific backend and therefore creates affinity to an instance that might be removed during scaling or failover. CloudMonitor is an observability service, not a session store. STS issues temporary Alibaba Cloud credentials and does not maintain application user sessions.

Consequently, separating session state from ECS compute by storing it in Tair gives the architecture the elasticity and fault tolerance required.

Study Guide reference: Distributed Architecture on Alibaba Cloud; Performant Architecture; Core Infrastructure Deep Dive.

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

Each selected option maps directly to one of the stated enterprise requirements.

A multi-zone PolarDB deployment protects the database against availability-zone-level infrastructure failure. Alibaba Cloud ' s multi-AZ PolarDB architecture keeps replicated data in separate zones and can use standby resources for failover when the primary zone becomes unavailable, resulting in a higher database SLA than a single-zone deployment.

Cloud Backup provides centralized policy-driven backup and recovery for Alibaba Cloud and on-premises resources, including ECS data, databases, NAS, OSS, and other supported workloads. This addresses the requirement for automated application and database protection without building custom backup infrastructure.

RAM roles and associated policies provide fine-grained authorization. RAM policies define allowed actions, affected resources, and optional access conditions, enabling least-privilege access to sensitive student data and administrative services.

Leaving OSS data unencrypted conflicts with the handling of sensitive enterprise information, while manual ACK scaling does not contribute to the stated requirement for high availability or automated operations.

The resulting architecture therefore combines multi-AZ database resilience, managed backup protection, and fine-grained identity authorization.

Study Guide reference: Securing Workloads on Alibaba Cloud — RAM; Building Highly Available, Performant Cloud Architecture — PolarDB HA and Cloud Backup.

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

Option B provides the simplest consolidated content-delivery architecture. Alibaba Cloud CDN can use multiple origins, and current CDN functionality supports origin-selection rules based on parameters such as request path, headers, query strings, and cookies. This allows static requests to be associated with an OSS origin while application requests are forwarded toward the ALB-backed application tier.

Static objects stored in OSS benefit directly from CDN edge caching. Requests are routed to nearby CDN points of presence, and cached resources can be returned without repeatedly accessing the OSS origin, reducing both latency and origin load.

Dynamic responses are generally not cached because they are generated uniquely for requests. They can still be routed to the application origin according to the configured origin rules.

The Global Accelerator alternatives create an unnecessarily fragmented architecture and attempt to use separate acceleration paths where one CDN-facing domain and origin-routing configuration can satisfy the question with fewer components. They also introduce additional DNS and acceleration configuration.

Therefore, a single CDN delivery layer with OSS and ALB-backed origins, combined with Alibaba Cloud DNS directing the application domain to CDN, produces the lowest configuration overhead.

Study Guide reference: Delivering Services and Content on Alibaba Cloud — CDN, OSS acceleration, ALB origins, and intelligent content delivery.

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

The architectural defect is that application state is stored independently on local block storage attached to each ECS instance. ALB can route successive requests to either backend, so each server exposes only the files stored on its own EBS disk. The correct solution is therefore to separate persistent shared data from individual compute instances.

Alibaba Cloud File Storage NAS provides shared file storage that can be mounted concurrently by multiple ECS instances. A single NAS file system becomes the authoritative repository for uploaded documents, so regardless of which ECS instance receives a request, both instances access the same underlying dataset. Alibaba Cloud explicitly supports mounting NAS on multiple ECS instances for shared access.

Periodic EBS synchronization is operationally fragile and introduces consistency windows. ALB session persistence would merely hide the architectural problem and would fail when an ECS instance becomes unavailable or is replaced. Sending every request to both servers would also complicate application logic and still leave divergent storage.

Moving the data to NAS converts the application tier into a horizontally scalable compute layer while maintaining one consistent shared filesystem.

Study Guide reference: Core Infrastructure Deep Dive — ECS storage patterns, File Storage NAS, shared storage, and stateless application architecture.

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.

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

Function Compute with EventBridge provides the lowest-management architecture among the choices. Function Compute is a fully managed, event-driven compute platform: Alibaba Cloud provisions and scales the required execution infrastructure automatically, and billing is based on configured resources and execution duration. This removes the operational burden of maintaining ECS instances or an ACK cluster.

The stated execution time of up to one hour is supported. Current Function Compute documentation permits individual function executions of up to 24 hours, so the job duration does not require a container cluster merely because it exceeds traditional short-function runtimes.

EventBridge supports recurring time-triggered events using fixed schedules or cron expressions and is suitable for scheduled batch-processing workflows. Function Compute also integrates directly with EventBridge-based cloud-product event triggers.

Options A and C introduce Kubernetes control and workload-management complexity that is unnecessary for a single scheduled processing job. Option B is less precise because Serverless Workflow provides orchestration rather than being required to perform the actual computation.

Therefore, EventBridge schedules the daily invocation and Function Compute performs the OSS-backed processing without persistent infrastructure.

Study Guide reference: Delivering Services on Alibaba Cloud; serverless architecture and event-driven application delivery.

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

The strongest architecture for an existing e-commerce platform experiencing predictable but substantial traffic spikes is OSS/CDN + ALB + Auto Scaling. Auto Scaling is specifically designed to increase ECS capacity when traffic or resource utilization rises and remove unnecessary instances after demand subsides. Alibaba Cloud documents this as a core mechanism for handling traffic spikes while avoiding permanent over-provisioning.

ALB complements Auto Scaling by distributing requests across healthy ECS backend instances. As scaling creates additional instances, they can be automatically added to the ALB server group, allowing traffic to use the enlarged compute pool immediately.

Static images and videos should be moved to OSS and accelerated through CDN. CDN caches static resources on geographically distributed edge nodes, substantially reducing requests reaching the ECS application tier and lowering origin bandwidth and processing load during sales events.

Function Compute is highly elastic, but introducing it merely to supplement an existing server-based application normally requires application restructuring. It is therefore less directly applicable than the three mechanisms specifically designed to scale and offload the existing architecture.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — Auto Scaling, ALB, CDN offloading, and elastic ECS architecture.

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

Simple Log Service (SLS) is a managed log-ingestion, storage, query, analysis, and visualization service, making it the most operationally efficient front-end for this telemetry workload. It eliminates the requirement to provision and manage ECS-based collectors or a separate search cluster simply to ingest and analyze log records.

For longer-term retention, Alibaba Cloud supports automatically shipping SLS data to OSS. This creates a clean hot-to-cold architecture: maintain recent data in SLS for interactive analysis and export older data to OSS for economical retention.

OSS lifecycle management can then automatically transition aging objects to lower-cost storage classes such as Archive. Lifecycle rules are explicitly designed to automate storage-class transitions based on object age, eliminating manual archival administration.

Option A requires additional Elasticsearch retention administration. Option B requires managing ECS infrastructure even though the question explicitly prioritizes reduced operational management. Option D adds Kafka unnecessarily and still specifies manual archival, directly conflicting with the requirement to minimize operational effort.

Thus, SLS for managed ingestion and recent analysis combined with SLS-to-OSS shipping and OSS lifecycle transitions provides the strongest serverless/managed retention architecture.

Study Guide reference: Core Infrastructure Deep Dive; Core Storage Infrastructure; operationally efficient log and data-storage architecture.

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

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.