Free Practice Questions for Alibaba Cloud CAP-C01 Exam

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.

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

File Storage NAS is Alibaba Cloud ' s managed shared filesystem service and is the correct storage family for workloads that require standard filesystem semantics and mounting by many clients. NAS supports NFS and SMB-based access, and a mount target acts as the private VPC endpoint through which clients access a NAS filesystem. General-purpose NAS currently supports up to two mount targets, and a mount target can be concurrently accessed by large numbers of compute nodes.

Alibaba Cloud also explicitly supports accessing NAS from an on-premises data center through VPN Gateway. This means the same private network architecture can accommodate cloud-hosted ECS clients and systems connected through the enterprise VPN.

OSS provides object semantics rather than a native shared NFS/SMB filesystem. EBS is block storage attached to compute instances and would require Priya to build and maintain custom file-server proxies, reducing availability and increasing administration.

Among the offered answers, multiple NAS mount points best align with the requirement for scalable managed file storage and resilient access paths while preserving standard filesystem protocols.

Study Guide reference: Core Infrastructure Deep Dive — File Storage NAS, NFS/SMB, mount targets, and hybrid-cloud storage.

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.

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

ROS Stack Groups are specifically designed for centrally deploying a common Resource Orchestration Service template across multiple Alibaba Cloud accounts and regions. This makes option D the architecture that directly addresses both dimensions of the requirement: multi-account governance and multi-region infrastructure-as-code deployment.

Alibaba Cloud documentation states that stack instances belonging to a stack group can deploy stacks into destination accounts and different regions. With Resource Directory integration and service-managed permissions, trusted access can be enabled so that stack groups are operated by a management account or delegated administrator while deployments occur in organization member accounts.

Nested stacks are primarily a template-composition mechanism; they do not constitute centralized multi-account deployment orchestration. Manually combining ordinary ROS templates and RAM policies could technically enable cross-account operations, but it recreates functionality that Stack Groups provide natively and increases operational overhead. Resource Directory and Cloud Governance alone also do not replace the actual multi-account, multi-region stack deployment mechanism.

Therefore, Resource Directory establishes the organizational account structure while ROS Stack Groups provide repeatable infrastructure deployment across those accounts and target regions.

Study Guide reference: Core Infrastructure Deep Dive; Resource Orchestration Service, multi-account governance, and repeatable cloud architecture.

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

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.

Data Management Service is specifically designed to centralize database administration, authorization, and governance. Its permission model provides fine-grained control over instances, databases, tables, columns, rows, and sensitive data. Administrators can control logon, query, export, and change privileges while maintaining centralized governance rather than manually coordinating several independent services.

DMS is also appropriate where the organization needs auditable database access. Alibaba Cloud explicitly describes DMS authorization scenarios that include controlling RDS access and auditing employee data access.

RAM controls permissions to Alibaba Cloud resources and APIs, but combining RAM with ActionTrail would require multiple mechanisms and would not provide DMS ' s database-object-level permission model. An RDS IP whitelist is useful as a network access restriction but cannot express granular user permissions or provide centralized database governance. WAF protects HTTP/HTTPS applications and is not the appropriate control plane for direct RDS database authorization.

DMS therefore provides the required access control and audit functionality with the lowest operational complexity by consolidating database security administration into a purpose-built managed service.

Study Guide reference: Securing Workloads on Alibaba Cloud — DMS access control, database governance, RDS security, and auditing.

Option C provides the lowest-change migration path for the application tier. Rehosting the existing Windows workload on Windows Server ECS instances preserves its operating-system environment while distributing instances across availability zones improves resilience against zone-level infrastructure failures.

For the database tier, Option A provides the stronger managed architecture. Alibaba Cloud explicitly supports using DTS to migrate self-managed Oracle databases to PolarDB for PostgreSQL (Compatible with Oracle), including schema, full-data, and incremental-data migration for minimal migration downtime.

PolarDB ' s Oracle-compatible edition is specifically engineered to run Oracle workloads with minimal application modification. It supports Oracle-compatible data types, SQL constructs, PL/SQL features, OCI connectivity, packages, sequences, synonyms, and related functionality.

It also provides built-in high availability: failures are detected automatically and workloads can fail over to healthy nodes. This provides a more complete managed availability architecture than simply deploying independent self-managed Oracle servers across zones, which would additionally require Oracle-level replication/failover configuration.

Options B and D require substantial application refactoring and therefore conflict with the explicit requirement to minimize development changes.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — workload migration, ECS multi-zone design, DTS, and PolarDB Oracle compatibility.

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

Option A offers the strongest combination of resilience, predictable baseline capacity, flexibility, and reduced cost. Nine standard pay-as-you-go ECS instances are spread evenly across three zones and can support the scheduled workloads that have strict SLA requirements. The remaining three instances use lower-cost preemptible/spot capacity for user jobs that can tolerate interruption or delay.

Alibaba Cloud describes spot instances as offering the same compute performance as ordinary pay-as-you-go ECS but at substantially lower prices, with the trade-off that capacity can be reclaimed. This makes spot capacity appropriate for interruption-tolerant workloads but inappropriate as the sole capacity supporting strict SLAs.

A Savings Plan discounts eligible pay-as-you-go ECS usage while preserving significantly greater flexibility than traditional reserved-instance matching. Current Alibaba Cloud documentation states that Savings Plans apply discounts to pay-as-you-go usage and can offer flexibility across instance configurations; they do involve a one- or three-year hourly spend commitment, but they do not provision or reserve fixed ECS capacity.

Options C and D concentrate too much reliable capacity into fewer zones or place excessive workload on interruptible capacity. Option A therefore provides the best workload-tiering and multi-zone design among the available choices.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — multi-zone ECS, workload resilience, Savings Plans, and spot instances.

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

Option A refers to PolarDB Global Database Network (GDN), Alibaba Cloud ' s architecture for connecting PolarDB clusters across regions. A GDN contains a primary cluster and secondary regional clusters. Data changes are continuously replicated, local reads can be served by regional clusters, and write operations are routed to the primary cluster. Maintaining a single authoritative write path is particularly important for reservation transactions where concurrent booking operations must be controlled consistently.

Option C provides resilient application capacity by deploying ECS application servers in multiple regions and using ALB within each regional deployment to distribute requests among healthy instances. In a complete production implementation, a global routing mechanism such as DNS traffic management or Global Accelerator would normally direct users between those regional application stacks.

Function Compute is suitable for payment-gateway integrations because payment callbacks and API interactions are event-driven or request-driven workloads. Function Compute can be exposed securely through API Gateway, which provides routing, authentication, traffic control, and API management without persistent integration servers.

OSS versioning is useful for protecting stored objects but does not supply the transactional database, regional application availability, or payment-processing functionality required here.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — multi-region PolarDB, GDN, regional application tiers, ALB, and serverless integration.

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