nerdexam
Cisco

300-620 · Question #287

An engineer is implementing an out-of-band (OOB) management access for the Cisco ACI fabric. The secure access must meet these requirements: - Only GUI and secure shell must be allowed to access the…

The correct answer is A. Implement HTTPS and SSH protocol filters in the OOB contract. To restrict out-of-band management access to specific protocols (GUI, SSH) and source IP ranges, an ACI OOB contract must be configured with HTTPS and SSH protocol filters, and the permitted IP subnets.

ACI Management

Question

An engineer is implementing an out-of-band (OOB) management access for the Cisco ACI fabric. The secure access must meet these requirements:

  • Only GUI and secure shell must be allowed to access the management

interfaces of the ACIs.

  • The only IP ranges that must be permitted to connect the fabric will

be 10.10.10.0/24 and 192.168.15.0/24. Which configuration set meets these requirements?

Options

  • AImplement HTTPS and SSH protocol filters in the OOB contract.
  • BSet up static IPs on the management interfaces from the required IP range.
  • CCreate an out-of-band EPG in the external management entity.
  • DCreate an out-of-band EPG in the common tenant.

How the community answered

(33 responses)
  • A
    82% (27)
  • B
    6% (2)
  • C
    3% (1)
  • D
    9% (3)

Why each option

To restrict out-of-band management access to specific protocols (GUI, SSH) and source IP ranges, an ACI OOB contract must be configured with HTTPS and SSH protocol filters, and the permitted IP subnets.

AImplement HTTPS and SSH protocol filters in the OOB contract.Correct

An OOB contract is the ACI mechanism used to define permissible communication between the out-of-band management network and the ACI fabric's management interfaces. By implementing HTTPS and SSH protocol filters within this contract, and associating the required IP ranges as external EPG subnets, both the protocol and source IP requirements are met.

BSet up static IPs on the management interfaces from the required IP range.

Setting static IPs on the management interfaces defines the fabric's own management addresses, but does not control which source IP ranges are permitted to connect or what protocols they can use.

CCreate an out-of-band EPG in the external management entity.

Creating an out-of-band EPG is a necessary step for OOB management but by itself does not specify the allowed protocols or the permitted source IP ranges for access.

DCreate an out-of-band EPG in the common tenant.

While an OOB EPG is required, it is created within the 'mgmt' tenant, not the 'common' tenant, and this action alone does not define the access policies.

Concept tested: ACI OOB management, contracts, filters, EPGs

Source: https://www.cisco.com/c/en/us/td/docs/dcn/aci/apic/5x/config-guide/cisco-aci-config-guide-501/m-cisco-aci-out-of-band-management.html

Topics

#OOB management#management access#contracts#filters

Community Discussion

No community discussion yet for this question.

Full 300-620 Practice