500-470 Sample Questions Answers

An ISE PoV (Proof of Value) is a service that demonstrates the value of Cisco Identity Services Engine (ISE) to potential customers. It consists of two components: a virtual machine (VM) and a license. The VM is a pre-configured ISE environment that can be deployed on any cloud platform, such as Cisco dCloud1. The license is a one-time payment that grants access to the ISE features and capabilities for three years2.

The two options that are used as part of an ISE PoV are A and E. Option A refers to the VM, which is the core component of the ISE PoV. Option E refers to the POV Kit, which is a bundle that includes the VM, the license, and some additional resources, such as documentation, videos, and webinars2. Option B, C, and D are not used as part of an ISE PoV.

References: 1 Cisco dCloud 2 ISE PoV licenses

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750/software/release/15-0_2_se

/configuration/guide/scg3750/sw8021x.pdf

The protocol that is used between an endpoint and a switch with an 802.1 authentication is EAP, which stands for Extensible Authentication Protocol. EAP is a framework that defines how the endpoint (also called the supplicant) and the switch (also called the authenticator) exchange authentication messages over a wired or wireless network. EAP supports various authentication methods, such as passwords, certificates, tokens, or biometrics, and can be encapsulated in different transport protocols, such as RADIUS, Diameter, or EAPOL. EAP is used in 802.1X authentication, which is a standard for port-based network access control that prevents unauthorized access to a network1.

The other options, TACACS, MAB, and RADIUS, are not protocols that are used between an endpoint and a switch with an 802.1 authentication. TACACS is a protocol that provides remote authentication and authorization for network devices, such as routers or switches, but it is not used for endpoint authentication. MAB is a technique that uses the MAC address of an endpoint as a credential for 802.1X authentication, but it is not a protocol itself. RADIUS is a protocol that provides centralized authentication, authorization, and accounting for network access, but it is not used directly between the endpoint and the switch, but rather between the switch and the authentication server1. References := : 2: What Is 802.1X Authentication? How Does 802.1x Work? - Fortinet2, 1: IEEE 802.1X - Wikipedia1

 Identity management is the practice of making sure that people and entities with digital identities have the right level of access to enterprise resources like networks and databases. User roles and access privileges are defined and managed through an identity management system, such as Cisco Identity Services Engine (ISE)1. Identity management solves two customer problems:

• Provides network visibility and security: Identity management allows customers to see who and what is on their network, and to control their access based on policies and context. Identity management also integrates with other security solutions, such as Cisco Firepower, Cisco Stealthwatch, or Cisco Umbrella, to detect and respond to threats, and to enforce adaptive network access policies based on the threat level of the endpoints2.
• Achieves dynamic and adaptive network segmentation: Identity management enables customers to segment their network based on the identity and context of the users and devices, rather than the IP addresses and VLANs. This allows customers to implement a zero-trust model, where only trusted users and devices can access the resources they need, and where the access policies can be dynamically updated based on the changing conditions and requirements. Identity management also supports Cisco TrustSec, which is a technology that assigns scalable group tags (SGTs) to endpoints and enforces group-based policies (contracts) across the network3.

References:

 1: [What Is Identity Access Management (IAM)? - Cisco

https://www.arista.com/assets/data/pdf/Whitepapers/Arista_Networks_VXLAN_White_Paper.pdf

A VxLAN header adds 50 bytes to an original Ethernet frame. This is because a VxLAN header consists of the following components:

• 8-byte outer UDP header for VxLAN: The default VxLAN destination UDP port number is 47891
• 20-byte outer IP header: Valid addresses of VTEPs or VxLAN multicast groups on the transport network. Devices in the transport network forward VxLAN packets based on the outer IP header1
• 8-byte VxLAN header: VxLAN information for the frame. It includes a 24-bit VxLAN Network Identifier (VNI) that identifies the VxLAN of the frame, and an 8-bit flags field that indicates the validity of the VNI1
• 14-byte inner Ethernet header: The original Ethernet header of the encapsulated frame. It includes the source and destination MAC addresses, the EtherType, and optionally a 4-byte VLAN tag2

The total size of these components is 8 + 20 + 8 + 14 = 50 bytes. Therefore, a VxLAN header adds 50 bytes to an original Ethernet frame.

References :=

• VXLAN packet format - Aruba
• MTU Considerations for VXLAN | Matt Oswalt

The Cisco V-Edge Router performs QoS traffic classification on the ingress interface, before the traffic enters the VPN. The classification is based on the match criteria specified in the access lists, which can include the source and destination IP addresses, ports, protocols, DSCP values, and application-aware NBAR attributes. The classification results in assigning a forwarding class and a QoS group to each packet. The forwarding class determines the output queue and the scheduling policy for the packet on the egress interface. The QoS group is an internal label that can be used to remark the DSCP value of the packet or to match the packet in another access list for further processing. References:

• : Forwarding and QoS Configuration Guide for vEdge Routers, Cisco SD-WAN Release 20, Chapter 2: Configuring Localized Data Policy, https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/qos/vEdge-20-x/qos-book/localized-data-policy.html#id_1050591
• : Cisco SD-WAN Design Guide, Release 20, Chapter 6: Quality of Service, https://www.cisco.com/c/en/us/td/docs/solutions/CVD/SDWAN/2020/b_SD-WAN_Design_Guide_Aug_2020/b_SD-WAN_Design_Guide_Aug_2020_chapter_0110.html2

Device Sensor is a feature that enables Cisco devices to collect and report information about the endpoints connected to them. This information can be used by ISE to identify and classify the endpoints, and apply appropriate policies based on their attributes. Device Sensor can collect information from various sources, such as DHCP, CDP, LLDP, and HTTP User-Agent. Among the options given, only DHCP and CDP are valid sources of information for Device Sensor. References := : Cisco Identity Services Engine Administrator Guide, Release 2.7 - Device Sensor [Cisco Identity Services Engine]- Cisco (https://learningnetworkstore.cisco.com/c/en/us/td/docs/security/ise/2-7/admin_guide/b_ise_admin_guide_27/b_ise_admin_guide_27_chapter_010100.html)

2of30

https://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise-networks/sd-wan/nb-07-clo ud-router-data-sheet-cte-en.pdf

A vEdge Cloud Router is a virtualized version of the vEdge router that can be deployed in various cloud environments. According to the Cisco vEdge Cloud Data Sheet1, the vEdge Cloud Router can be instantiated as a virtual machine (VM) on a KVM hypervisor or as a VM on a VMware ESXi hypervisor, as well as in public cloud environments, such as Amazon AWS or Google Cloud Platform. Therefore, the two platforms that can host a vEdge Cloud Router are AWS and Microsoft Azure.

References:

 1: [Solutions - Cisco vEdge Cloud Data Sheet - Cisco]