Free Alibaba Cloud Certified Professional: Cloud Architect Practice Questions

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.

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

Option B reduces interference between transaction processing and read-heavy workloads inside PolarD

B.  

Option D provides stronger isolation for computationally expensive analytics. DTS can continuously synchronize PolarDB for MySQL data into MaxCompute using initial full synchronization followed by ongoing incremental change capture. Analysts can then execute large-scale analytical workloads against MaxCompute without placing those queries on the production transactional database.

Running queries on ECS does not inherently remove load from PolarDB because the SQL operations would still execute against the database. Introducing MongoDB merely to execute analytical queries creates a second database technology without an appropriate replication or analytical architecture.

Together, PolarDB read/write splitting optimizes operational read traffic while DTS-to-MaxCompute isolates heavyweight analytical processing, producing an effective HTAP-style separation of concerns.

Study Guide reference: Core Infrastructure Deep Dive — PolarDB, read/write splitting, DTS, MaxCompute, and analytical workload offloading.

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

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 core problem is durability during transient processing or network failures. A topic provides publish/subscribe notification delivery, but placing an SMQ queue behind the topic creates a persistent buffer between the notification producer and the Function Compute consumer. Alibaba Cloud supports subscribing a queue to an SMQ topic so that every message published to the topic is copied into the queue and retained for consumption.

Function Compute should then process records from the queue. Queue semantics provide the required failure recovery: after a consumer receives a message, it becomes temporarily invisible. The consumer deletes the message only after successful processing. If processing fails—for example because of a temporary connectivity problem—the message is not deleted and becomes visible again after the visibility timeout, allowing another processing attempt.

Function Compute also supports SMQ queue triggers with configurable retries, fault-tolerance behavior, and dead-letter handling, which can further strengthen this architecture.

Increasing memory does not fix network reliability, and multi-region deployment alone does not guarantee message persistence. A durable queue therefore prevents transient failures from silently losing ingestion work.

Study Guide reference: Core Infrastructure Deep Dive — Simple Message Queue, Function Compute, durable asynchronous processing, retries, and decoupled event-driven 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.