300-101試験の合格の前提条件はCCNA Routing and Switching 認定またはいずれかの CCIE 認定です。
CCNP Routing and Switching試験コンビネーションツールで、CCNP Routing and Switching 認定の取得に必要な試験を確認できます。
CCNP Routing and Switching資格300-101（Implementing Cisco IP Routing）試験を目前に控えても、ちゃんと試験に準備するチャンスもあります。
Testpassportは、より良いCCNP Routing and Switching資格300-101問題集を作成するために、それは同じ選択、試験に合格するためにあなたに合った唯一の方法は特別な訓練の唯一の30時間、時間とたくさんのお金をする必要があり、あなたは簡単に出席するためにあなたの最初の時間を渡すことができます。
CCNP Routing and Switching資格300-101試験概要：
試験番号：300-101 ROUTE
試験名称：Implementing Cisco IP Routing
関連資格：CCNP Routing and Switching
CCDP
試験時間：120 分
試験数：45 – 65 問
試験言語：日本語、英語
試験登録：Pearson VUE
ROUTE 300-101は、ルーティングに関する知識とスキルを証明する試験です。
CCNP Routing and Switching資格300-101認定試験の合格者は、高度な IP アドレッシングとルーティングを使用して、拡張性とセキュリティに優れたシスコ ルータを LAN、WAN、IPv6 に接続する能力があると認定されます。
TestpassportはROUTE 300-101（Implementing Cisco IP Routing）試験に関する正確かつ詳細なトレーニング資料を提供します。Testpassportによって提供される300-101 ROUTE試験情報を使用することは問題ではない、あなたが高得点で試験に合格することができます。
CCNP Routing and Switching資格300-101試験の出題内容：
1.0 ネットワークの基本事項 10%
2.0 レイヤ 2 テクノロジー 10%
3.0 レイヤ 3 テクノロジー 40%
4.0 VPN テクノロジー 10%
5.0 インフラストラクチャのセキュリティ 10%
6.0 インフラストラクチャ サービス 20%
TestpassportはCCNP Routing and Switching資格300-101認定試験の情報源を提供するための最良のウェブサイトであることが証明されています。弊社のROUTE 300-101勉强資料の中の問題と解答は試験の全部内容を覆い、1回で試験に合格することを保証します。
最新の300-101練習問題集を提供し、300-101無料サンプルをダウンロードできます。
1.A network engineer notices that transmission rates of senders of TCP traffic sharply increase and
decrease simultaneously during periods of congestion.
Which condition causes this?
A. global synchronization
B. tail drop
C. random early detection
D. queue management algorithm
Answer: A
Explanation:
TCP global synchronization in computer networks can happen to TCP/IP flows during periods of
congestion because each sender will reduce their transmission rate at the same time when packet loss
occurs. Routers on the Internet normally have packet queues, to allow them to hold packets when the
network is busy, rather than discarding them.
Because routers have limited resources, the size of these queues is also limited. The simplest technique
to limit queue size is known as tail drop. The queue is allowed to fill to its maximum size, and then any
new packets are simply discarded, until there is space in the queue again. This causes problems when
used on TCP/IP routers handling multiple TCP streams, especially when bursty traffic is present. While
the network is stable, the queue is constantly full, and there are no problems except that the full queue
results in high latency. However, the introduction of a sudden burst of traffic may cause large numbers of
established, steady streams to lose packets simultaneously.
Reference: http://en.wikipedia.org/wiki/TCP_global_synchronization
2.Which three problems result from application mixing of UDP and TCP streams within a network with no
QoS? (Choose three.)
A. starvation
B. jitter
C. latency
D. windowing
E. lower throughput
Answer: A,C,E
Explanation:
It is a general best practice not to mix TCP-based traffic with UDP-based traffic (especially streaming
video) within a single service provider class due to the behaviors of these protocols during periods of
congestion. Specifically, TCP transmitters will throttle-back flows when drops have been detected.
Although some UDP applications have application-level windowing, flow control, and retransmission
capabilities, most UDP transmitters are completely oblivious to drops and thus never lower transmission
rates due to dropping. When TCP flows are combined with UDP flows in a single service provider class
and the class experiences congestion, then TCP flows will continually lower their rates, potentially giving
up their bandwidth to drop-oblivious UDP flows. This effect is called TCP-starvation/UDP-dominance. Thiscan increase latency and lower the overall throughput. TCP-starvation/UDP-dominance likely occurs if
(TCP-based) mission-critical data is assigned to the same service provider class as (UDP-based)
streaming video and the class experiences sustained congestion. Even if WRED is enabled on the
service provider class, the same behavior would be observed, as WRED (for the most part) only affects
TCP-based flows.
Granted, it is not always possible to separate TCP-based flows from UDP-based flows, but it is beneficial
to be aware of this behavior when making such application-mixing decisions.
Reference: http://www.cisco.com/warp/public/cc/so/neso/vpn/vpnsp/spqsd_wp.htm
