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.

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

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.

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

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.

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

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.

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

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.