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

Data Transmission Service and OSS lifecycle management address the two distinct requirements: continuously replicated operational data and economical long-term retention.

DTS provides real-time data synchronization by continuously capturing changes from a source database and applying them to a destination. Alibaba Cloud identifies active geo-redundancy, disaster recovery, cross-region replication, and real-time data synchronization as standard DTS scenarios. Maintaining a secondary synchronized dataset in another failure domain therefore provides substantially better recovery characteristics than relying only on periodic backups.

Historical data has a different access pattern. Regulatory medical records can remain necessary for years while being rarely retrieved. OSS lifecycle policies can automatically transition aging objects from frequently accessed storage into lower-cost storage classes such as Archive. Alibaba Cloud specifically describes lifecycle policies for medical records and other compliance datasets that become cold over time.

Option B provides backup protection but does not directly provide the requested continuous replication architecture and unnecessarily introduces self-managed databases on ECS. DMS simplifies database administration but is not a data-replication or archival-storage mechanism.

Consequently, DTS supplies the live replication/fault-tolerance layer, while OSS lifecycle policies supply automated and cost-efficient long-term retention.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — DTS replication, disaster recovery, OSS lifecycle management, and compliance-oriented storage.

Serverless App Engine is the strongest fit because it provides an application-oriented serverless platform specifically intended for hosting containerized and microservice applications without requiring the organization to administer Kubernetes clusters or ECS infrastructure. SAE can deploy applications directly from container images, including images stored in Alibaba Cloud Container Registry, and automatically manages provisioning, application lifecycle, scaling, monitoring, and underlying resources.

SAE namespaces also provide logical isolation for development, testing, and production environments. This directly addresses the requirement for separate production and testing deployments while avoiding the overhead of maintaining separate ACK clusters.

SAE integrates with Application Load Balancer for Layer 7 ingress and routing. ALB can expose SAE applications and route traffic to the appropriate backend application instances.

ACK Serverless removes worker-node management but still introduces Kubernetes objects and cluster administration. ACK Managed requires even greater cluster administration. Function Compute is optimized for functions and event-driven processing rather than straightforward migration of a multi-service container application.

Study Guide reference: Core Infrastructure Deep Dive — serverless compute, SAE, containerized applications, microservices, and application scaling.

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

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.

Tair is the appropriate architecture for a frequently changing game leaderboard because Redis-compatible sorted data structures are optimized for high-throughput score updates and ranking operations. Instead of repeatedly executing expensive aggregation and sorting queries against the relational database, the application can maintain player scores in Tair and retrieve the highest-ranked members directly.

Alibaba Cloud specifically documents leaderboard implementations based on Tair ' s sorted-set capabilities. Tair ' s enhanced exZset functionality supports scalable ranking use cases and can distribute large leaderboards across multiple internal structures while preserving rank calculation.

This also protects RDS from high-frequency scoreboard queries. RDS remains the durable transactional database, while Tair operates as the low-latency serving and ranking layer for frequently accessed score data.

CDN caching is unsuitable because the leaderboard changes continually and requires near-real-time freshness. A second relational PostgreSQL database would duplicate database infrastructure without providing the specialized in-memory ranking semantics required. An RDS read replica can reduce pressure on the primary database, but calculating and sorting rankings through SQL for every refresh remains less efficient than maintaining rankings directly in an in-memory sorted structure.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — Tair, caching, low-latency architectures, and database performance optimization.

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

Express Connect combined with Cloud Enterprise Network Transit Routers provides the appropriate enterprise hybrid-network architecture. Express Connect establishes a dedicated private circuit from the on-premises data center to Alibaba Cloud, providing lower latency, predictable performance, high bandwidth, and reduced exposure compared with Internet-based VPN connectivity.

The Express Connect circuit terminates through a Virtual Border Router. That VBR can be attached to CEN, where Transit Routers provide hub-and-spoke connectivity to multiple VPCs instead of requiring separate point-to-point connections for every VPC. Transit Routers can connect VPCs, VBRs, VPN attachments, and inter-region Transit Routers, enabling centralized routing across a geographically distributed enterprise network.

Alibaba Cloud also supports connecting an on-premises VBR and multiple VPCs to a Transit Router so that all attached networks communicate over private connectivity. Cross-region CEN connections then extend the architecture to VPCs in additional regions.

VPN Gateway relies on Internet-based encrypted tunnels and would require more tunnel management at scale. NAT Gateway performs address translation and does not provide private hybrid interconnection. Apsara Stack is an on-premises cloud platform rather than the required connectivity service.

Study Guide reference: Building Enterprise-grade Networks on Alibaba Cloud — Express Connect, CEN, Transit Router, hybrid networking, and cross-region connectivity.

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