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

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


\n<\/b>Question 261. What is the primary purpose of FCIP<\/b><\/p>\n

    \n
  1. <\/b> Carry Ethernet VLANs only<\/span><\/li>\n
  2. <\/b> Replace server memory<\/span><\/li>\n
  3. <\/b> Transport Fibre Channel across IP networks<\/span><\/li>\n
  4. <\/b> Configure ACI contracts<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. Transport Fibre Channel across IP networks<\/b><\/p>\n

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

    Fibre Channel over IP allows Fibre Channel SAN traffic to travel across an IP network. Cisco MDS switches can establish FCIP tunnels between geographically separated storage fabrics so Fibre Channel frames can cross a routed WAN without requiring a native Fibre Channel connection across the complete distance. This makes FCIP useful for disaster recovery, remote replication, data migration, and geographically distributed storage. After an FCIP link is established, the virtual Fibre Channel connection can participate in normal fabric operations such as FSPF, domain management, zoning, and VSAN transport according to the configured design.<\/span><\/p>\n

    Question 262. What is the default TCP port used by MDS FCIP<\/b><\/p>\n

      \n
    1. <\/b> 3225<\/span><\/li>\n
    2. <\/b> 3260<\/span><\/li>\n
    3. <\/b> 5246<\/span><\/li>\n
    4. <\/b> 443<\/span><\/li>\n<\/ol>\n

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

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

      Cisco MDS uses TCP port 3225 as the default listener port for FCIP connections. Administrators can configure a different listener port when network policy or design requirements make another value necessary, but 3225 is the factory default. FCIP runs Fibre Channel communication across an IP transport, so the TCP connection between the FCIP peers must be permitted through any intervening routed infrastructure or security devices. Firewalls and WAN policies should therefore account for the configured FCIP TCP ports when SAN fabrics are extended between data centers.<\/span><\/p>\n

      Question 263. How many TCP connections does an MDS FCIP link create by default<\/b><\/p>\n

        \n
      1. <\/b> Five<\/span><\/li>\n
      2. <\/b> One<\/span><\/li>\n
      3. <\/b> Four<\/span><\/li>\n
      4. <\/b> Two<\/span><\/li>\n<\/ol>\n

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

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

        Cisco MDS creates two TCP connections for each FCIP link by default. One connection carries Fibre Channel data frames, while the second connection is reserved for Fibre Channel control frames. Separating control traffic helps maintain low latency for important switch to switch fabric protocol communication even when the data connection is carrying substantial storage traffic. Cisco allows the number of TCP connections to be changed for specific performance requirements. Higher bandwidth FCIP designs can benefit from additional TCP connections depending on the platform, WAN characteristics, and configured maximum bandwidth.<\/span><\/p>\n

        Question 264. What does the second default FCIP TCP connection carry<\/b><\/p>\n

          \n
        1. <\/b> Only Ethernet broadcasts<\/span><\/li>\n
        2. <\/b> Fibre Channel control frames<\/span><\/li>\n
        3. <\/b> Server management traffic<\/span><\/li>\n
        4. <\/b> GPU data<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. Fibre Channel control frames<\/b><\/p>\n

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

          The second default FCIP TCP connection is reserved for Fibre Channel control frames, including Class F switch to switch protocol traffic. The other default TCP connection transports normal Fibre Channel data frames. Cisco separates these traffic types so important fabric control communication can receive lower latency instead of competing directly with large storage data transfers. This design helps maintain stable fabric operations over an IP WAN. Administrators can configure additional TCP sessions when required, but the standard FCIP link begins with two connections divided between data and control traffic.<\/span><\/p>\n

          Question 265. What is the default state of FCIP Path MTU discovery<\/b><\/p>\n

            \n
          1. <\/b> Enabled<\/span><\/li>\n
          2. <\/b> Disabled<\/span><\/li>\n
          3. <\/b> Passive<\/span><\/li>\n
          4. <\/b> Manual only<\/span><\/li>\n<\/ol>\n

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

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

            Path MTU discovery is enabled by default for Cisco MDS FCIP connections. It allows TCP to discover the minimum MTU supported across the complete IP path between FCIP endpoints and adjust the maximum TCP segment size accordingly. This helps prevent unnecessary fragmentation when WAN links or intermediate devices support different packet sizes. Cisco documents a default PMTU reset timeout of 3600 seconds. Proper MTU planning remains important because FCIP encapsulation adds overhead and storage applications can be sensitive to inefficient WAN transport behavior.<\/span><\/p>\n

            Question 266. What is the default state of TCP SACK for MDS FCIP<\/b><\/p>\n

              \n
            1. <\/b> Monitor only<\/span><\/li>\n
            2. <\/b> Disabled<\/span><\/li>\n
            3. <\/b> Enabled<\/span><\/li>\n
            4. <\/b> Passive<\/span><\/li>\n<\/ol>\n

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

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

              TCP Selective Acknowledgment is enabled by default on Cisco MDS FCIP connections. SACK improves TCP recovery when several packets are lost within one transmission window. Without selective acknowledgment, the sender has less precise information about which segments were lost and may require additional round trips to recover them. With SACK, the receiver identifies the missing portions so the sender can retransmit only the required data. This behavior is particularly useful across WAN links where latency makes inefficient retransmission more expensive and can reduce storage replication performance.<\/span><\/p>\n

              Question 267. What is the default FCIP TCP keepalive timeout<\/b><\/p>\n

                \n
              1. <\/b> 30 seconds<\/span><\/li>\n
              2. <\/b> 60 seconds<\/span><\/li>\n
              3. <\/b> 120 seconds<\/span><\/li>\n
              4. <\/b> 300 seconds<\/span><\/li>\n<\/ol>\n

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

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

                Cisco MDS FCIP uses a default TCP keepalive idle interval of 60 seconds. When the connection remains idle for the configured interval, the system sends a series of keepalive probes to determine whether the remote endpoint is still reachable. Cisco documents eight probes at one second intervals after the idle period. If no response is received and the connection remains idle, the FCIP link is automatically closed. This mechanism helps detect failed or unreachable FCIP peers even when no storage data is actively crossing the WAN connection.<\/span><\/p>\n

                Question 268. What is the default minimum FCIP TCP retransmit time in MDS NX OS 9.4.2 and later<\/b><\/p>\n

                  \n
                1. <\/b> 500 milliseconds<\/span><\/li>\n
                2. <\/b> 200 milliseconds<\/span><\/li>\n
                3. <\/b> 100 milliseconds<\/span><\/li>\n
                4. <\/b> 50 milliseconds<\/span><\/li>\n<\/ol>\n

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

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

                  Beginning with Cisco MDS NX OS Release 9.4.2, the default minimum TCP retransmission timeout for FCIP is 50 milliseconds. Earlier releases used a default value of 200 milliseconds. The retransmission timer determines how long TCP waits before retransmitting data when an acknowledgment is not received. Reducing the minimum value can improve loss recovery on modern lower latency networks, although overly aggressive retransmission behavior can increase unnecessary network traffic. Designers should use settings appropriate to the actual WAN latency, packet loss characteristics, and FCIP performance requirements.<\/span><\/p>\n

                  Question 269. What is the purpose of FCIP Write Acceleration<\/b><\/p>\n

                    \n
                  1. <\/b> Increase Fibre Channel domain IDs<\/span><\/li>\n
                  2. <\/b> Compress zoning databases<\/span><\/li>\n
                  3. <\/b> Reduce WAN latency impact on writes<\/span><\/li>\n
                  4. <\/b> Replace TCP<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 3. Reduce WAN latency impact on writes<\/b><\/p>\n

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

                    FCIP Write Acceleration improves storage write performance across long distance IP networks by reducing the effect of WAN round trip latency on SCSI write operations. Cisco describes the feature as acknowledging write frames closer to the sending side so the host can continue transmitting data without waiting for every normal long distance storage exchange to complete. This can significantly increase throughput for replication and other write intensive workloads across high latency links. Write Acceleration should be deployed according to Cisco path requirements because incorrect multipath behavior can disrupt accelerated storage exchanges.<\/span><\/p>\n

                    Question 270. What is the default state of FCIP Write Acceleration<\/b><\/p>\n

                      \n
                    1. <\/b> Disabled<\/span><\/li>\n
                    2. <\/b> Enabled<\/span><\/li>\n
                    3. <\/b> Mandatory<\/span><\/li>\n
                    4. <\/b> Automatic<\/span><\/li>\n<\/ol>\n

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

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

                      FCIP Write Acceleration is disabled by default on Cisco MDS FCIP interfaces. Administrators must explicitly enable the feature when they want to reduce the effect of WAN latency on storage write operations. Cisco also requires the capability to be configured appropriately at both ends of the FCIP link. Write Acceleration is therefore not automatically activated simply because an FCIP tunnel exists. Designers should enable it only after validating the traffic path, supported hardware, software requirements, and multipath behavior because accelerated exchanges have stricter forwarding requirements than ordinary FCIP traffic.<\/span><\/p>\n

                      Question 271. Where must FCIP Write Acceleration be enabled<\/b><\/p>\n

                        \n
                      1. <\/b> On the host only<\/span><\/li>\n
                      2. <\/b> On the target only<\/span><\/li>\n
                      3. <\/b> On the IP router only<\/span><\/li>\n
                      4. <\/b> On both FCIP endpoints<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 4. On both FCIP endpoints<\/b><\/p>\n

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

                        Cisco requires Write Acceleration to be enabled on both ends of the FCIP link. The feature depends on coordinated behavior between the host side and target side FCIP devices to accelerate storage write exchanges correctly. Enabling the setting on only one endpoint does not provide operational Write Acceleration. The complete forwarding path must also satisfy Cisco design requirements so commands and responses remain on the appropriate FCIP connection or supported port channel. This makes Write Acceleration an end to end FCIP design consideration rather than a simple local interface optimization.<\/span><\/p>\n

                        Question 272. What should be avoided when using FCIP Write Acceleration<\/b><\/p>\n

                          \n
                        1. <\/b> TCP SACK<\/span><\/li>\n
                        2. <\/b> FSPF equal cost paths<\/span><\/li>\n
                        3. <\/b> Fibre Channel zoning<\/span><\/li>\n
                        4. <\/b> VSANs<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. FSPF equal cost paths<\/b><\/p>\n

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

                          Cisco states that FCIP Write Acceleration should not operate across FSPF equal cost paths. Accelerated commands and corresponding responses must follow the same FCIP link or supported FCIP port channel. If several equal cost FCIP paths exist, traffic associated with one exchange can take different paths, which can result in SCSI discovery problems or failed read and write operations. Designers should therefore make FSPF routing deterministic for accelerated flows. Supported active FCIP port channels can provide redundancy and bandwidth while maintaining the path behavior required by Write Acceleration.<\/span><\/p>\n

                          Question 273. What does FCIP Tape Acceleration improve<\/b><\/p>\n

                            \n
                          1. <\/b> Ethernet routing<\/span><\/li>\n
                          2. <\/b> Server BIOS performance<\/span><\/li>\n
                          3. <\/b> Tape backup and archive transfers<\/span><\/li>\n
                          4. <\/b> ACI endpoint learning<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. Tape backup and archive transfers<\/b><\/p>\n

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

                            FCIP Tape Acceleration is designed to improve tape backup and archive performance across long distance WAN links. Tape applications commonly operate sequentially and can have only a limited number of outstanding SCSI write operations. Normal WAN latency can therefore have a large impact because each operation may wait for remote storage responses. Cisco Tape Acceleration reduces this latency effect and allows data to stream more efficiently from the host toward the remote tape system. The feature is especially useful for geographically separated backup environments that transport Fibre Channel tape traffic through FCIP.<\/span><\/p>\n

                            Question 274. What is the default state of FCIP compression<\/b><\/p>\n

                              \n
                            1. <\/b> Disabled<\/span><\/li>\n
                            2. <\/b> Enabled<\/span><\/li>\n
                            3. <\/b> Mandatory<\/span><\/li>\n
                            4. <\/b> Dynamic<\/span><\/li>\n<\/ol>\n

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

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

                              FCIP compression is disabled by default. When enabled on supported Cisco MDS platforms, the feature compresses IP packets traveling across the FCIP connection. Compression can reduce WAN bandwidth consumption when the storage data contains information that compresses effectively. However, compression requires processing resources and does not always provide the same benefit for data that is already compressed or encrypted. Cisco provides different compression behavior according to supported platform and release capabilities. Designers should evaluate both WAN bandwidth savings and processing overhead before enabling FCIP compression in a production storage replication design.<\/span><\/p>\n

                              Question 275. Which algorithm is documented for traditional MDS FCIP compression<\/b><\/p>\n

                                \n
                              1. <\/b> AES<\/span><\/li>\n
                              2. <\/b> LZS<\/span><\/li>\n
                              3. <\/b> SHA<\/span><\/li>\n
                              4. <\/b> RSA<\/span><\/li>\n<\/ol>\n

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

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

                                Cisco documentation identifies the Lempel Ziv Stac algorithm for traditional MDS FCIP compression. The feature compresses FCIP packets to reduce the amount of data transmitted over the WAN. Cisco historically provided modes that favored either higher throughput or a higher compression ratio. The best choice depends on WAN bandwidth, available processing capacity, and the compressibility of the storage workload. Compression should not be assumed to help every application because already compressed data may provide little reduction. Proper testing is recommended before using compression as part of a production FCIP performance strategy.<\/span><\/p>\n

                                Question 276. What happens if both FCIP endpoints are configured only in passive TCP mode<\/b><\/p>\n

                                  \n
                                1. <\/b> Five connections are created<\/span><\/li>\n
                                2. <\/b> The data path becomes Fibre Channel native<\/span><\/li>\n
                                3. <\/b> Write Acceleration starts<\/span><\/li>\n
                                4. <\/b> The TCP connection is not initiated<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 4. The TCP connection is not initiated<\/b><\/p>\n

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

                                  In passive FCIP TCP mode, a Cisco MDS switch waits for its peer to initiate the TCP connection instead of actively opening the connection itself. Cisco specifically warns not to configure both ends of the same FCIP link as passive. If both devices are waiting for the other endpoint to initiate communication, no TCP session begins and the FCIP link cannot establish. At least one endpoint therefore needs active connection behavior. Active mode is the default behavior and causes the switch to attempt the IP connection to its configured FCIP peer.<\/span><\/p>\n

                                  Question 277. What does ACI Rogue Endpoint Control quarantine<\/b><\/p>\n

                                    \n
                                  1. <\/b> Only the misbehaving endpoint<\/span><\/li>\n
                                  2. <\/b> The entire tenant<\/span><\/li>\n
                                  3. <\/b> Every endpoint in the VRF<\/span><\/li>\n
                                  4. <\/b> All leaf ports<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. Only the misbehaving endpoint<\/b><\/p>\n

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

                                    Cisco ACI Rogue Endpoint Control is designed to limit the impact of an endpoint that moves excessively between interfaces or locations. Instead of disabling endpoint learning for the complete bridge domain, the feature can quarantine only the specific MAC or IP endpoint causing the problem. Cisco keeps the endpoint associated with a fixed tunnel endpoint and port for a configured period while learning for that endpoint is suppressed. This provides more granular protection than mechanisms that affect an entire bridge domain and can reduce the impact of one malfunctioning server or incorrect network teaming configuration.<\/span><\/p>\n

                                    Question 278. What can ACI Endpoint Move Dampening disable when excessive moves occur<\/b><\/p>\n

                                      \n
                                    1. <\/b> All spine routing<\/span><\/li>\n
                                    2. <\/b> Every tenant<\/span><\/li>\n
                                    3. <\/b> Learning on the bridge domain<\/span><\/li>\n
                                    4. <\/b> The APIC cluster<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 3. Learning on the bridge domain<\/b><\/p>\n

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

                                      Endpoint Move Dampening monitors aggregate endpoint moves within an ACI bridge domain. When the configured move frequency threshold is exceeded, ACI can disable learning on the affected bridge domain for a configured hold interval. The endpoint that is moving too frequently is also flushed. This mechanism helps protect the fabric from excessive learning updates caused by loops, incorrect server teaming, or unstable endpoint attachment. Because the action can affect the entire bridge domain, Cisco also provides more granular Rogue Endpoint Control for scenarios where administrators want to quarantine only the individual misbehaving endpoint.<\/span><\/p>\n

                                      Question 279. What is the default ACI hold interval after learning is disabled by endpoint protection<\/b><\/p>\n

                                        \n
                                      1. <\/b> 30 seconds<\/span><\/li>\n
                                      2. <\/b> 60 seconds<\/span><\/li>\n
                                      3. <\/b> 120 seconds<\/span><\/li>\n
                                      4. <\/b> 300 seconds<\/span><\/li>\n<\/ol>\n

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

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

                                        Cisco documents a default hold interval of 300 seconds for endpoint protection behavior that disables bridge domain learning. The hold interval is configured through the endpoint retention policy associated with the bridge domain. It applies to mechanisms such as Endpoint Move Dampening and Endpoint Loop Protection when their action is to stop learning. After the hold period expires, normal endpoint learning can resume. Designers can modify the interval according to operational requirements, but the value should be long enough to stop repeated instability while avoiding unnecessary disruption to legitimate endpoint movement.<\/span><\/p>\n

                                        Question 280. What is the default local endpoint aging interval in ACI<\/b><\/p>\n

                                          \n
                                        1. <\/b> 300 seconds<\/span><\/li>\n
                                        2. <\/b> 900 seconds<\/span><\/li>\n
                                        3. <\/b> 630 seconds<\/span><\/li>\n
                                        4. <\/b> 1800 seconds<\/span><\/li>\n<\/ol>\n

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

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

                                          Cisco ACI uses a default local endpoint aging interval of 900 seconds when no customized endpoint retention policy is configured. Endpoint aging removes stale endpoint information after the endpoint has not been observed for the configured period. Cisco distinguishes local endpoint aging from remote endpoint aging and bounce entry aging, which use different default values and can be configured at different policy levels. Correct endpoint aging helps prevent obsolete MAC and IP information from remaining indefinitely in the fabric while still allowing actively used endpoints to remain learned and reachable.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Cisco CCNP Data Center 300-610 Exam Dumps and Practice Test Dumps. Question 261. What is the primary purpose of FCIP Carry Ethernet VLANs only Replace server memory Transport Fibre Channel across IP networks Configure ACI contracts Correct Answer: 3. Transport Fibre Channel across IP networks Explanation: Fibre Channel over IP allows Fibre Channel […]<\/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\/22905"}],"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=22905"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22905\/revisions"}],"predecessor-version":[{"id":22906,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22905\/revisions\/22906"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}