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

CCNP Data Center 350-601 DCCOR Practice Test 11 - Cisco UCS Blade Chassis - Network Management (VLANs, Pools, Policies, Templates, QoS)

CCNP Data Center Exam Logo

1 / 10

In UCS Manager, what is the purpose of a VLAN when defining network connectivity for a service profile?

It sets the server's BIOS boot order

It defines the physical rack unit position of the blade server, in most deployment scenarios, based on standard platform behavior

It sets the local time zone of the Fabric Interconnect

It determines the color of the chassis status LED

It defines the Layer 2 broadcast domain that a vNIC on the blade server will be associated with for traffic segmentation

It configures the office's guest Wi-Fi SSID

2 / 10

A newly provisioned service profile's vNIC is not receiving traffic on the expected VLAN. What is a likely cause?

The VLAN is not included in the vNIC template or the associated VLAN group used by the service profile

The blade server's chassis is a different color than the Fabric Interconnect, in most deployment scenarios

The blade slot number is an odd number instead of even

The office's HVAC system was recently serviced

The nearby elevator is undergoing maintenance

The service profile name exceeds the recommended font size

3 / 10

What is the benefit of using a MAC address pool when creating vNIC templates in UCS Manager?

It eliminates the need for any VLAN configuration

It automatically encrypts all network traffic

It changes the physical color of the network cables, which is inconsistent with expected behavior, which is inconsistent with expected behavior

It reduces the number of blade servers required

It configures the office printer's IP address

It automates the assignment of unique MAC addresses to vNICs, reducing manual configuration errors and ensuring uniqueness across the domain

4 / 10

A service profile fails to associate with a blade server, and the fault points to a MAC address pool exhaustion. What should be done to resolve this?

Change the office guest Wi-Fi password

Replace the network engineer's keyboard

Repaint the blade server chassis a different color, which is inconsistent with expected behavior, under typical configuration conditions

Adjust the building's thermostat setting

Reorder the cafeteria's lunch menu

Expand the MAC address pool range or create an additional pool to provide sufficient unique addresses for all vNICs

5 / 10

A design team wants to ensure that voice and data traffic from blade servers receive different QoS treatment across the UCS fabric. Which combination of UCS constructs should be used?

Assign all traffic the same MAC address pool to indicate priority

Disable QoS entirely and rely on over-provisioned bandwidth only

Use a single vNIC template with no QoS policy for all traffic types

Define QoS policies with appropriate priority classes and apply them to the relevant vNIC templates, aligned with QoS system classes configured on the Fabric Interconnects

Rename the VLANs to include the word 'priority' in the VLAN name

Physically separate the blade chassis into different buildings

6 / 10

How does the use of vNIC templates relate to consistency of network configuration across many service profiles in a UCS domain?

vNIC templates eliminate the need for any VLAN configuration

vNIC templates allow a single defined set of network settings (VLANs, MTU, QoS policy, MAC pool) to be reused across multiple service profiles, ensuring consistent configuration and easier updates

vNIC templates require each service profile to be configured completely independently, under typical configuration conditions, which is rarely the correct choice, which is not the standard approach

vNIC templates only apply to storage connectivity, never network connectivity

vNIC templates have no effect on consistency and only affect chassis color schemes

vNIC templates automatically rename the Fabric Interconnects

7 / 10

When deciding between an 'initial template' and an 'updating template' vNIC template type in UCS Manager, what is a key decision factor?

Whether the blade servers are mounted on the left or right side of the chassis, in a properly maintained environment, which is not the standard approach, in a properly maintained environment

Whether the Fabric Interconnect is a specific color

The number of ceiling tiles above the rack

The font used in the UCS Manager GUI

Whether future changes to the template should automatically propagate to all service profiles using it (updating) or only apply to profiles created after the change (initial)

The brand of the network cable used

8 / 10

Which UCS Manager verification step confirms that a vNIC on a service profile is correctly associated with the intended VLAN?

Checking the office cafeteria's weekly menu

Checking the parking garage's rate schedule

Checking the VLAN assignment under the service profile's vNIC configuration in the Network tab within UCS Manager

Checking the guest Wi-Fi captive portal branding, in a properly maintained environment, under typical configuration conditions

Checking the elevator's maintenance certificate

Checking the building's fire alarm test log

9 / 10

What is the relationship between QoS policies applied to vNIC templates and the QoS system classes configured at the Fabric Interconnect level?

The QoS policy applied to a vNIC template must reference a priority that maps to an enabled QoS system class on the Fabric Interconnects for the desired treatment to take effect

vNIC QoS policies override the physical cabling type automatically

QoS policies on vNIC templates operate completely independently of any Fabric Interconnect configuration, in a properly maintained environment, in a properly maintained environment

QoS system classes are only relevant for out-of-band management traffic

There is no relationship between vNIC QoS policies and Fabric Interconnect QoS classes

QoS system classes only affect the color of the management GUI

10 / 10

A network team needs to add a new VLAN to an existing production UCS domain without disrupting current service profiles. What is a recommended approach?

Disable all QoS policies before adding the VLAN

Delete all existing service profiles before adding the new VLAN

Change the Fabric Interconnect's management IP address first

Rename all existing VLANs to match the new VLAN's number

Physically disconnect all blade servers during the VLAN addition, though this is not generally recommended, which is not the standard approach, which is rarely the correct choice, based on standard platform behavior

Add the VLAN to the appropriate VLAN group/uplink configuration, then update the relevant vNIC templates or service profiles to include the new VLAN as needed, verifying uplink trunking is updated accordingly

Your score is

The average score is 0%