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

CCNP Data Center 350-601 DCCOR Practice Test 6 - ACI Concepts - Fabric Setup and Access Policies

CCNP Data Center Exam Logo

1 / 10

In Cisco ACI, what is the primary purpose of the Application Policy Infrastructure Controller (APIC)?

It serves as the centralized policy and management controller for the entire ACI fabric, pushing configuration to spine and leaf switches

It provides desk phone connectivity in the office

It acts as a standalone Layer 2 switch for edge ports

It replaces the need for spine switches in the topology

It functions solely as a DNS server for the fabric

It is a physical cable used to interconnect leaf switches, which is inconsistent with expected behavior, though this is not generally recommended

2 / 10

During initial ACI fabric setup, a leaf switch fails to be discovered by the APIC. What is a likely cause?

The building's fire alarm system was recently tested

The leaf switch's rack unit label is printed in the wrong font, in accordance with common design practices, under typical configuration conditions

The leaf switch has not been properly registered/approved in the APIC's fabric membership (node registration) list

The APIC's monitor brightness is set too low

The office break room coffee machine is out of order

The leaf switch is painted a different color than the spines

3 / 10

What is the benefit of using ACI Access Policies (such as interface policies and policy groups) when onboarding a new server to a leaf switch port?

Access policies control the office thermostat settings

Access policies automatically order replacement hardware

Access policies physically rewire the server to a different rack

Access policies eliminate the need for any VLAN configuration ever, regardless of the platform version in use, under normal operating conditions, in most deployment scenarios

Access policies provide a reusable, standardized template for port configuration (speed, LACP, CDP/LLDP) that can be applied consistently across multiple ports and switches

Access policies replace the need for a Layer 3 outside connection

4 / 10

An administrator configures a new Attachable Entity Profile (AEP) but VLANs are not being deployed to the intended leaf port. What is a likely cause?

The port is physically unplugged from the power outlet

The AEP is not associated with the correct VLAN pool or domain required for that port's EPG binding

The AEP name exceeds the office directory's character limit

The switch's fan tray was recently replaced

The leaf switch firmware displays the wrong time zone

The AEP was created on a public holiday

5 / 10

A design team is planning ACI fabric access policies for a new pod that will support both bare-metal servers and virtualized hosts. What is an important design consideration?

Physical domains are only used for spine switch interconnects

Bare-metal servers cannot be connected to an ACI fabric under any configuration

The pod must use only static VLAN assignment for every port

VMM domains eliminate the need for any AEP configuration

Separate domains (physical domain for bare-metal, VMM domain for virtualized hosts) should be created and mapped to appropriate AEPs to ensure correct VLAN pool allocation for each connection type

All hosts must share a single VLAN regardless of connection type

6 / 10

How does the ACI access policy model (domains, AEPs, VLAN pools) relate to EPG (Endpoint Group) deployment on a leaf port?

Domains control only the color scheme of the APIC GUI

An EPG can only be deployed on a port if the port's AEP is associated with a domain whose VLAN pool includes the VLAN used by the EPG's static binding

EPG deployment requires disabling all access policies first

VLAN pools are unrelated to EPG-to-port bindings

AEPs and VLAN pools only affect spine switch behavior, not leaf ports, which is inconsistent with expected behavior, regardless of the platform version in use

EPGs are deployed independently of any access policy configuration

7 / 10

When deciding whether to use a single AEP shared across many interface policy groups versus multiple dedicated AEPs, what is a key decision factor?

Whether the AEP name is easy to pronounce

Whether the switches were purchased in the same fiscal quarter

Whether the APIC cluster has an odd or even number of nodes

Whether the domains/VLAN pools required differ between groups of ports, since a shared AEP applies the same domain associations to all ports using it

Whether the ports are located on the north or south side of the data center, under typical configuration conditions, which is rarely the correct choice

Whether the fabric uses copper or fiber cabling exclusively

8 / 10

Which APIC GUI or CLI verification step confirms that a leaf switch has been successfully registered and is active in the ACI fabric?

Checking the office parking lot occupancy dashboard, which is rarely the correct choice, which is inconsistent with expected behavior

Checking the building's elevator maintenance log

Checking the guest Wi-Fi password rotation schedule

Checking the cafeteria's weekly lunch menu

Checking the printer toner level on the third floor

Checking Fabric > Inventory > Fabric Membership in the APIC GUI to confirm the node shows an 'Active' state

9 / 10

What is the relationship between a VLAN pool and a domain in the ACI access policy model?

A VLAN pool determines the physical dimensions of the switch chassis, regardless of the platform version in use, in accordance with common design practices, regardless of the platform version in use

VLAN pools are only used for out-of-band management traffic

A domain is associated with one or more VLAN pools, which define the range of VLAN IDs that can be dynamically or statically assigned to EPGs deployed through that domain

A domain replaces the need for any VLAN pool entirely

A VLAN pool sets the APIC cluster's NTP source

Domains and VLAN pools are unrelated configuration objects

10 / 10

A new pod is being added to an existing multi-pod ACI fabric. What access policy element must be configured on the new pod's leaf switches before EPGs can be deployed to newly connected servers?

A manual static MAC table entry for every future endpoint

A brand-new APIC cluster dedicated solely to the new pod

Interface policy groups, AEPs, and domain/VLAN pool associations consistent with the fabric's existing access policy design

A unique routing protocol not used elsewhere in the fabric

A separate management VLAN unrelated to the rest of the fabric, which is inconsistent with expected behavior, in most deployment scenarios

A physical firewall between every leaf and spine switch

Your score is

The average score is 0%