01. Which two pieces of information are typically found on a logical network diagram? (Choose two.)
- cable types
- connector types
- interface identifiers
- DLCI for virtual circuits
- operating system versions
02. Excessive broadcasts are generally a symptom of a problem at which layer?
- physical
- data link
- network
- transport
- incorrect encapsulation
- incorrect STP configuration
- incorrect ARP mapping
- incorrect clock rate
- information about the network design
- IP addressing allocation on the network
- requirements about the service provider setup
- requirements for access control lists to regulate traffic
- expected performance under normal operating conditions
05.Refer to the exhibit. Which two steps should be taken during the process of creating network documentation? (Choose two.)
- Record the information about the devices discovered in the Campus network only.
- Record the information about the devices discovered in the entire network, including the remote locations.
- Transfer any information about the devices from the network configuration table that corresponds to a component of the topology diagram.
- Transfer only the Layer 2 and Layer 3 information about the devices from the network configuration table that corresponds to a component of the topology diagram.
- Transfer the recorded information about the devices from the network configuration table gathered during peak network utilization that corresponds to a component of the topology diagram.
- TCP/IP splits the lowest layer of the OSI model into two separate layers.
- The top layer of the TCP/IP model combines the functions of the top three OSI layers.
- Troubleshooting with the TCP/IP model requires different techniques than with the OSI model.
- The network access layer is responsible for exchanging packets between devices on a TCP/IP network.
- The Internet layer provides communication between applications, such as FTP, HTTP, and SMTP on separate hosts.
- The TCP/IP network access layer corresponds to the OSI physical and data link layers.
- The jabber in the data center indicates a local physical layer problem. Use the protocol analyzer to determine the source of the jabber, and then check for a recent NIC driver update or bad cabling.
- Because all clients are experiencing application problems, the administrator should use a top-down approach with the application servers in the data center.
- The scope of the problem indicates a likely routing or spanning-tree problem. Begin by checking routing tables, and follow up using appropriate STP show commands to find a loop if routing is working normally.
- Poll the staff to determine if any recent changes have been made. Back out all the changes one by one until the error condition is fixed.
- bottom up
- top down
- divide and conquer
- middle out
- baselining tool
- knowledge base
- protocol analyzer
- cable tester
- cable analyzer
- network analyzer
- protocol analyzer
- knowledge base
- physical
- data link
- network
- application
- narrowing the scope
- gathering symptoms from suspect devices
- analyzing existing symptoms
- determining ownership
13.Refer to the exhibit. Which three pieces of information can be determined by analyzing the output shown? (Choose three.)
- A carrier detect signal is present.
- Keepalives are being received successfully.
- Default encapsulation is used on this serial link.
- Packets passing this interface cannot exceed 1 KB in size.
- The reliability of this link is very low.
- The LCP negotiation phase is complete.
- The web server should be tested for an application layer problem.
- Frame Relay at R3 and R2 should be tested to narrow the scope of the problem.
- The fact that users at Branch A are working normally proves that there is no problem at R2.
- An ACL entry error could cause the failure at Layer 4 in either R3 or R2.
- The successful ping from R3 to R1 proves that the WAN is functioning normally. Therefore, the problem has to be in the upper layers.
- application
- transport
- network
- data link
- physical
- physical
- data link
- network
- transport
- 192.168.3.32 0.0.0.7
- 192.168.3.32 0.0.0.15
- 192.168.3.40 0.0.0.7
- 192.168.3.40 0.0.0.15
- physical layer
- data link layer
- network layer
- transport layer
- application layer
- All layers
- Layer 1, Layer 2, and Layer 3
- Layer 1, Layer 2, Layer 3, and Layer 4
- Layer 6 and Layer 7
- Determine fault.
- Get to know the user to build trust.
- Obtain information by asking simple pertinent questions.
- Impress the user with use of technical language and skills.
- Determine if the problem is related to time or a specific event.
- Determine if the user can re-create the problem or events leading to the problem.
No comments:
Post a Comment