Explanation
DNA Center is the central point of management for SD-Access. It provides a graphical user interface (GUI) to design, provision, and monitor the SD-Access fabric. DNA Center also offers various service applications that leverage the network data and analytics to provide insights, automation, and assurance for the network and the applications running on it. DNA Center does not perform the functions of identifying and authenticating endpoints, which are handled by ISE; nor does it act as the point of exchange of reachability and policy for two domains, which are the roles of the border nodes and the control plane nodes; nor does it maintain a database of endpoint IDs to fabric edge nodes, which is the function of the LISP mapping system. References:
Cisco DNA Center User Guide, Release 2.2.2.0, Chapter 1: Introduction to Cisco DNA Center,
https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management
Cisco SD-Access Design Guide, Release 2.2.2.0, Chapter 2: SD-Access Fabric Design,
https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/sda-design-guide-2-2-2-0.html#_Toc67188

Explanation
A WAN design is a plan for how to connect multiple sites or locations over a wide area network (WAN). A WAN design can have various benefits, depending on the goals and requirements of the organization. Two of the possible benefits from a WAN design are:
Ensure remote site uptime: A WAN design can help to ensure that remote sites or branches have reliable and consistent connectivity to the central site or the cloud. This can improve the availability and performance of critical applications and services, such as voice, video, collaboration, and data backup. A WAN design can also provide redundancy and resiliency in case of network failures or disasters, by using multiple WAN links, backup routes, or failover mechanisms. For example, SD-WAN is a WAN design that uses software to dynamically route traffic over the best available WAN link, based on the network conditions and the application requirements1.
Prioritize and secure with granular control: A WAN design can also help to prioritize and secure the traffic and applications that flow over the WAN. This can enhance the quality of service (QoS) and the security of the network. A WAN design can use various techniques, such as traffic shaping, policy-based routing, encryption, firewall, or VPN, to classify, prioritize, and secure the WAN traffic according to the business needs and the security policies. For example, TrustSec is a WAN design that uses software-defined segmentation to enforce granular access policies based on the identity and context of users, devices, and applications2.
The other options, provide lower quality service to guest users, reduce cost and increase operational complexity, and lower circuit bandwidth requirements, are not benefits from a WAN design. Providing lower quality service to guest users is not a desirable outcome, as it can affect the user experience and the reputation of the organization. Reducing cost and increasing operational complexity is a trade-off that may not be worth it, as it can create more challenges and risks for the network management and maintenance. Lowering circuit bandwidth requirements is not a benefit in itself, but a means to achieve other benefits, such as reducing cost or improving performance. A WAN design should aim to optimize the bandwidth utilization and allocation, rather than simply lowering it. References := : 1: Cisco SD-WAN Solution Design Guide (CVD) – Cisco1, 2:
Cisco TrustSec Solution Overview – Cisco

Explanation
A Digital Network is a network that is based on the Cisco Digital Network Architecture (Cisco DNA), which is an open and extensible, software-driven network architecture designed to rapidly deliver services that enable IT to innovate faster, reduce costs and complexity, lower risk, and comply with regulatory requirements1. A key function of a Digital Network is centralized provisioning, which allows IT to automate the deployment and configuration of network devices and services using a single platform, such as the Cisco DNA Center2.
Centralized provisioning simplifies network management, reduces human errors, and accelerates network changes.
References:
2: [Cisco DNA Software – Digital Network Architecture – Cisco] : 1: [Cisco Digital Network Architecture]

Explanation/Reference:
Reference: https://sdwan-docs.cisco.com/Product_Documentation/Software_Features/ Release_18.1/04Segmentation/02Configuring_Segmentation_(VPNs)

Explanation
According to the Cisco Enterprise Networks SDA, SDWAN and ISE Exam for System Engineers document1, the three Cisco recommendations on “How to Win” are:
Explain support for 3rd party network devices: Cisco ISE can integrate with more than 60 third-party solutions that span across security and network portfolios. This enablesCisco ISE to leverage the information and capabilities of these solutions to enhance the identity and access management, network visibility and segmentation, threat detection and response, and policy enforcement of the network. By explaining this support, the customer can see the value and flexibility of Cisco ISE in their existing or heterogeneous network environment2.
Explain architectural advantage of holistic Cisco solution: Cisco ISE is part of the Cisco Digital Network Architecture (DNA), which is a comprehensive and open platform that provides end-to-end network automation, assurance, security, and analytics. By explaining the architectural advantage of the holistic Cisco solution, the customer can see how Cisco ISE works seamlessly with other Cisco DNA components, such as Cisco DNA Center, Cisco SD-Access, Cisco SD-WAN, Cisco TrustSec, and Cisco Stealthwatch, to deliver a unified and consistent network experience across wired, wireless, and cloud domains3.
Talk about Cisco’s focus on Security and integration with StealthWatch, Sourcefire, WSA, vulnerability scanner to make smarter policy decisions: Cisco ISE is a core component of the Cisco security portfolio, which provides comprehensive and integrated security solutions for the network. By talking about Cisco’s focus on security and integration with other security products, such as StealthWatch, Sourcefire, WSA, and vulnerability scanner, the customer can see how Cisco ISE can provide enhanced visibility, threat detection, and policy enforcement for the network. For example, Cisco ISE can use the data from StealthWatch to identify anomalous or malicious behavior of the endpoints and apply appropriate network access policies based on the threat level4.
The other options, show case Cisco portfolio or ISE feature set during PoC and demonstrate complex policy flows, rather show case Wizards and enhanced context visibility, are not Cisco recommendations on “How to Win”. Showing case Cisco portfolio or ISE feature set during PoC is a general best practice, but not a specific recommendation for winning the customer. Demonstrating complex policy flows, rather than showing case Wizards and enhanced context visibility, is a counterproductive approach, as it can confuse or overwhelm the customer with technical details, rather than highlighting the benefits and simplicity of Cisco ISE. References
:= : 2: Cisco Identity Services Engine Administrator Guide, Release 2.7 – ISE Security Ecosystem Integration Guides [Cisco Identity Services Engine] – Cisco2, 1: Cisco Enterprise Networks SDA, SDWAN and ISE Exam for System Engineers1, 3: Cisco Identity Services Engine – Cisco3, 4: Cisco Identity Services Engine Administrator Guide, Release 2.7 – Stealthwatch Integration [Cisco Identity Services Engine] – Cisco4

Explanation
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

Explanation
A centralized SD-Access design is where a single fabric domain spans across the main site and all branch sites over the WAN. This design has some challenges, such as:
Since the traffic is encapsulated in VXLAN headers, SD-WAN features such as application-aware routing, QoS, and security policies cannot be applied to the traffic based on the original IP headers. This means that the SD-WAN controller cannot optimize or route the traffic based on the application or user identity. The traffic is treated as a single class of service across the WAN.
The centralized design also introduces a single point of failure and a potential bottleneck at the main site, where the border nodes and the control plane nodes are located. If the main site goes down or the WAN link fails, the branch sites will lose connectivity to the fabric domain and the external networks.
The centralized design also requires a high bandwidth and low latency WAN connection between the main site and the branch sites, which may not be feasible or cost-effective for some scenarios.
References :=
Some possible references are:
Cisco Enterprise Networks SDA, SDWAN and ISE Exam for System Engineers (ENSDENG) Study Guide Cisco SD-Access and SD-WAN Integration Design Guide

Explanation/Reference:
Reference: https://www.slideshare.net/robboyd/techwisetv-workshop-cisco-identity-services-engine-ise slide 3

Explanation
Some of the statements that are true regarding Cisco SD-WAN license tiers are:
With Pro license, control and data policies are supported2. This license tier enables network operators to define and enforce policies for traffic shaping, quality of service (QoS), application optimization, and security2.
With Plus license, split-tunnel is supported3. This license tier enables network operators to use split-tunneling technology to route traffic through different paths based on application or user preferences3.
With Enterprise license, vAnalytics is included4. This license tier enables network operators to use vAnalytics feature to collect and analyze data from various sources such as endpoints, applications, devices, networks, and cloud services4.

Explanation/Reference:
Reference: https://www.cisco.com/c/en_sg/partners/blackbelt/enterprise-networking.html#~stickynav=2

Explanation
ISE automation BYOD flow is a process that allows users to self-enroll their devices to the network without requiring IT intervention. The process consists of three main functions: certificate enrollment, device registration, and supplicant provisioning.
Certificate enrollment is the function that allows users to obtain a digital certificate from a certificate authority (CA) for their devices. This certificate is used to authenticate the device to the network and provide secure communication. ISE supports different CA options, such as Microsoft CA, Cisco ISE CA, or third-party CA .
Device registration is the function that allows users to register their devices to the network and associate them with their identity. This enables ISE to apply policies based on the device type, ownership, and posture. ISE supports different device registration methods, such as portal-based, API-based, or bulk import .
Supplicant provisioning is the function that allows users to install and configure a network access client (supplicant) on their devices. This client is used to connect to the network using the appropriate protocols and settings. ISE supports different supplicant provisioning methods, such as native supplicant, Cisco Network Setup Assistant (NSA), or Cisco AnyConnect Secure Mobility Client (AnyConnect) .
References:
[Cisco Identity Services Engine Administrator Guide, Release 2.7 – BYOD [Cisco Identity Services Engine]] :
[Cisco Identity Services Engine Administrator Guide, Release 2.7 – Certificate Provisioning [Cisco Identity Services Engine]] : [Cisco Identity Services Engine Administrator Guide, Release 2.7 – Device Registration
[Cisco Identity Services Engine]] : [Cisco Identity Services Engine Administrator Guide, Release 2.7 – Supplicant Provisioning [Cisco Identity Services Engine]]

Explanation
https://www.cisco.com/en/US/technologies/tk648/tk365/tk207/technologies_white_paper0900 aecd80243fe7.html The default interval for BFD packets is 1 second. BFD uses Hello packets to detect the liveness and faults on a connection. BFD Hello Interval packet is sent at the default interval of 1000 milliseconds on all connections1. This command can be used to change the hello interval for a transport color. The interval for transmitting and receiving BFD packets can also be configured on the interface level or the BFD session level, depending on the device and the protocol234. The BFD detection time is calculated as the product of the local detection multiplier and the agreed remote transmission interval. The lower the BFD detection time, the faster the BFD session can detect a fault. However, a lower BFD detection time also consumes more system resources and bandwidth. Therefore, the BFD detection time should be configured according to the network situation and performance requirements. References:
1: Bidirectional Forwarding Detection – Cisco
2: Configuring the BFD Detection Time – CloudEngine 16800 … – Huawei
3: Cisco IOS XE Catalyst SD-WAN Qualified Command Reference
4: bfd min-echo-receive-interval – Aruba