Free Huawei H13-527_V5.0 Practice Exam with Questions & Answers

After correcting the typing error, option A is still the invalid one. The correct Neutron legacy syntax is based on associating a floating IP with a port , not with a volume . Official OpenStack and Red Hat OpenStack command references show the valid legacy pattern as neutron floatingip-associate FLOATINGIP_ID PORT, meaning the floating IP ID is given first and the target must be a port ID or name . A volume ID does not belong in this operation.

OpenStack documentation also shows that the supported modern client approach is to use openstack server add floating ip < server > < ip-address > for server association, while older nova floating-ip-associate commands existed as legacy or deprecated commands. That means option D reflects a historical valid form, and option C reflects a Neutron-style valid form.

Option B is not the modern official syntax shown in current docs, but A is unquestionably invalid because it uses the wrong object type and wrong argument structure. For a single-answer exam question, the best verified answer is A .

========

The correct answer is B (FALSE). Huawei documentation confirms that a dummy external network exists and may appear as an option when creating services such as VPC-related resources. Huawei’s Elastic IP and related network-service guidance gives examples such as selecting the dummy external network in one group and then selecting an actual Internet external network in another group for service use. This shows that the dummy external network is mainly a default placeholder or structural network object, not the real tenant-bound network required for service traffic.

Because of that, the second part of the statement is inaccurate. The proper requirement is not simply to “bind the dummy external network to tenants” so VPCs can be created properly. Instead, tenants and services need the correct actual external network resources and related mappings or selections. The Huawei examples make it clear that the dummy external network is not the operational external network used for normal connectivity. Therefore, although the first part about default creation is consistent with Huawei practice, the conclusion about binding it to tenants is not correct. For that reason, the full statement is FALSE.

========

The correct answer is B. VM performance deteriorates. Huawei’s official Resource Audit Overview for HUAWEI CLOUD Stack explains that Service OM resource audit is designed for high-frequency exception types caused by unplanned system failures, such as host reboot, process restart, or backup recovery. Huawei explicitly states that resource audit is used when problems such as residual resources and unavailable resources occur after those events. This directly matches options C and D. The same audit section also covers scenarios like abnormal VM states, orphan VMs, fake VMs, and image or volume inconsistencies caused by restoration or failed processes.

By contrast, VM performance deterioration is a performance management or capacity tuning issue, not a resource-audit exception type. Huawei’s compute resource management materials discuss performance tuning separately, such as changing VM flavors or adjusting resources, which shows that performance degradation is not handled by the Service OM resource-audit function itself. Therefore, among the four options, the issue that cannot be handled by Service OM’s resource audit is B.

========

The correct answer is B. BMS . For a typical web application architecture on HUAWEI CLOUD Stack, ECS provides the compute instances, IMS provides reusable images for quick deployment, AS enables elastic scale-out and scale-in based on demand, and ELB distributes traffic and improves availability. Huawei’s ECS and IMS documentation explicitly notes that ECS images can be used with Auto Scaling for dynamic expansion to meet peak demand, which directly supports quick deployment and elasticity.

BMS is a dedicated bare-metal service intended for scenarios needing direct physical hardware access, stronger isolation, or reduced virtualization overhead. It is useful for special workloads, but it is not required for the classic goals listed in the question, especially high cost-effectiveness and fast elastic web scaling. Those goals are more naturally achieved with ECS-based architectures plus ELB and AS. Huawei’s BMS positioning emphasizes physical-server management and performance advantages, not being a necessary part of a standard web application elasticity stack. Therefore, among the listed services, the one that is not required is BMS , making B the verified answer.

========

The correct answer is C. Quick and elastic adjustment of CPUs and memory . Huawei’s official HUAWEI CLOUD Stack materials describe Bare Metal Server (BMS) as dedicated physical servers that provide excellent or remarkable computing performance and direct access to physical resources. Huawei also explains that Ironic works with Nova and Neutron to manage BMS resources, highlighting the physical-server nature of the service. These characteristics support advantages such as physical isolation , no hypervisor performance overhead , and direct access to specialized hardware .

By contrast, Huawei’s ECS Advantages documentation explicitly says that with ECS, administrators can modify an ECS flavor, including the number of CPUs and memory size . That kind of quick and elastic CPU/memory adjustment is therefore an ECS advantage , not a BMS-over-ECS advantage.

So after correcting the option formatting, A , B , and D are all real BMS strengths, while C belongs more to virtualized ECS elasticity. Therefore, the verified answer is C .

========

The best verified answer is A and D . Huawei’s official EVS documentation states that the major disk performance metrics include IOPS, throughput, and latency . Among the options given in your question, throughput is therefore definitely one of the major EVS disk metrics. ( ; )

In addition, Huawei EVS usage materials consistently treat capacity as a core disk attribute when defining EVS disks and their sizing. Although capacity is not a performance metric like throughput, exam questions of this type often use “major metrics” more broadly to mean the key measurable characteristics users pay attention to when selecting disks. By contrast, maximum snapshots is a feature limit rather than a primary disk metric, and endurance is not listed by Huawei as one of the standard major EVS disk metrics in the product guidance cited above.

So based on Huawei documentation and the exam-style wording, the most defensible answer is A and D : Throughput and Capacity . ( )

========

The statement is TRUE . In HUAWEI CLOUD Stack, a resource set is a logical grouping of cloud resources under a tenant or VDC for purposes such as authorization, organization, and management. Huawei documentation describes resource sets as being used to classify and manage resources within a tenant context, which means their scope is tied to the tenant’s own resource domain. This is why resource sets are commonly used to separate production, test, departmental, or project resources inside the same tenant or VDC rather than as a cross-tenant migration mechanism. ( )

Operationally, resources can be reassigned or moved between resource sets when administrators need to reorganize management boundaries, but the resource-set model itself is not designed to move resource sets across tenants . Cross-tenant transfer would break the tenant-based isolation and authorization structure that Huawei Cloud Stack uses for cloud governance. This is consistent with Huawei’s hierarchical cloud management approach, where tenants are major security and administration boundaries, while resource sets are subordinate organizational tools. Therefore, the verified answer is A (TRUE) because resource migration between resource sets is allowed within the management domain, but resource sets themselves are not intended for migration across tenants. ( )

========

In OpenStack, Keystone is the Identity service responsible for authentication and authorization. A core Keystone concept is that permissions are not usually granted directly to a user; instead, users are assigned one or more roles, and those roles are associated with a project, domain, or system scope. OpenStack’s official Keystone documentation states that the Identity service assigns roles to users, and a user can have different roles in different projects. It also explains that default roles such as admin, member, and reader are used to control what actions a user can perform. This means the statement is correct: Keystone users are assigned roles, and those roles determine their permissions.

This is also consistent with Huawei Cloud’s identity and permission model, where permissions are controlled through assigned authorization policies and identities use tokens containing identity and permission information when accessing services. In practical Huawei Cloud Stack and OpenStack-based environments, role-based access control is the standard method for defining what a user is allowed to do. Therefore, the correct answer is TRUE .

The correct answers are A and C. Huawei’s cloud-service monitoring documentation shows that administrators can view the cloud service topology and dependencies between the current cloud service and other cloud services. This is exactly the kind of capability enabled by a CMDB’s dynamic dependency model, and it clearly supports application deployment topology display, which corresponds to option C.

Dynamic dependency information is also highly relevant to root cause locating, because dependency graphs help O & M personnel trace failures from one service to dependent services and identify the likely upstream or downstream source of an issue. Huawei troubleshooting materials reference locating faults of dependent services, which aligns with option A.

By contrast, resource capacity planning is a capacity-management scenario rather than a dynamic-dependency scenario, and certificate replacement in batches is an operational maintenance task that does not primarily depend on CMDB dynamic dependencies. Therefore, the supported scenarios are A and C, making the verified answer A, C.

Horizon is the web-based dashboard for OpenStack, designed to provide a consistent graphical interface for managing cloud resources. In practice, Horizon focuses on presenting a consistent view of services to users and administrators, and OpenStack components commonly maintain API backward compatibility to support upgrades and continued interoperability. OpenStack documentation also shows that Horizon can be used in larger and multi-region environments, which supports the idea that scalability is relevant to its operational value.

However, API eventual consistency is not a Horizon value proposition. “Eventual consistency” is a concept found in distributed storage systems such as OpenStack Swift/Object Storage, where updates may take time to become visible everywhere. OpenStack documentation explicitly uses this term in the context of Object Storage behavior, not Horizon dashboard design. Because Horizon is a management dashboard rather than a distributed storage consistency model, API eventual consistency does not belong as one of its core value propositions. Therefore, the correct answer is A . This is the best-supported conclusion from official OpenStack documentation and aligns with Huawei Cloud training-style OpenStack topic coverage.