Alibaba Cloud CAP-C01 Alibaba Cloud Certified Professional: Cloud Architect Exam Practice Test

The workload is an excellent candidate for preemptible, currently called spot, ECS capacity because it is short-lived, batch-oriented, horizontally scalable, and explicitly tolerant of interruption. The question states that if an instance fails, another instance can reprocess the job. That removes the main architectural objection to using interruptible compute.

Alibaba Cloud describes ECS spot instances as unused ECS capacity offered at substantially reduced prices compared with standard pay-as-you-go instances. The documented recommended scenarios include short-term tasks, data analytics, and applications that are highly fault tolerant and able to tolerate interruption.

Savings Plans and reserved-instance-style commitments can reduce costs for predictable long-term baseline consumption, but this workload runs only at two scheduled times each day. Purchasing committed capacity for a sporadic workload can leave paid capacity economically underutilized. Higher-specification pay-as-you-go instances also do not inherently minimize compute cost.

Using a launch template with preemptible/spot ECS instances allows Auto Scaling to add inexpensive compute when the batch workload requires it, while the application ' s retry mechanism handles interruptions.

Study Guide reference: Core Compute Infrastructure Deep Dive; Scalable Architecture on Alibaba Cloud; cost optimization for elastic compute.

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

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.

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

OSS versioning is specifically intended to protect objects from unintended deletions and overwrites. When versioning is enabled, OSS retains historical versions of an object. A normal delete operation creates a delete marker instead of permanently destroying all existing versions, allowing an administrator to restore a previous version when required.

Alibaba Cloud explicitly recommends versioning as a protection mechanism against accidental deletion or overwriting. Its current documentation states that, after versioning is enabled, accidentally deleted or overwritten content remains available as historical versions that can subsequently be restored.

Encryption protects confidentiality of stored data but does not provide logical deletion recovery. A private bucket ACL reduces unauthorized access but does not stop an authorized administrator or application from deleting an object accidentally. Lifecycle rules automate transitions or deletion according to defined policies; improperly configured lifecycle rules can themselves delete data, so they are not the primary protection mechanism requested here.

For particularly critical workloads, versioning can be supplemented with backup or carefully designed cross-region replication, but among the four choices, enabling OSS versioning directly addresses accidental deletion and provides recovery capability.

Study Guide reference: Core Storage Infrastructure Deep Dive; data durability, protection, and OSS object-management mechanisms.

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

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.

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

Time Series Database is specifically designed for timestamped telemetry generated by IoT devices, monitoring systems, and industrial equipment. Alibaba Cloud identifies IoT device monitoring as a core TSDB scenario, including continuously collecting, storing, analyzing, and querying device-status and business-event data in real time.

ApsaraMQ for Kafka provides the high-throughput ingestion and buffering layer. It is a managed distributed Kafka platform intended for real-time data pipelines, monitoring-data aggregation, log collection, streaming processing, and large-scale analytics. Its partitioned distributed architecture lets producers ingest very large event volumes while downstream consumers process the streams independently.

Function Compute supplies elastic event processing without persistent compute servers. Alibaba Cloud supports ApsaraMQ for Kafka triggers that invoke Function Compute automatically whenever new records arrive in Kafka topics. This enables functions to perform transformations, filtering, enrichment, alert generation, or routing in near real time.

EMR is valuable for Hadoop/Spark-style batch analytics, but the question specifically emphasizes low-latency real-time ingestion and analysis. It therefore does not replace the streaming components selected above.

Study Guide reference: Core Infrastructure Deep Dive — IoT telemetry, TSDB, ApsaraMQ for Kafka, Function Compute, and real-time streaming architectures.

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

Alibaba Cloud Cloud Firewall is the purpose-built managed network-security service for centralized traffic inspection, filtering, access control, and threat prevention. It protects multiple network boundaries, including traffic between cloud workloads and the Internet as well as east-west traffic involving VPC environments.

For Internet-facing assets, Cloud Firewall can inspect inbound and outbound traffic and apply access-control policies, DPI-based analysis, intrusion-prevention rules, and threat intelligence without requiring an organization to deploy and maintain a self-managed firewall appliance.

For private architectures, a VPC Firewall can inspect and control traffic traversing VPC boundaries through CEN or Express Connect. Access-control policies determine which traffic is permitted or blocked.

Simple Log Service can analyze network logs but does not itself enforce inline traffic filtering. Traffic Mirroring copies traffic to another inspection system and therefore requires additional tooling. Security Center focuses primarily on workload security posture, vulnerability management, malware protection, and host security rather than functioning as the VPC ' s inline network firewall.

Cloud Firewall therefore most closely reproduces the company ' s former inspection-and-filtering architecture as a fully managed cloud-native service.

Study Guide reference: Securing Workloads on Alibaba Cloud — Cloud Firewall, network inspection, access control, IPS, and VPC security.

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

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.

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.

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

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.

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

Server Load Balancer SSL termination and Certificate Management Service provide the most direct combination for centralized TLS protection and certificate lifecycle management.

With SSL/TLS termination on the load-balancing layer, clients establish encrypted HTTPS or SSL connections to the SLB service. Encryption processing is performed centrally rather than requiring every backend instance to independently process incoming TLS handshakes. This simplifies the backend architecture and centralizes certificate configuration.

Certificate Management Service is specifically designed for issuing, importing, storing, monitoring, deploying, and renewing SSL certificates. Alibaba Cloud currently supports centralized certificate deployment to services including SLB, CDN, WAF, ECS, and other supported resources.

The integration is particularly strong because Alibaba Cloud ' s load-balancing services use certificates managed through Certificate Management Service. For example, SSL listeners require appropriate server certificates for encrypted client connections.

WAF adds web-application threat protection but is not primarily a certificate lifecycle automation solution. CDN with HTTPS is valuable for accelerated content delivery but is not required simply to centralize TLS termination. KMS protects cryptographic keys and secrets but does not replace SSL certificate deployment and lifecycle management.

Therefore, SLB plus Certificate Management Service provides encrypted access and centralized certificate administration with the lowest operational burden.

Study Guide reference: Securing Workloads on Alibaba Cloud — TLS, certificate lifecycle management, SSL termination, and secure load balancing.

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

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 ECS security group must allow inbound HTTPS traffic. For an inbound security-group rule, the Internet clients are the source, so the correct rule permits TCP destination port 443 from source 0.0.0.0/0. This makes Option C correct. Alibaba Cloud security groups are stateful, which means response traffic belonging to an allowed connection is automatically permitted and does not require a matching outbound security-group rule.

Network ACLs behave differently. Alibaba Cloud VPC network ACLs are stateless. If the ACL permits an inbound HTTPS request but does not permit the corresponding return packet, the TCP session cannot operate correctly. The inbound ACL therefore needs TCP 443 from Internet clients, while the outbound ACL must permit return traffic to client ephemeral destination ports. Alibaba Cloud explicitly recommends 1024–65535 when all client ephemeral-port implementations must be supported.

Option D permits only the incoming side of the ACL and therefore fails because response packets remain blocked. Option E incorrectly assumes that outbound server responses use destination port 443; the server ' s source port is 443, but the destination is the client ' s ephemeral port.

Study Guide reference: Securing Workloads on Alibaba Cloud — stateful Security Groups, stateless network ACLs, HTTPS exposure, and ephemeral ports.

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

OSS provides region-specific internal endpoints specifically for private access from Alibaba Cloud compute resources. When an ECS instance and an OSS bucket reside in the same region, the ECS instance can access the bucket using an internal OSS domain such as an oss- < region > -internal.aliyuncs.com endpoint. Traffic remains on Alibaba Cloud ' s internal network instead of traversing the public Internet.

This directly satisfies the security requirement without adding unnecessary networking components. The ECS instance does not require an EIP, NAT Gateway, or Internet connectivity for the OSS data path.

VPN Gateway is intended primarily for connecting VPCs to on-premises networks or other private networks; it is unnecessary for same-region OSS access. PrivateLink has legitimate private-service connectivity use cases, but the presence of a native OSS internal endpoint makes it unnecessary here. A VPC gateway endpoint may be relevant to certain Alibaba Cloud service integrations, but it is not required for this straightforward same-region ECS-to-OSS architecture.

The important exam design principle is to prefer a service ' s native private endpoint when one exists and the workload is already located inside the corresponding Alibaba Cloud region.

Study Guide reference: Building Enterprise-grade Networks on Alibaba Cloud — VPC private connectivity and OSS internal endpoints.

A multi-zone deployment within the same region is the standard architecture for surviving the complete failure of one availability zone. Alibaba Cloud zones within a region are physically isolated for fault tolerance while maintaining high-speed internal network connectivity. Alibaba Cloud explicitly recommends deploying resources across different zones when higher disaster-recovery capability is required.

For an application tier, multiple ECS instances should be placed in separate zones and normally fronted by a multi-zone ALB or another suitable load-balancing service. Health checks ensure that traffic is no longer directed to unavailable instances, allowing surviving instances in another zone to continue serving requests. Alibaba Cloud ' s current high-availability guidance specifically describes multi-zone ECS and load-balancer deployments as the architecture for resilience against data-center or zone failures.

Option A remains vulnerable because all compute resources share the same zone failure domain. Option C retains a single compute point of failure regardless of storage performance. Option D can protect against an entire regional disaster, but it adds substantially greater networking, data synchronization, routing, and operational complexity than is necessary for the stated requirement of surviving one zone failure.

Therefore, distributing ECS instances across multiple zones within one region is the correct high-availability strategy.

Study Guide reference: Highly Available Architecture on Alibaba Cloud; Core Compute Infrastructure; multi-zone disaster recovery.

Tair, Auto Scaling, and ALB directly address the three core runtime requirements: session performance, elastic capacity, and distributed traffic handling.

Tair provides an in-memory Redis-compatible data tier that is appropriate for high-frequency session information. Keeping session state outside individual ECS game servers allows requests to be handled by different backend instances without losing player session information and avoids disk/database latency on critical session lookups.

Auto Scaling directly satisfies the requirement to react automatically to sudden player surges. Alibaba Cloud Auto Scaling can monitor metrics such as CPU utilization and automatically add ECS instances when capacity thresholds are exceeded, then remove excess capacity as demand decreases.

ALB distributes client requests across the resulting game-server fleet, performs health checks, and avoids overloading individual ECS instances.

CDN is highly valuable for downloading static assets such as textures, patches, images, and game packages because those objects can be cached at edge POPs. However, standard CDN does not provide the core dynamic scaling mechanism for real-time game sessions. Given that exactly three selections are required, Auto Scaling is essential because the question explicitly requires automatic scaling during player surges.

Study Guide reference: Building Highly Available, Performant Cloud Architecture — Tair, ALB, Auto Scaling, low-latency session architecture, and elastic gaming workloads.

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