H13-811_V3.5 Exam Dumps - Huawei HCIA-Cloud Service Questions and Answers

Option A is false because deleting historical object versions is not required before versioning can be suspended. Huawei Cloud states that once versioning has been enabled, it cannot revert to the original Disabled state, but it can be suspended. Existing historical versions remain stored in OBS after suspension and may be manually deleted later only if they are no longer required.

Option B is correct. When versioning is enabled, OBS automatically assigns a unique version ID to newly uploaded versions. Objects with identical names are retained as separate object versions distinguished by those IDs.

Option C is also correct. Huawei explicitly supports configuration of OBS versioning through the OBS Console, APIs, and SDKs.

Option D is correct because versioning is disabled by default for newly created buckets. It must be explicitly enabled if the customer wants multiple versions retained instead of allowing a newly uploaded namesake object to replace the current object.

Therefore, A incorrectly adds a prerequisite that Huawei does not impose for suspending versioning.

Reference topics: OBS Versioning; Version IDs; Suspending Versioning; Historical Object Versions.

A → 2

B → 1

C → 3

The mappings follow Huawei Cloud's system-defined authorization model for Bare Metal Server. BMS CommonOperations provides operational permissions required for routine server administration. Huawei explicitly identifies starting, stopping, restarting, and querying BMS instances as operations permitted under the common-operations permission set. It therefore maps to permission 2.

BMS FullAccess represents administrator-level access to the BMS service. It permits operations that CommonOperations and ReadOnlyAccess cannot perform, including higher-impact lifecycle and configuration operations. Huawei Cloud's BMS permission matrix shows that reinstalling a BMS operating system is supported by FullAccess but not by CommonOperations or ReadOnlyAccess. Consequently, BMS FullAccess maps to permission 1.

BMS ReadOnlyAccess is intended for users who need visibility into BMS resources without authority to modify them. It permits users to query and view BMS information, including server lists and instance details, but does not authorize lifecycle actions such as starting, stopping, restarting, or reinstalling an operating system. It therefore maps to permission 3.

The verified mapping is CommonOperations → routine operations; FullAccess → OS reinstallation; ReadOnlyAccess → viewing BMS information .

Reference topics: Bare Metal Server Permissions; IAM Authorization for BMS; System-Defined BMS Policies.

Option D is incorrect . Huawei Cloud's official RDS for PostgreSQL constraints specify that a maximum of five read replicas can be created for one DB instance , not 15. Huawei's current read-replica documentation reiterates the same five-replica limit. The “15 read replicas” characteristic is associated with other Huawei database architectures, such as TaurusDB/GaussDB-related scaling designs, and must not be transferred to standard RDS for PostgreSQL.

Option C is directly supported by Huawei documentation. RDS for PostgreSQL is an object-relational database designed for complex OLTP and supports NoSQL and GIS data types. Huawei explicitly identifies websites, location-based applications, and complex data object processing as representative workloads.

Option B is also valid. Huawei Cloud provides real-time status and performance monitoring for RDS instances, exposing database-related metrics and allowing alarms to be configured for operational monitoring.

Option A reflects the managed-service security architecture: RDS provides controls involving network isolation, security groups, SSL, account authorization, backups, and other mechanisms to protect databases and user data.

The numerical scaling claim in D therefore makes it decisively incorrect.

Reference topics: RDS for PostgreSQL; Read Replicas; Database Monitoring; PostgreSQL Application Scenarios; RDS Security.

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

Statement C is false because it gives the definition of a shared image rather than a private image. Huawei Cloud defines a private image as an image available to the user who created it. Such an image can contain an operating system, pre-installed public applications, service data, and the user's own applications. It is commonly used to rapidly create identically configured ECS instances.

A shared image , conversely, is a private image that another Huawei Cloud user has explicitly shared with the recipient. Therefore, saying that “a private image is shared by other users” reverses these concepts.

Option A is correct. Huawei describes Marketplace images as third-party images containing an operating system, application environment, and software already installed, allowing rapid deployment of application environments.

Option B is also correct: public images are standardized system images provided by the cloud platform and made available broadly to customers.

Option D conforms to Huawei IMS sharing restrictions. Huawei Cloud specifies that encrypted images cannot be directly shared with other tenants; an encrypted image must first be replicated as an unencrypted image if sharing is required.

Thus, C is the single incorrect statement .

Reference topics: Image Management Service; Public Images; Private Images; Shared Images; Marketplace Images; Image Encryption.

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

Option A is incorrect because it confuses full-access permissions with a read-only role. In Huawei Cloud IAM, a permission whose name contains FullAccess normally represents full or administrator-level permissions for the corresponding service. For example, IAMFullAccess provides full permissions for IAM operations rather than read-only access.

Huawei Cloud separately defines Tenant Guest as providing read-only permissions for cloud services other than IAM. This distinction is important in HCIA IAM authorization concepts: FullAccess and ReadOnlyAccess represent materially different privilege levels.

The remaining statements correctly describe Huawei Cloud authorization. IAM supports roles and policies as authorization mechanisms, with policies providing more fine-grained control. User groups provide an efficient way to authorize multiple IAM users: an administrator assigns permissions to a group and then places users in that group, after which the users inherit the group's permissions. Finally, an IAM user can perform only the cloud-service operations allowed by the permissions granted to that identity.

Thus, option A incorrectly assigns the behavior of a read-only permission model to FullAccess and is the required answer.

Reference topics: IAM Permissions; Roles and Policies; User Groups; FullAccess; Tenant Guest.

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

All four categories form part of Huawei Cloud's layered security architecture. Network security includes controls and services designed to protect network boundaries and traffic, such as Anti-DDoS, Advanced Anti-DDoS, VPC security controls, firewalls, and network isolation. Huawei Cloud describes network security as a core component of its full-stack cloud defense model.

Application security protects web applications and application-layer traffic. Representative Huawei Cloud services include Web Application Firewall, which detects and blocks HTTP/HTTPS attacks, and application vulnerability/security capabilities.

Computing security covers server and workload protection. Host Security Service protects ECS and other server workloads through vulnerability management, intrusion detection, account-security controls, malware detection, and web tamper protection. Security-management capabilities such as Cloud Bastion Host and centralized security operations provide access management, authentication, authorization, auditing, and operational control.

Finally, data security encompasses encryption, database protection, identity/access control, sensitive-data protection, and lifecycle safeguards. Huawei's security architecture explicitly identifies protection of confidentiality, integrity, availability, durability, and traceability as data-security objectives.

Therefore, A, B, C, and D are all included .

Reference topics: Huawei Cloud Security Architecture; Network Security; Application Security; Compute Security; Security Management; Data Security.

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

Option A specifically describes Huawei Cloud's dynamic resource adjustment mode . In Huawei Auto Scaling, dynamic scaling uses an alarm policy that evaluates real-time monitoring metrics such as CPU utilization. When the configured alarm condition is reached, AS automatically performs a scaling action to increase or decrease resources so that capacity follows unpredictable workload changes.

Option B is incorrect because triggering an AS policy does not automatically redefine the configured maximum number of instances . The maximum is an upper boundary for the AS group. A scaling policy changes the expected number of instances, adds or removes instances, or sets the instance count to a configured value while remaining within the minimum and maximum boundaries.

Option C correctly describes planned scaling , but the question specifically asks about dynamic resource scaling. Huawei classifies scheduled and periodic policies as planned adjustment mechanisms suitable for workloads that change predictably according to a schedule.

Option D is incorrect because alarm-triggered scaling is subject to a cooldown period . During that period, Huawei Cloud rejects additional scaling requests generated by alarm policies to prevent repeated unnecessary scaling operations.

Therefore, for dynamic resource scaling, A is the correct answer .

Reference topics: Auto Scaling; Dynamic Resource Adjustment; Alarm Policies; Planned Scaling; Cooldown Period.

Statement C is incorrect because container images do not require a private registry. Huawei Cloud container services can consume images from multiple sources, including Huawei Cloud SoftWare Repository for Container (SWR), public repositories, shared repositories, and supported third-party image repositories. Huawei Cloud CCI documentation explicitly states that containers can pull both SWR images and third-party images .

A container image is a standardized, executable package containing the files and configuration required for a containerized application. Huawei describes it as containing the application and required supporting components such as environments, libraries, configuration files, and file systems. This supports option A.

Option B is consistent with the container-image concept because images can contain a base operating-system environment or filesystem together with application dependencies and configuration required by the application.

Option D is also valid. An image acts as an immutable deployment template: once constructed, the same image can be instantiated repeatedly as containers, enabling applications to run with a consistent packaged environment rather than requiring the software stack to be manually reconfigured for every deployment.

A private registry is useful for controlling proprietary enterprise images, but it is an architectural choice—not a mandatory requirement. Therefore, C is the incorrect statement.

Reference topics: Container Images; SWR; Container Registries; CCI Image Sources; Containerized Application Deployment.

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