Cisco 350-601 Practice Test - Questions Answers, Page 14

In a vPC (Virtual Port Channel) configuration, multicast traffic is handled based on the IGMP (Internet Group Management Protocol) and PIM (Protocol Independent Multicast) configurations. When a host sends traffic to a multicast group, the vPC switches determine the forwarding path based on the multicast routing table and the RPF (Reverse Path Forwarding) check.

Option B is correct because when multicast traffic with source address 10.10.10.10 targeting group 239.1.1.1 is received on Po10 Switch1, the switch will perform an RPF check and forward the traffic out of the interfaces that lead to the Rendezvous Point (RP) and the receivers. This ensures that the multicast traffic is efficiently distributed to all receivers that are part of the multicast group. The traffic would be forwarded out on Po1, which is typically connected to the RP, and Po20, which connects to other receivers in the network.

To ensure that vPC and non-vPC switches receive the same STP bridge ID from the upstream vPC switch peers, the engineer must implement the peer-switch feature on the vPC domain. The peer-switch feature allows the two vPC peer switches to act as a single logical switch for STP purposes, and to use the same bridge ID and priority. This way, the downstream switches will see the vPC peer switches as a single STP root, and will not have any STP loops or inconsistencies. The peer-switch feature also improves the convergence time and reduces the number of STP instances required in the network.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 3: Data Center LAN Network Connectivity, Lesson 3.5: Cisco Nexus 7000 Series Switches

Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 6.x, Chapter: Configuring vPCs, Section: Configuring the Peer Switch Feature

Create a user defined role and add the required privileges.

Assign a role to a user.Comprehensive and Detailed Explanation: = To meet the requirements of adding a new FCoE VLAN to the core switches with restricted read-write access, the network engineer must create a user defined role and assign it to a user. A user defined role is a custom role that can be created to grant specific privileges and permissions to a user, based on the tasks and functions they need to perform. A user defined role can be created using the role command, and then the required privileges can be added using the rule command. For example, to create a role named FCoE-admin and add the privilege to configure FCoE VLANs, the following commands can be used:

role FCoE-admin rule 1 permit read-write feature fcoe rule 2 permit read-write feature vlan

After creating the user defined role, it can be assigned to a user using the username command. For example, to assign the FCoE-admin role to a user named John, the following command can be used:

username John role FCoE-admin

By creating and assigning a user defined role, the network engineer can ensure that the user has the minimum required privileges to perform the FCoE VLAN configuration, without granting them full network-admin access or modifying the existing roles.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 3: Data Center LAN Network Connectivity, Lesson 3.5: Cisco Nexus 7000 Series Switches

Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x, Chapter: Configuring User Accounts and RBAC, Section: Configuring User-Defined Roles

When a VLAN is added to a trunk and it does not appear on the vNIC of an associated server, it typically indicates that the vNIC template is not updating as it should to reflect changes. By changing the template type of Trunk-A to an updating template, any changes made to the trunk configuration, such as adding a new VLAN, will be dynamically applied to all vNICs associated with that template. This action will allow the newly added VLAN to be included in the vNIC configuration without the need to manually update each vNIC or recreate the templates.

The solution that meets the requirements for implementing an automation solution to allow the backup of the configuration of Cisco Nexus series switches to a centralized location is the Guest Shell. The Guest Shell is a Linux-based container that runs on the Cisco Nexus operating system and provides a secure environment for running Python scripts and custom applications. The Guest Shell supports the RPM packaging format, which allows the team-developed custom monitoring scripts to be easily installed and managed. The Guest Shell is isolated from the underlying Cisco Nexus operating system, which means that it has no impact on the operating system if the resource contention occurs. The Guest Shell also allows the use of Python to expand the existing automation framework, such as using the NX-API or the Cisco Nexus Python SDK to interact with the switch configuration and state.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 8: Data Center Automation and Orchestration, Lesson 8.2: Cisco NX-OS Programmability

Cisco Nexus 9000 Series NX-OS Programmability Guide, Release 9.3(x), Chapter: Using Guest Shell

To monitor ingress traffic from SW1 and SW2 port-channel interfaces from SW3, the engineer must implement a configuration that specifies the source interfaces for monitoring and the destination interface where the monitored traffic will be sent. The correct configuration is found in Option D, which includes the commands to create a monitor session, specify the source interfaces as port-channel 1 and port-channel 2 with the 'rx' option to indicate ingress traffic, and set the destination interface to Ethernet 1/4 where the traffic can be analyzed. This setup uses a Switched Port Analyzer (SPAN) or Remote SPAN (RSPAN) to capture and forward the traffic for monitoring purposes.

The attribute that must be selected to implement microsegmentation of endpoints within the same IP subnet using a network-based attribute that allows IP subnet independence is the Tag attribute. The Tag attribute is a user-defined attribute that can be assigned to endpoints based on any criteria, such as location, function, or security level. The Tag attribute can be used to create microsegmentation policies in ACI, which define the rules for communication between endpoints within the same or different bridge domains. The Tag attribute enables IP subnet independence, which means that the microsegmentation policies are not tied to the IP subnet of the endpoints, and can be applied across different subnets or even different fabrics. The Tag attribute also simplifies the management and scalability of microsegmentation policies, as it does not require the use of IP addresses or MAC addresses to identify endpoints.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 6: Data Center Network Connectivity Design, Lesson 6.2: Cisco ACI Overview and Concepts

Cisco Application Centric Infrastructure Fundamentals, Chapter: Endpoint Groups and Microsegmentation, Section: Microsegmentation Using Tags

When configuring a vHBA template in Cisco UCS Manager, the engineer needs to specify the logical addresses used by the vHBA and the path through which the SAN traffic flows. The two resources that must be specified in the vHBA template are the WWN (World Wide Name) and the Fabric ID. The WWN is a unique identifier for the vHBA that is used for zoning and LUN masking in the SAN environment. The WWN can be assigned manually or automatically from a WWN pool. The Fabric ID is a parameter that determines which fabric interconnect (A or B) the vHBA is associated with. The Fabric ID can be set to a specific value or to 'default', which allows the system to choose the best available fabric interconnect based on the availability and load balancing policies.Reference:=

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 5: Cisco Unified Computing System, Lesson 5.2: Cisco UCS B-Series Connectivity

Cisco UCS Manager GUI Configuration Guide, Release 4.0, Chapter: Configuring SAN Connectivity, Section: Creating vHBA Templates