H13-811_V3.5 Practice Questions

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.

Huawei Cloud establishes a clear parent-child relationship between a Huawei Cloud account and the IAM users created under that account. The account owns the cloud resources and is the billing entity , whereas IAM users consume or manage resources according to permissions assigned by the account administrator.

Therefore, option C is correct: IAM users do not independently pay for the resources they use. Charges generated through their authorized operations are billed to the parent account. Options B and D are also correct because the account administrator retains authorization control and can modify or revoke permissions assigned to IAM users.

Option A is incorrect because it incorrectly treats the IAM user as a payment entity. Authorization determines what an IAM user is permitted to access or operate , not who is responsible for payment. Huawei Cloud explicitly distinguishes resource ownership and billing from delegated resource access. An IAM user does not receive an independent bill merely because access to a resource has been authorized.

Accordingly, the correct relationship is: account owns and pays; IAM users operate resources according to delegated permissions; the account controls those permissions .

Reference topics: IAM Users; Huawei Cloud Accounts; IAM Authorization; Billing Responsibility.

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

Statements B and C are false . Huawei Cloud distinguishes alarm-based, scheduled, and periodic Auto Scaling policies. An alarm policy triggers a scaling operation in response to monitored metrics such as CPU utilization. Scaling “every three hours” is time-interval behavior and therefore belongs to a periodic policy , not an alarm policy. This makes B incorrect.

Statement C is also incorrect. The expected number of instances is the desired number of ECS instances that should currently run within an AS group. Huawei specifies that this value must remain between the configured minimum and maximum instance counts. It can be modified manually or changed through scheduled, periodic, or alarm-based policies. It is not synonymous with the minimum instance count during peak hours.

Statement A is valid because an AS configuration can use a Huawei Cloud public image; Huawei's AS configuration parameters explicitly support public, private, and shared images.

Statement D is also valid. Huawei specifies that when an existing ECS is manually added to an AS group, the ECS must not already be a member of another AS group .

Consequently, the two false statements are B and C .

Reference topics: Auto Scaling Configurations; AS Policies; Expected Instances; AS Groups.

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