H13-811_V3.5 HCIA-Cloud Service V3.5 Questions and Answers

All four options are valid Huawei Cloud CTS functions. Trace recording provides the fundamental audit capability: CTS records system-triggered operations as well as operations performed through the console or APIs. These records enable accountability, troubleshooting, security investigation, and compliance auditing.

Trace query allows users to retrieve and filter recent operation records directly on the CTS console according to attributes such as resource type, operator, trace source, operation status, and time.

Trace transfer supports longer-term preservation. CTS compresses recorded traces into trace files and periodically transfers them to configured storage or logging destinations, including OBS or LTS depending on tracker configuration.

Trace file encryption is also explicitly supported. Huawei's current CTS documentation states that trace files can be encrypted using keys provided through Data Encryption Workshop during the transfer process. This protects audit information at rest and provides stronger security for retained operation records.

This question differs slightly from asking only for the three foundational audit-processing functions; it asks broadly which options are functions of CTS , and Huawei's official function list includes encryption in addition to recording, querying, transfer, and key event notification.

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

Reference topics: Cloud Trace Service Functions; Trace File Encryption; Trace Recording; Trace Transfer; Trace Query.

The statement is FALSE because directly binding an EIP to an ECS is only one of several Huawei Cloud mechanisms for providing Internet access. An ECS with its own EIP can communicate directly with the public network, but ECSs can also access the Internet without having an EIP individually bound to each server .

The principal alternative is a public NAT Gateway using an SNAT rule . Huawei Cloud states that servers in a VPC subnet can share an EIP through a public NAT gateway. The NAT gateway translates their private source addresses into the configured public EIP, enabling outbound Internet connectivity while avoiding the need to expose or allocate an individual public IP address to every ECS.

Huawei's ECS documentation also explicitly describes “Internet connectivity for an ECS without an EIP bound” and recommends NAT Gateway as the standard solution. A proxy/SNAT ECS can also provide an Internet access path in suitable architectures.

Therefore, binding an EIP directly to the ECS is a valid method, but it is not the only method , making the statement false.

Reference topics: Elastic IP; Public NAT Gateway; SNAT; ECS Internet Connectivity; VPC Networking.

The statement is TRUE . Huawei Cloud Image Management Service supports creating private images from external image files, with OBS serving as the staging storage location for those files. The documented workflow is to prepare the source image, upload the image file to an appropriate OBS bucket, and then register or import that file through IMS as a private image.

Huawei's IMS documentation explicitly describes the scenario as registering an image file that has been uploaded to an OBS bucket as a private image . During image creation, the administrator selects Import Image or Image File as the source, selects the OBS bucket containing the prepared file, and then selects the required file.

Supported formats and detailed constraints depend on the image type and import method. For example, standard system-disk image imports and optimized fast-import workflows have specific requirements concerning image formats, file size, operating system, and bucket storage class. However, these restrictions do not change the fundamental integration represented in the question.

OBS therefore provides object storage for the source image file, while IMS performs image registration and lifecycle management. The resulting private image can subsequently be used to provision identically configured ECS instances.

Reference topics: Image Management Service; Creating Private Images; Importing Image Files; OBS and IMS Integration.

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

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.

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

Statements B and C are correct . Huawei Cloud Eye supports batch creation of monitoring alarms. Huawei's documented quota specifically states that up to 50 monitored objects can be selected when creating an alarm rule and that up to 1,000 alarm rules can be created at one time . Huawei even provides the exact example used here: 50 monitored objects multiplied by 20 metrics produces 1,000 alarm rules. Therefore, B is directly supported.

Statement C is also valid. Cloud Eye alarm rules can provide monitoring triggers used with Auto Scaling. An alarm-based AS policy references a Cloud Eye alarm rule; when monitored metrics meet the configured threshold condition, the corresponding scaling action can be initiated.

Statement A is false because Cloud Eye server monitoring is not limited to OS-level resource metrics. With the Agent installed, Huawei Cloud Eye also provides process monitoring , including process CPU usage, memory usage, opened files, and customized process-monitoring tasks.

Statement D is false because alarm templates and batch alarm creation eliminate the requirement to create every alarm rule individually.

Reference topics: Cloud Eye Server Monitoring; Process Monitoring; Alarm Rules; Alarm Templates; Auto Scaling Integration.

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

The statement is TRUE. Huawei Cloud OBS provides several resource-based authorization mechanisms, including bucket policies and object policies. Their principal distinction is the scope of resources to which they apply.

Huawei's official OBS Permission Configuration Guide explicitly states that an object policy applies to only one object in a bucket, whereas a bucket policy applies to multiple objects or all objects within the bucket. This enables administrators to select the authorization mechanism that best matches the required granularity.

An object policy is useful when permissions must be configured specifically for an individual object, such as granting another principal read or write permissions to one particular resource without broadening access to the rest of the bucket.

A bucket policy supports broader authorization scenarios. Its policy statements can define principals, actions, resources, effects, and conditions to grant or restrict access to selected objects, prefixes, or the entire bucket. Typical uses include allowing another Huawei Cloud account to access specified OBS resources or granting IAM identities access to defined bucket content.

The question therefore correctly distinguishes object-level policy scope from bucket-level multi-object policy scope.

Reference topics: OBS Permission Management; Object Policies; Bucket Policies; Resource-Based Authorization.

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

For the HCIA-Cloud Service V3.5 snapshot model represented by this question, the statement is FALSE. Huawei Cloud's exam-era EVS documentation states that an EVS snapshot captures the state of a disk at a specific point in time and can be used for rollback or creation of another disk. However, the snapshot is dependent on its source EVS disk.

Huawei's earlier official EVS documentation explicitly states that when an EVS disk is deleted, the disk data and snapshots created for that disk are also deleted. The applicable documentation also states that when a snapshot's source disk is deleted, all snapshots of that source disk are deleted.

This distinction matters because Huawei has subsequently introduced standard snapshots stored in OBS, for which newer lifecycle behavior can differ. Current documentation distinguishes legacy snapshots from standard snapshots: legacy snapshots are deleted with the source disk, whereas newer standard snapshots may remain. However, HCIA V3.5 questions were written around the earlier EVS snapshot behavior.

Accordingly, the proposition that deleting an EVS disk does not delete its snapshots contradicts the V3.5-era model.

Reference topics: EVS Snapshots; Snapshot Lifecycle; EVS Disk Deletion; Point-in-Time Recovery.

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

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.

The statement is FALSE . Huawei Cloud explicitly supports using VPN to establish communication between VPCs deployed in different regions . The Huawei Cloud VPC FAQ describes this architecture directly: VPCs in the same region can be connected by VPC peering, while VPCs in different regions can establish connectivity through VPN. In the VPN design, each VPC uses a VPN gateway, and the two gateways establish an encrypted connection over the Internet. The VPC CIDR blocks are configured as the local and remote subnets.

This distinction is central to the HCIA V3.5 networking domain. VPC peering is region-scoped : two VPCs connected through a peering connection must reside in the same region. VPN, by contrast, can establish encrypted connectivity between geographically separated VPC networks. Huawei's VPN documentation specifies creating a VPN gateway for each VPC, creating VPN connections, configuring the peer gateway EIP, defining peer subnets, and applying matching cryptographic parameters.

Consequently, saying that Huawei Cloud VPN “does not support” cross-region VPC communications directly contradicts the supported VPN deployment model.

Reference topics: Virtual Private Network; Cross-Region VPC Connectivity; VPC Peering; VPN Gateways.

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

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.

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

Option B is incorrect because Huawei Cloud OBS does not allow a bucket that has already had versioning enabled to return to the original Disabled state. Versioning can initially be enabled on a bucket, but once enabled, it can subsequently only be suspended , not disabled.

Option A is correct. With versioning enabled, OBS assigns unique version IDs to uploaded objects, allowing multiple objects with the same key or name to coexist as different versions. This protects against accidental overwrites and provides point-in-time recovery capabilities.

Option C is also correct when a specific historical version is permanently deleted. Each object version is independently identified by its version ID, so deleting one specified version does not inherently remove the other retained versions.

Option D accurately describes the initial state. Huawei states that versioning is disabled by default for newly created OBS buckets. When versioning has never been enabled, uploading a new object with the same name replaces the existing object instead of maintaining multiple historical versions.

The critical distinction is therefore Disabled versus Suspended . Disabled is the initial state; after versioning is enabled, it cannot be restored to Disabled.

Reference topics: OBS Versioning; Version IDs; Suspending Versioning; Object Recovery.

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

Statement C is incorrect in the HCIA-Cloud Service V3.5 IMS model. Huawei Cloud does not impose a standalone service charge simply for using the core Image Management Service functions such as creating a standard private image. Huawei's official getting-started documentation explicitly states that creating a private image is free . Charges may nevertheless arise from dependent resources associated with image usage.

This distinction explains option A. Depending on the image and deployment model, costs can be associated with licensed operating systems, storage used for image files, backups, OBS objects, or other dependent cloud resources. These costs do not make IMS itself a separately charged service.

Option B correctly reflects the principal image categories taught in the HCIA course: public images, private images, and shared images . Marketplace images are additionally available as third-party packaged offerings but do not invalidate this fundamental IMS classification.

Option D also correctly describes the role of an image. Images provide standardized operating environments and can include the operating system, pre-installed applications, configuration data, and user applications. They can then serve as templates for rapidly creating ECS instances with consistent software configurations.

Accordingly, the incorrect statement is C .

Reference topics: Image Management Service; IMS Billing; Private Images; Image Classification; ECS Creation from Images.

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

The statement is FALSE because the management tracker used for general cloud-resource auditing does not need to be created manually when CTS is first enabled. Huawei Cloud explicitly states that when CTS is enabled for the first time, a management tracker named system is created automatically.

The management tracker identifies and associates with the cloud services used by the account and records management operations, including resource creation, modification, query, login-related actions, and deletion. Therefore, the portion of the statement saying that the user must manually create the tracker is technically incorrect.

Huawei does allow users to create additional data trackers manually. These trackers are specifically designed to record operations performed on data in OBS buckets, such as uploads and downloads. That is different from the automatically created management tracker.

Huawei's official getting-started workflow is explicit: open CTS, choose Enable CTS , and the system automatically creates the management tracker named system. Configuration such as OBS or LTS trace transfer can then be added if long-term retention is required.

Therefore, enabling CTS is necessary, but manually creating its primary management tracker is not.

Reference topics: Cloud Trace Service; Management Tracker; Data Tracker; Enabling CTS.

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

The correct advantages are B, C, and D. Huawei Cloud EVS provides a range of disk specifications and performance classes so customers can select storage appropriate for different workloads and budgets. Huawei's EVS overview explicitly lists various disk types and high security/reliability among its principal benefits.

EVS is also easier to manage than traditional physical storage. Huawei documentation comparing EVS with traditional hard disks states that EVS disks provide higher reliability and I/O throughput and are easier to use. Cloud-based provisioning eliminates much of the physical installation, replacement, cabling, and capacity-management work associated with conventional disks.

Option A is incorrect. EVS is block storage intended for cloud servers and cannot be used independently. Huawei explicitly states that EVS disks must first be attached to a supported server and then initialized, partitioned, and formatted before applications can persist data on them.

High reliability derives from distributed storage and data-protection mechanisms, while the range of available disk classes enables workload-specific performance selection.

Therefore, various disk types, ease of use, and high reliability are advantages; independent use is not.

Reference topics: EVS Advantages; Block Storage; EVS Reliability; EVS Disk Types.

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

All four operations are supported management actions for Huawei Cloud RDS instances, subject to the applicable database engine, instance type, current status, and other service constraints.

Changing the failover priority is supported for primary/standby RDS deployments. Huawei allows administrators to prioritize either Reliability , which emphasizes data consistency, or Availability , which emphasizes service continuity during failover.

Deleting a DB instance is a standard lifecycle-management operation available to appropriately authorized users. Huawei's RDS permission model includes the rds:instance:delete action for this purpose.

Scaling up storage space is likewise an established RDS modification operation. Administrators can increase allocated storage when database capacity requirements grow, and supported database engines can also provide storage autoscaling options.

Finally, rebooting a DB instance is a supported administrative action used when configuration changes, troubleshooting, or other operational circumstances require an instance restart. Huawei's CTS integration explicitly identifies both scaling storage and restarting an instance as auditable RDS operations.

Huawei's RDS API catalog lists deleting, scaling storage, rebooting, and changing failover priority as supported instance-management operations.

Reference topics: RDS Instance Management; Failover Priority; Storage Scaling; DB Instance Reboot; DB Instance Deletion.