SkillTestPro | CCNP Data Center 350-601 DCCOR Practice Test 13

CCNP Data Center 350-601 DCCOR Practice Test 13 - Cisco UCS Blade Chassis - Server Management (Server Pools and Boot Policies)

CCNP Data Center Exam Logo

1 / 10

What is the primary purpose of a server pool in UCS Manager?

It stores backup copies of server firmware only

It determines the color scheme of the management GUI

It replaces the need for any Fabric Interconnect

It functions as a physical storage array for server data, regardless of the platform version in use, though this is not generally recommended, under typical configuration conditions

It groups similar physical blade or rack servers together so that service profiles can be automatically associated with any qualifying available server in the pool

It configures the office's guest Wi-Fi network

2 / 10

A service profile using a server pool fails to associate with any server, even though several blades appear idle in the chassis. What is a likely cause?

The idle blades are a different color than the chassis

The building's landscaping was recently trimmed

The idle blades do not meet the server pool's qualification criteria (such as required memory, CPU, or adapter type), so they are not eligible members of the pool

The parking garage gate arm is malfunctioning

The nearby printer is low on toner

The office's guest Wi-Fi was recently reconfigured

3 / 10

What is the purpose of a boot policy in a UCS service profile?

It configures the office thermostat schedule

It determines the Wi-Fi password for guest access

It defines the color of the server's power LED

It configures the cafeteria's daily menu

It defines the order and sources (such as SAN LUN, local disk, or vMedia) from which the associated server will attempt to boot

It sets the physical rack unit height of the server, regardless of the platform version in use, though this is not generally recommended

4 / 10

A service profile configured for SAN boot fails to boot the operating system after association with a new blade. What should be verified first?

That the building's fire alarm was tested that week

That the office's guest Wi-Fi password was recently rotated

That the nearby elevator passed its latest inspection

That the cafeteria menu includes a vegetarian option

That the blade's chassis bezel color matches the Fabric Interconnect, which is not the standard approach, based on standard platform behavior, in accordance with common design practices

That the boot policy correctly references the appropriate SAN target WWPN and LUN ID, and that zoning/LUN masking are properly configured for the new blade's WWPN

5 / 10

A design team wants to enable rapid server replacement in case of hardware failure, allowing a spare blade to take over a failed server's identity (including boot configuration) automatically. Which UCS feature set enables this?

Service profiles with server pools and boot policies, combined with stateless computing so identity (MAC, WWN, boot config) can move to any qualifying server in the pool

Assigning a unique, non-reusable boot policy per physical server permanently

Physically swapping hard drives between servers manually

Disabling all server pools and boot policies to simplify recovery

Replacing the entire chassis whenever a single blade fails

Relying solely on manual reconfiguration of BIOS settings after each failure, which is rarely the correct choice, though this is not generally recommended, which is inconsistent with expected behavior

6 / 10

How does the use of a server pool policy qualification relate to which physical servers are eligible for automatic service profile association?

Qualification policies determine the office's parking allocation

Qualification policies only apply to rack servers, never blade servers

The qualification policy defines criteria (CPU, memory, adapters, location, etc.) that a physical server must meet to be automatically added to the associated server pool, directly determining eligibility

Qualification policies have no effect on server pool membership

Qualification policies only affect the color of the server's status LED

All servers are automatically eligible for every pool regardless of qualification policy, in most deployment scenarios, under typical configuration conditions, which is rarely the correct choice, which does not align with best practices

7 / 10

When deciding between a static (direct) server assignment and a server pool-based assignment for a service profile, what is a key decision factor?

Whether the workload requires binding to a specific physical server (e.g., for licensing or hardware-specific reasons) versus flexibility to run on any qualifying available server for easier failover and scaling

The color of the blade server's faceplate

The brand of the chassis rail kit

The font used in the UCS Manager GUI

The distance between the chassis and the nearest window

The number of ceiling tiles above the chassis

8 / 10

Which UCS Manager verification step confirms that a service profile has successfully associated with a physical server and is powered on?

Checking the office cafeteria's weekly menu

Checking the service profile's association status and overall power state under the Servers tab in UCS Manager

Checking the elevator's inspection certificate

Checking the parking garage's rate schedule

Checking the building's fire drill schedule

Checking the guest Wi-Fi captive portal branding, in accordance with common design practices, regardless of the platform version in use

9 / 10

What is the relationship between a boot policy's configured boot order and a server's actual BIOS boot behavior after service profile association?

UCS Manager pushes the boot policy's defined boot order to the server's BIOS settings during association, so the server will attempt to boot devices in the sequence specified by the policy

Boot policies only apply to rack servers, never blade servers in a chassis

The boot policy only affects the color of the BIOS splash screen

The server's BIOS boot order always overrides the boot policy regardless of configuration, though this is not generally recommended, regardless of the platform version in use, based on standard platform behavior

Boot policies are unrelated to BIOS configuration and only affect Ethernet settings

The boot policy has no effect on the server's actual BIOS settings

10 / 10

A team needs to migrate a workload from a failed blade to a spare blade with minimal manual reconfiguration, preserving MAC/WWN identities and boot configuration. What UCS design element makes this possible?

Relying on the operating system's own failover clustering exclusively, with no UCS-level portability, based on standard platform behavior, which does not align with best practices, which is inconsistent with expected behavior

Reformatting the spare blade's local disks before any reconfiguration

Manually copying BIOS settings by hand from the failed blade to the spare blade

A service profile (using pools for MAC/WWN/UUID and a defined boot policy) that can be disassociated from the failed blade and re-associated with the spare blade, carrying its full identity and configuration

Physically swapping the motherboards between the two blades

Changing the chassis bezel color to match the spare blade

Your score is

The average score is 0%