{"id":22661,"date":"2026-09-26T06:50:37","date_gmt":"2026-09-26T06:50:37","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22661"},"modified":"2026-09-26T06:50:37","modified_gmt":"2026-09-26T06:50:37","slug":"cisco-ccnp-300-425-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccnp-300-425-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"Cisco CCNP 300-425 Practice Test Questions and Exam Dumps Part14 Q261-280"},"content":{"rendered":"

View Full <\/b>Cisco CCNP 300-425 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Question 261. Which multicast forwarding mode does Cisco recommend for best wireless performance<\/b><\/p>\n

    \n
  1. <\/b> Unicast forwarding<\/span><\/li>\n
  2. <\/b> Broadcast forwarding<\/span><\/li>\n
  3. <\/b> Multicast forwarding<\/span><\/li>\n
  4. <\/b> Local forwarding<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. Multicast forwarding<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    Cisco recommends multicast forwarding mode when the underlying network infrastructure supports multicast routing. This method allows the controller to send a single multicast stream toward multiple access points instead of creating a separate unicast copy for every AP. The approach can significantly reduce controller and network bandwidth consumption when applications use multicast extensively. It is especially useful for multicast video, large IPv6 wireless environments, and Bonjour deployments without mDNS proxy operation. The routed network between the controller and AP subnets must support multicast correctly or the wireless multicast traffic cannot reach the access points.<\/span><\/p>\n

    Question 262. Which range does Cisco recommend for a private CAPWAP multicast group address<\/b><\/p>\n

      \n
    1. <\/b> 239.0.0.0 through 239.255.255.255<\/span><\/li>\n
    2. <\/b> 127.0.0.0 through 127.255.255.255<\/span><\/li>\n
    3. <\/b> 169.254.0.0 through 169.254.255.255<\/span><\/li>\n
    4. <\/b> 192.168.0.0 through 192.168.255.255<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. 239.0.0.0 through 239.255.255.255<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      Cisco recommends choosing the CAPWAP multicast group from the private multicast address range beginning with 239. Certain portions of that range should still be avoided because they can create undesirable Layer 2 flooding behavior. The selected address is used by the controller to distribute multicast traffic toward access points. Designers must also make sure the chosen address is not already being used by another application or protocol. Selecting a unique and appropriate multicast group prevents conflicts and supports predictable multicast forwarding throughout the wireless infrastructure.<\/span><\/p>\n

      Question 263. How should CAPWAP multicast group addresses be assigned to multiple WLCs<\/b><\/p>\n

        \n
      1. <\/b> Use the same address on every WLC<\/span><\/li>\n
      2. <\/b> Use the mDNS address on every WLC<\/span><\/li>\n
      3. <\/b> Use a broadcast address<\/span><\/li>\n
      4. <\/b> Use a different multicast address on each WLC<\/span><\/li>\n<\/ol>\n

        Correct Answer: 4. Use a different multicast address on each WLC<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        Cisco recommends assigning a different CAPWAP multicast group address to each wireless controller. Reusing the same multicast address on multiple controllers can result in multicast packet duplication and make forwarding behavior more difficult to control. Each controller uses its configured multicast group to distribute wireless multicast traffic efficiently to its associated access points. Designers should choose addresses from the recommended private multicast range and verify that the selected groups do not conflict with existing network applications. Correct multicast address planning is therefore an important component of controller and routed infrastructure design.<\/span><\/p>\n

        Question 264. What does IGMP snooping help reduce<\/b><\/p>\n

          \n
        1. <\/b> Client authentication<\/span><\/li>\n
        2. <\/b> Unnecessary multicast transmission<\/span><\/li>\n
        3. <\/b> AP certificate usage<\/span><\/li>\n
        4. <\/b> Controller redundancy<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. Unnecessary multicast transmission<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          IGMP snooping improves multicast efficiency by tracking which clients have joined particular IPv4 multicast groups. The wireless infrastructure can then avoid transmitting multicast frames from access points that do not have interested clients. This reduces unnecessary airtime consumption and limits traffic on the wired network. Cisco recommends IGMP snooping in most multicast environments when application behavior supports proper group membership signaling. Designers should still validate multicast applications because some implementations do not correctly send or refresh group membership messages, which can cause multicast forwarding entries to expire unexpectedly.<\/span><\/p>\n

          Question 265. Which UDP port does mDNS use<\/b><\/p>\n

            \n
          1. <\/b> 5353<\/span><\/li>\n
          2. <\/b> 5246<\/span><\/li>\n
          3. <\/b> 1812<\/span><\/li>\n
          4. <\/b> 16666<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. 5353<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            Multicast DNS uses UDP port 5353 for Bonjour service announcements and service discovery queries. Devices such as printers, media receivers, and collaboration systems use mDNS to advertise services and allow clients to locate them without a traditional DNS server. Basic mDNS traffic is link local, so it normally remains within the local Layer 2 network. Cisco Catalyst 9800 controllers can provide an mDNS gateway function when services and clients need to discover one another across separate VLANs or subnets. Understanding the mDNS port and scope is important when designing firewall and segmentation policies.<\/span><\/p>\n

            Question 266. Which IPv4 multicast address is used by Bonjour mDNS<\/b><\/p>\n

              \n
            1. <\/b> 224.0.0.1<\/span><\/li>\n
            2. <\/b> 239.255.255.250<\/span><\/li>\n
            3. <\/b> 224.0.0.251<\/span><\/li>\n
            4. <\/b> 255.255.255.255<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. 224.0.0.251<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              Bonjour mDNS uses the IPv4 multicast address 224.0.0.251. Service advertisements and discovery queries are sent to this address using UDP port 5353. Because this is a link local multicast address, the traffic normally does not cross routed boundaries. That behavior works well in small local networks but creates challenges in enterprises where printers, displays, and clients may reside on different VLANs. The Catalyst 9800 mDNS gateway addresses this limitation by learning service advertisements and making selected services discoverable across network segments according to configured policies.<\/span><\/p>\n

              Question 267. What problem does the Catalyst 9800 mDNS gateway solve<\/b><\/p>\n

                \n
              1. <\/b> DFS radar detection<\/span><\/li>\n
              2. <\/b> Service discovery across different subnets<\/span><\/li>\n
              3. <\/b> AP image upgrades<\/span><\/li>\n
              4. <\/b> Controller high availability<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. Service discovery across different subnets<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                Traditional mDNS is limited to the local Layer 2 broadcast domain, which prevents devices on separate subnets from directly discovering one another. The Catalyst 9800 mDNS gateway solves this limitation by learning and caching Bonjour service advertisements and responding to appropriate service queries across segmented networks. This allows a wireless client on one subnet to discover an approved printer, display, or other service located on another subnet. Administrators can use service policies and location filtering to control which services are visible, preventing the enterprise from simply flooding every Bonjour advertisement across the entire network.<\/span><\/p>\n

                Question 268. What is the default state of the Catalyst 9800 mDNS gateway<\/b><\/p>\n

                  \n
                1. <\/b> Enabled globally<\/span><\/li>\n
                2. <\/b> Enabled on guest WLANs<\/span><\/li>\n
                3. <\/b> Enabled only for AirPlay<\/span><\/li>\n
                4. <\/b> Disabled<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. Disabled<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  The Catalyst 9800 mDNS gateway is disabled by default and must be explicitly enabled when cross subnet Bonjour service discovery is required. This differs from simple mDNS bridging, which is enabled by default for WLAN traffic within the same Layer 2 domain. Enabling the gateway allows the controller to learn service advertisements and respond to discovery queries across network segments. Designers should configure service policies carefully so only required service types are shared. Controlled gateway operation is more scalable and secure than indiscriminately extending all multicast service discovery traffic across the enterprise.<\/span><\/p>\n

                  Question 269. What is the default state of mDNS bridging on Catalyst 9800 WLANs<\/b><\/p>\n

                    \n
                  1. <\/b> Disabled<\/span><\/li>\n
                  2. <\/b> Enabled only with guest access<\/span><\/li>\n
                  3. <\/b> Enabled<\/span><\/li>\n
                  4. <\/b> Available only with FlexConnect<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 3. Enabled<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    Catalyst 9800 enables mDNS bridging by default for packets received on wired and wireless interfaces associated with each WLAN. Bridging allows Bonjour traffic to remain available within the same Layer 2 broadcast domain without requiring the mDNS gateway function to be enabled. If CAPWAP multicast forwarding is active, mDNS packets can be distributed toward APs through the configured AP multicast group. Otherwise, the controller can send individual copies through CAPWAP unicast tunnels. Administrators can disable mDNS bridging on individual WLANs when the service discovery traffic is unnecessary.<\/span><\/p>\n

                    Question 270. What must a custom mDNS service policy contain<\/b><\/p>\n

                      \n
                    1. <\/b> Both IN and OUT service lists<\/span><\/li>\n
                    2. <\/b> Only an IN service list<\/span><\/li>\n
                    3. <\/b> Only an OUT service list<\/span><\/li>\n
                    4. <\/b> A mobility anchor<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. Both IN and OUT service lists<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      A custom Catalyst 9800 mDNS service policy requires both inbound and outbound service lists. The inbound list controls which service advertisements the mDNS gateway can learn. Without an inbound list, the gateway cannot learn the relevant services. The outbound list controls which learned services can be returned or announced to clients. Without an outbound list, the controller cannot provide those services in response to discovery requests. Using both directions allows administrators to create precise Bonjour policies that control service learning and service visibility across wireless and wired network segments.<\/span><\/p>\n

                      Question 271. Which engine identifies applications for Cisco AVC<\/b><\/p>\n

                        \n
                      1. <\/b> RRM<\/span><\/li>\n
                      2. <\/b> CAPWAP<\/span><\/li>\n
                      3. <\/b> DHCP<\/span><\/li>\n
                      4. <\/b> NBAR2<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 4. NBAR2<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        Cisco Application Visibility and Control uses the NBAR2 engine to identify applications and protocols in network traffic. NBAR2 performs deep packet inspection and marks individual flows according to the detected application. This information provides visibility into what wireless users are actually running instead of showing only addresses and port numbers. Administrators can then use recognized application information for reporting and policy control. AVC combines NBAR based classification with Flexible NetFlow so application statistics can be collected, displayed, and exported to external analysis systems.<\/span><\/p>\n

                        Question 272. Which technology reports AVC traffic statistics<\/b><\/p>\n

                          \n
                        1. <\/b> STP<\/span><\/li>\n
                        2. <\/b> Flexible NetFlow<\/span><\/li>\n
                        3. <\/b> HSRP<\/span><\/li>\n
                        4. <\/b> CDP<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. Flexible NetFlow<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          Cisco AVC integrates with Flexible NetFlow to report application and protocol statistics. NBAR2 first identifies the application associated with each traffic flow, and Flexible NetFlow provides the framework for recording and exporting information about those flows. Administrators can view application visibility on the controller or send NetFlow information to supported external collectors for additional analysis. This combination allows wireless designers and operators to understand actual application use and create policy decisions based on recognized traffic rather than relying only on basic address and port information.<\/span><\/p>\n

                          Question 273. What technique does AVC use to identify applications<\/b><\/p>\n

                            \n
                          1. <\/b> DNS recursion<\/span><\/li>\n
                          2. <\/b> Radio scanning<\/span><\/li>\n
                          3. <\/b> Deep packet inspection<\/span><\/li>\n
                          4. <\/b> DHCP snooping<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. Deep packet inspection<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            Application Visibility and Control uses deep packet inspection to identify the applications generating wireless network traffic. The NBAR2 engine analyzes traffic flows and attempts to recognize the protocol or application based on packet characteristics rather than relying solely on basic port numbers. This provides more meaningful visibility because many modern applications use dynamic ports or share common transport protocols. Once traffic is identified, the information can be reported through Flexible NetFlow and used in application aware policy rules. Encryption can reduce classification accuracy because important application information may no longer be visible to the inspection engine.<\/span><\/p>\n

                            Question 274. What can AVC control rules do to selected application traffic<\/b><\/p>\n

                              \n
                            1. <\/b> Police bandwidth<\/span><\/li>\n
                            2. <\/b> Change AP antennas<\/span><\/li>\n
                            3. <\/b> Modify floor plans<\/span><\/li>\n
                            4. <\/b> Increase PoE power<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. Police bandwidth<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              AVC provides more than application visibility. Administrators can create control rules that apply policing to recognized applications and therefore limit the amount of bandwidth certain traffic can consume. This can help protect important applications from nonessential traffic and prevent individual applications from overwhelming limited wireless or WAN capacity. Cisco notes that application bandwidth contracts can coexist with per client downstream rate limiting. For the control portion of AVC to operate, application visibility and Flexible NetFlow must be configured so traffic can first be identified correctly before the policy action is applied.<\/span><\/p>\n

                              Question 275. Which traffic type is not supported by Catalyst 9800 AVC<\/b><\/p>\n

                                \n
                              1. <\/b> TCP traffic<\/span><\/li>\n
                              2. <\/b> UDP traffic<\/span><\/li>\n
                              3. <\/b> Unicast traffic<\/span><\/li>\n
                              4. <\/b> Multicast traffic<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. Multicast traffic<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                Cisco lists multicast traffic as unsupported for Catalyst 9800 Application Visibility and Control. AVC is designed to classify and report supported client traffic flows using NBAR and Flexible NetFlow. Because multicast is not supported by this feature, administrators should not expect AVC application policies to classify or control multicast application streams in the same way as supported unicast flows. Multicast applications should instead be addressed through the controller multicast architecture, IGMP behavior, wireless QoS, and other multicast specific design mechanisms appropriate to the deployment.<\/span><\/p>\n

                                Question 276. How many rules can an AVC profile support including the default DSCP rule<\/b><\/p>\n

                                  \n
                                1. <\/b> 10<\/span><\/li>\n
                                2. <\/b> 23<\/span><\/li>\n
                                3. <\/b> 50<\/span><\/li>\n
                                4. <\/b> 100<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. 23<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  Cisco states that an AVC profile supports a maximum of 23 rules when AVC is enabled, and this total includes the default DSCP rule. If an administrator creates more than 23 rules, the AVC policy is not sent to the access point. This limit makes policy planning important because application controls should focus on meaningful business requirements rather than creating excessive individual rules. Designers should group requirements where practical and verify the resulting policy deployment on the AP. A configuration appearing on the controller does not provide the intended behavior if the policy cannot be successfully installed on the access point.<\/span><\/p>\n

                                  Question 277. Which deployment mode supports AVC IPv6 packet classification<\/b><\/p>\n

                                    \n
                                  1. <\/b> Local mode<\/span><\/li>\n
                                  2. <\/b> FlexConnect mode only<\/span><\/li>\n
                                  3. <\/b> Fabric mode only<\/span><\/li>\n
                                  4. <\/b> Sniffer mode<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. Local mode<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    Cisco supports IPv6 packet classification for AVC in Local mode. This allows the controller based architecture to identify supported IPv6 application flows using the AVC classification framework. Cisco specifically notes restrictions for FlexConnect and Fabric deployments where IPv6 packet classification is not supported for AVC. Designers planning application visibility should therefore verify the forwarding model and traffic protocol requirements before assuming the same AVC capabilities exist in every wireless architecture. Feature differences between Local, FlexConnect, and Fabric modes can influence which design best satisfies application monitoring requirements.<\/span><\/p>\n

                                    Question 278. Where is AVC IPv6 packet classification not supported<\/b><\/p>\n

                                      \n
                                    1. <\/b> Local mode<\/span><\/li>\n
                                    2. <\/b> Local mode with central switching<\/span><\/li>\n
                                    3. <\/b> FlexConnect and Fabric modes<\/span><\/li>\n
                                    4. <\/b> Local mode on Catalyst APs<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 3. FlexConnect and Fabric modes<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      Cisco lists IPv6 packet classification as unsupported for AVC in FlexConnect and Fabric modes. The restriction also includes ICMPv6 classification. Local mode supports IPv6 AVC classification. This difference matters when an enterprise wants application visibility for an IPv6 client population across branch or fabric wireless deployments. Designers should verify feature support against the forwarding architecture rather than assuming a feature behaves identically in all controller modes. If IPv6 application visibility is a firm requirement, the chosen wireless design and telemetry architecture must support that requirement from the beginning.<\/span><\/p>\n

                                      Question 279. What must be configured for the AVC control function to operate<\/b><\/p>\n

                                        \n
                                      1. <\/b> Application visibility with Flexible NetFlow<\/span><\/li>\n
                                      2. <\/b> Guest anchoring<\/span><\/li>\n
                                      3. <\/b> AP sniffer mode<\/span><\/li>\n
                                      4. <\/b> Hyperlocation<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. Application visibility with Flexible NetFlow<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        Cisco states that application visibility with Flexible NetFlow must be configured for the control portion of AVC to function. The wireless system must first identify applications before it can apply application specific QoS and policing rules. NBAR performs application recognition, while Flexible NetFlow supplies the traffic visibility framework used by AVC. Once the application is identified, administrators can apply controls such as bandwidth limits. Without the visibility portion, the infrastructure lacks the required application classification information and therefore cannot apply the intended application aware control policy correctly.<\/span><\/p>\n

                                        Question 280. What can reduce NBAR application classification accuracy<\/b><\/p>\n

                                          \n
                                        1. <\/b> Lower AP mounting height<\/span><\/li>\n
                                        2. <\/b> Smaller DHCP scopes<\/span><\/li>\n
                                        3. <\/b> Longer SSID names<\/span><\/li>\n
                                        4. <\/b> Encrypted QUIC or DoH traffic<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4. Encrypted QUIC or DoH traffic<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          Encryption can make NBAR application identification less accurate because deep packet inspection cannot examine information that is hidden inside encrypted traffic. Cisco specifically notes that SaaS applications using end to end encryption, QUIC, or DNS over HTTPS can create classification challenges. When protocols such as QUIC operate without visible server name information, NBAR may not determine the correct application protocol identifier. Wireless designers using AVC should therefore recognize that application visibility is not perfect and that modern encryption increasingly limits what traditional packet inspection can identify reliably.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Cisco CCNP 300-425 Exam Dumps and Practice Test Dumps. Question 261. Which multicast forwarding mode does Cisco recommend for best wireless performance Unicast forwarding Broadcast forwarding Multicast forwarding Local forwarding Correct Answer: 3. Multicast forwarding Explanation: Cisco recommends multicast forwarding mode when the underlying network infrastructure supports multicast routing. This method allows the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22661"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=22661"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22661\/revisions"}],"predecessor-version":[{"id":22662,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22661\/revisions\/22662"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22661"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22661"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22661"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}