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

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.

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

Alibaba Cloud CDN is specifically designed to accelerate content delivery by distributing and caching content at geographically distributed points of presence. When a user requests an accelerated resource, CDN DNS scheduling assigns an appropriate PoP. If the resource is cached there, the PoP returns it directly without requiring a round trip to the origin infrastructure. Alibaba Cloud documentation explicitly states that static resources are cached on the nearest PoP to reduce latency and improve access efficiency.

This directly satisfies both key requirements in the question: caching static content and directing users toward edge infrastructure close to their locations. If content is not cached or has expired, the CDN PoP performs an origin fetch and then serves the resource.

GTM can perform DNS-based geographical or latency routing among application endpoints and regions, but it is not itself a distributed static-content caching service. Express Connect provides private dedicated connectivity between enterprise/on-premises networks and Alibaba Cloud. SLB distributes traffic among backend servers but does not provide a worldwide edge caching network.

Therefore, Alibaba Cloud CDN is the only listed service that simultaneously implements PoP-based edge delivery and static-content caching.

Study Guide reference: Delivering Content on Alibaba Cloud; content acceleration and global application-delivery architecture.

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

OSS, E-MapReduce, and MaxCompute collectively provide the strongest large-scale analytics architecture among the listed services.

OSS supplies the scalable data-lake storage layer. Alibaba Cloud describes OSS-based data lakes as capable of retaining structured, semi-structured, and unstructured datasets at very large scale while decoupling storage capacity from compute resources. OSS storage can scale independently into exabyte-scale environments.

E-MapReduce provides managed big-data processing based on ecosystems such as Hadoop and Spark and integrates directly with OSS. EMR DataLake configurations support Spark and Hive for batch workloads and Presto/Trino for interactive SQL analysis, making EMR highly appropriate for workloads requiring both scheduled processing and ad-hoc querying.

MaxCompute supplies a massively scalable managed data-warehouse and analytical processing layer. Alibaba Cloud also supports architectures where MaxCompute processes structured analytical datasets while OSS provides the underlying flexible data-lake storage.

PolarDB is an operational relational database and is not intended to act as the primary petabyte-scale data-lake processing platform. Elasticsearch is valuable for search and log analytics but does not replace the combination of OSS, EMR, and MaxCompute for generalized big-data processing.

Study Guide reference: Core Infrastructure Deep Dive — OSS data lakes, EMR, MaxCompute, distributed analytics, batch processing, and interactive query architectures.

CDN should form the content-delivery layer for cacheable video assets. Alibaba Cloud CDN distributes content to geographically dispersed edge nodes so viewers retrieve cached objects from nearby POPs rather than repeatedly connecting to a distant origin. Alibaba Cloud explicitly supports video-oriented CDN acceleration and edge delivery, reducing both end-user latency and origin bandwidth demand.

Auto Scaling addresses peak-time compute demand. It monitors workload conditions and automatically increases ECS capacity during traffic spikes, then scales resources back when traffic decreases. Alibaba Cloud specifically identifies streaming platforms with unpredictable demand as a typical Auto Scaling scenario.

Global Accelerator complements CDN and Auto Scaling where viewers or application endpoints are separated by long-distance or cross-border networks. GA routes traffic through Alibaba Cloud ' s optimized global BGP network, reducing latency, jitter, and packet loss. Alibaba documentation explicitly identifies video streaming as a latency-sensitive scenario that benefits from this architecture.

Tair can improve authentication or session performance, but it does not directly address video delivery quality or regional network performance. Therefore, CDN + Auto Scaling + Global Accelerator most directly satisfies the streaming requirement.

Study Guide reference: Delivering Services and Content on Alibaba Cloud — CDN, Global Accelerator, Auto Scaling, video delivery, and global traffic optimization.

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

The requirements explicitly identify two separate environments: a production ACK cluster using stable pay-as-you-go ECS capacity and a dedicated development cluster that is used only intermittently. Option D satisfies both requirements while preserving ACK-managed node-pool operations.

For the development cluster, preemptible instances—now generally described as spot instances in current Alibaba Cloud documentation—are appropriate because the workload is temporary, interruption-tolerant, and cost-sensitive. Alibaba Cloud states that spot capacity can reduce compute costs substantially compared with ordinary pay-as-you-go instances. ACK node pools can use spot instances and can automatically perform scaling and replacement operations.

The production cluster remains on pay-as-you-go nodes, avoiding the reclamation risk associated with spot capacity. A separate managed development cluster also preserves workload isolation.

Option A does not provide the required second development cluster and imposes subscription commitment. Option B requires Eric to maintain an external Auto Scaling and bootstrap mechanism, contradicting the desire for ACK to manage nodes. Option C again describes only one cluster and fails to retain the required production environment.

Study Guide reference: Core Infrastructure Deep Dive — ACK managed clusters, node pools, spot/preemptible ECS, and cloud cost optimization.