Business Data Communications And Networking - Final

Front 1

One basic component of a backbone network is the hardware device that connects other networks to the backbone.

Back 1

True

Front 2

Routed backbones use switches that move packets based on data link layer addresses.

Back 2

False

Front 3

A backbone network is a high-speed network that connects many networks

Back 3

True

Front 4

Routers connect two or more network segments that use the same or different data link protocols, but the same network protocol.

Back 4

True

Front 5

A room that contains a rack of equipment for a rack-based collapsed backbone is also called the main distribution facility (MDF) or central distribution facility (CDF).

Back 5

True

Front 6

The committed information rate (CIR) in a permanent virtual circuit is the maximum allowable rate that the network will attempt to provide.

Back 6

False

Front 7

Full mesh design networks are more common than partial mesh design networks.

Back 7

False

Front 8

Datagrams are connection-oriented.

Back 8

False

Front 9

Cloud (as in cloud architecture) means that the design for the common carrier's network comes from satellite networks above the clouds.

Back 9

False

Front 10

T carrier circuits can only be used to transmit voice.

Back 10

False

Front 11

DSL uses a remote loop to connect homes to the telephone company end office.

Back 11

False

Front 12

Tier 1 service providers connect together and exchange data at Network Access Points

Back 12

True

Front 13

IBM recently developed a new WiMAX chip set.

Back 13

False - Intel did

Front 14

Technologies such as DSL and cable modem are called narrowband technologies.

Back 14

False - Broadband

Front 15

A distribution hub includes a combiner and a Cable modem termination system.

Back 15

True

Front 16

Physical security of an organization's IT resources is not an important element in preventing intrusion to an internal LAN.

Back 16

False - it is highly important

Front 17

A Delphi team that helps the network manager assess the security risks to the organization should always have at least 20 members.

Back 17

False - its 3 - 9 people

Front 18

The best solution for planning for disaster recovery is to have a fully redundant backup network placed in a different location that would not be threatened by the same natural or man-made disaster that would destroy the original network.

Back 18

True

Front 19

Network cables are the easiest target for eavesdropping.

Back 19

False - WiFi is

Front 20

A NAT proxy server uses an address table to translate private IP addresses used inside the organization into proxy data link layer addressed used on the Internet.

Back 20

True

Front 21

The technology that is closest to a user in a network design is the core layer.

Back 21

False - the Access layer is closest to the user

Front 22

The turnpike effect results when a network is used at a much lower rate than was anticipated when it was designed.

Back 22

False - an expression that means that traffic increases much faster than originally forecast.

Front 23

Traffic analysis involves determining why some circuits are heavily used.

Back 23

True

Front 24

A traditional network design approach follows a structured systems analysis and design process similar to that used in building applications.

Back 24

True

Front 25

Today, most network designers use a three to five year planning horizon.

Back 25

True

Front 26

The goal of the needs analysis step in network design is to develop a physical network design.

Back 26

False - goal is to produce a logical network design

Front 27

One of the most commonly used network management protocols is Common Management Interface Protocol.

Back 27

True

Front 28

Today, all network traffic is due to traffic from internal application systems.

Back 28

False - much is produced by the discretionary use of the Internet!

Front 29

Today, the most expensive part of the network is the hardware.

Back 29

False - the most expensive part of the network is the staff members who design, operate, and maintain it

Front 30

Content caching is designed to store your own web material closer to your servers.

Back 30

False - to store outside web pages for faster load when site is revisited.

Front 31

One key to integrating diverse networks in an organization is for the individual network managers to realize that they no longer wield the same amount of power.

Back 31

True

Front 32

Network management is the process to operating, monitoring, and controlling the network to ensure it works as intended and provides value to its users.

Back 32

True

Front 33

Quality control charts are a simple tool that can be used by network managers to monitor network conditions.

Back 33

True

Front 34

Problem statistics are not helpful in determining whether vendors are meeting contractual maintenance commitments.

Back 34

False - statistics also can be used to determine
whether vendors are meeting their contractual maintenance commitments.

Front 35

One of the least common configuration activities is adding and deleting user accounts.

Back 35

False - It is the most common activity

Front 36

The future of network management lies in the management of LANs, BNs, and Internet resources instead of concentrating on mainframe resources.

Back 36

True

Front 37

Failure control requires developing a decentralized control philosophy for problem reporting.

Back 37

False - Centralized

Front 38

Today, the critical issue of network management is managing only the mainframe's network.

Back 38

False - it is managing the LANs, BNs...

Front 39

To ensure that critical problems get priority over less important ones, problem prioritizing is needed in a network.

Back 39

True

Front 40

Service level agreements specify the exact type of performance and fault conditions that an organization will accept from a common carrier or Internet service provider.

Back 40

True

Front 41

availability

Back 41

Uptime. important failure statistic the percentage of time the network is available to users. It is calculated as the number of hours per month the network is available divided by the total number of hours per month

Front 42

charge-back policy

Back 42

attempt to allocate the costs associated with the network to specific users.These users must “pay” for their network usage by transferring part of
their budget allocations to the network group.
**seldom used in LANs,

Front 43

configuration management

Back 43

managing the network’s hardware and software configuration,and documenting it, and ensuring it is updated as the configuration changes.

Front 44

cost management

Back 44

includes the costs of operating the network infrastructure and standard applications such as email and the Web,

Front 45

desktop management

Back 45

plays a key role in simplifying configuration management by automating and documenting the network configurations.
automatically produces and maintains accurate documentation of all software installed on each client computer and enables network managers to produce a variety of useful reports.

Front 46

downtime

Back 46

includes times when the network is unavailable because of faults and routine maintenance and network upgrades.

Front 47

end user support

Back 47

assisting end users

Front 48

fault management

Back 48

making sure the network operates as desired

Front 49

firefighting

Back 49

dealing with breakdowns and immediate problems.

Front 50

logical network parameters

Back 50

include performance measurement systems that keep track of user response times, the volume of traffic on a specific circuit,

Front 51

mean time between failures (MTBF)

Back 51

the number of hours or days of continuous operation before a component fails. Obviously, devices with higher MTBF are more reliable.

Front 52

mean time to diagnose
(MTTD)

Back 52

the average number of minutes until the
root cause of the failure is correctly diagnosed.

Front 53

mean time to fix (MTTF)

Back 53

This figure tells how quickly the staff is able to
correct the problem after they arrive.

Front 54

mean time to repair (MTTR)

Back 54

is the average number of minutes or hours until the failed device or circuit is operational again.

Front 55

mean time to respond (MTTR)

Back 55

measured as a monthly average of the time from inception of trouble ticket until repair personnel are on site, should be 4 hours or less

Front 56

monitor

Back 56

Watching, keeping track

Front 57

network cost of ownership (NCO)

Back 57

costing methods that examine only the direct costs of operating the computers, omitting softer indirect costs such as “wasted” time.

Front 58

network documentation

Back 58

The most basic information about network hardware is a set of network configuration diagrams that document the number, type, and placement of network circuits (whether organization owned or leased from a common carrier), network servers, network devices (e.g., hubs, routers), and client computers.
For most organizations, this is a large set of diagrams: one for each LAN, BN, and WAN.

Front 59

network management

Back 59

the process of operating, monitoring, and controlling the network to ensure it works as intended and provides value to its users.

Front 60

network monitoring

Back 60

keeping track of the operation of network circuits and devices to ensure they are functioning properly and to determine how heavily they are used.

Front 61

network operations center (NOC)

Back 61

responsible for monitoring and fixing problems. centers are staffed by a set of skilled network technicians that use sophisticated network management software.

Front 62

network weather map

Back 62

common type of monitoring approach which displays the usage of all major circuits in the network in real time.

Front 63

performance management

Back 63

ensuring the network is operating as efficiently as
possible

Front 64

physical network

Back 64

the operation of the network’s modems, multiplexers, circuits linking the various hardware devices, and any
other network devices.

Front 65

parameters

Back 65

rule or limit that controls what something is or how something should be done; network monitoring tool.

Front 66

problem statistics

Back 66

because they are a control device for the network
managers as well as for vendors. With this information, a manager can see how well the
network is meeting the needs of end users. These statistics also can be used to determine whether vendors are meeting their contractual maintenance commitments. Finally, they help to determine whether problem-solving objectives are being met.

Front 67

problem tracking

Back 67

allows the network manager to determine who is responsible for correcting any outstanding problems.

Front 68

service-level agreement (SLA)

Back 68

specifies the exact type of performance and fault conditions that the organization will accept.

Front 69

total cost of ownership (TCO)

Back 69

measure of how much it costs per year to keep one computer operating. TCO includes the actual direct cost of repair parts, software upgrades, and support staff members to maintain the network, install software, administer the network (e.g., create user IDs, back up user data), provide training and technical support, and upgrade hardware and software. It also includes the indirect cost of time “wasted” by the user when problems occur, when the network is down, or when the user is attempting to learn new software.

Front 70

trouble ticket

Back 70

recording of fault information.

Front 71

uptime

Back 71

Network availability

Front 72

access layer

Back 72

is the technology that is closest to the user—the user’s first contact with the network—and is often a LAN or
a broadband Internet connection.

Front 73

Akamai

Back 73

a special type of Internet service that works in the opposite direction.

Front 74

agent

Back 74

act as a proxy agent on behalf of SNMP managed devices

Front 75

alarm

Back 75

message to the network manager’s computer if it detects a critical situation such as a failing device or a huge increase in traffic.

Front 76

alarm storm

Back 76

One failure often generates several dozen problem
reports,

Front 77

application management

Back 77

software that also builds on the device management software, but instead of monitoring systems, it monitors applications.

Front 78

bandwidth shaper ... bandwidth limiter

Back 78

monitor traffic and can act to slow down traffic from users who consume too much capacity.

Front 79

baseline

Back 79

important to gain an understanding of the current operations (application systems and messages). This step provides a baseline against which future design requirements can be gauged

Front 80

building-block process

Back 80

basic design process involves three steps that are performed repeatedly: needs analysis, technology design, and cost assessment

Front 81

capacity management

Back 81

devices, sometimes called bandwidth limiters or bandwidth shapers, monitor traffic and can act to slow down traffic from users who consume too much capacity. These devices are installed at key points in the network, such as between a switch serving a LAN and the backbone it connects into, and are configured to allocate capacity based on the IP address of the source

Front 82

capacity planning

Back 82

Designing the circuit capacity, estimating the size and
type of the standard and advanced network circuits for each type of network (

Front 83

circuit loading

Back 83

the amount of data transmitted on a circuit

Front 84

cluster

Back 84

servers that are placed together in server farms

Front 85

Common Management Interface Protocol (CMIP)

Back 85

CMIP is a newer protocol for OSI-type networks developed by the ISO. (network management protocols)

Front 86

content caching

Back 86

basic idea behind content caching is to store other people’s Web data closer to your users. With content caching, you install a content engine (also
called a cache engine) close to your Internet connection and install special content
management software on the router

Front 87

content delivery

Back 87

a special type of Internet service that works in the opposite direction.

Front 88

content delivery provider

Back 88

Rather than storing other people’s Web files closer to their own internal users, a content delivery provider stores Web files for its clients closer to their potential users.

Front 89

content engine

Back 89

With content caching, you install a content engine (also called a cache engine) close to your Internet connection and install special content management software on the router

Front 90

core layer

Back 90

the innermost part of the network that connects the different distribution-layer networks to each other, such as the primary BN on a campus or a set of WAN circuits connecting different offices together.

Front 91

cost assessment

Back 91

gathers cost information for the network, usually through an RFP that specifies what equipment, software, and services are desired and asks vendors to provide their best prices.

Front 92

desirable requirements

Back 92

a negotiable list of desirable requirements for the network that are dependent on cost and availability

Front 93

device management software

Back 93

(sometimes called point management software) is
designed to provide information about the specific devices on a network. It enables the network-manager to monitor important devices such as servers, routers, and gateways, and typically report configuration information, traffic volumes, and error conditions for each device.

Front 94

distribution layer

Back 94

the next part of the network that connects the access layer to the rest of the network, such as the BN(s) in a specific building.

Front 95

geographic scope

Back 95

map of the actual setup of the three network layers - by connection

Front 96

green IT

Back 96

the design and use of information technology to improve environmental sustainability.

Front 97

latency

Back 97

the delay imposed by the device in processing messages. A high-latency device is one that takes a long time to process a message, whereas a low-latency device is fast.

Front 98

load balancing switch

Back 98

A special device called a load balancing switch or virtual server acts as a router at the front of the server farm. All requests are directed to the load balancer at its IP address. When a request hits the load balancer it forwards it to one specific server
using its IP address. Sometimes a simple round-robin formula is used (requests go to each server one after the other in turn); in other cases, more complex formulas track how busy each server actually is. If a server crashes, the load balancer stops sending requests to it and the network continues to operate without the failed server.

Front 99

logical network design

Back 99

a statement of the network elements needed to meet the needs of the organization. The logical design does not specify technologies or products to be used (although any specific requirements are noted). Instead, it focuses on the fundamental functionality needed, such as a high-speed access network, which in the technology design stage will be translated into specific technologies (e.g., switched 100Base-T).

Front 100

managed device

Back 100

standard devices, such as switches and routers, that have small onboard computers to monitor traffic flows through the device as well as the status of the device and other devices connected to it. Managed devices perform their functions (e.g., routing, switching) and also record data on the messages they process. These data can be sent to the network manager’s computer when the device receives a special control message requesting the data, or the device can send an alarm message to the network manager’s computer if it detects a critical situation such as a failing device or a huge increase in traffic.

Front 101

managed network

Back 101

network that uses managed devices

Front 102

management information base (MIB)

Back 102

central database storage for the information collected on each device by the agent about itself and the messages it processes

Front 103

mandatory requirements

Back 103

Once the network requirements have been identified, they also should be organized into mandatory requirements, development of a minimum level of requirements

Front 104

needs analysis

Back 104

the designer attempts to understand the fundamental current and future network needs of the various users, departments, and applications. This is likely to be an educated guess at best. Users and applications are classified as typical or high
volume. Specific technology needs are identified.

Front 105

network management software

Back 105

software required by a managed network used to store, organize and analyze the reports and alerts. There are 3 kinds: Device Management Software, System Management and Application Management

Front 106

physical network design

Back 106

developed after the logical network design, The physical network design starts with the client and server computers needed to support the users and applications. If the network is a new network, new computers will need to be purchased. If the network is an existing network, the servers may need to be upgraded to the newest technology. Once these are designed, then the circuits and devices connecting them are designed.

Front 107

policy-based management

Back 107

the network manager uses special software to set priority policies for network traffic that take effect when the network becomes busy.

Front 108

remote monitoring (RMON)

Back 108

Most SNMP devices have the ability for remote monitoring (RMON). Most first-generation SNMP tools reported all network monitoring information to one central network management database. Each device would transmit updates to its MIB on
the server every few minutes, greatly increasing network traffic. RMON SNMP software enables MIB information to be stored on the device itself or on distributed RMON probes that store MIB information closer to the devices that generate it.

Front 109

request for proposal (RFP)

Back 109

used to solicit bids from vendors for new network hardware, software, and services. RFPs specify what
equipment, software, and services are desired and ask vendors to provide their best prices.

Front 110

RMON probe

Back 110

that store MIB information closer to the devices that generate it. The data are not transmitted to the central server until the network manager requests, thus reducing network traffic

Front 111

root cause analysis

Back 111

The dozens of error messages are symptoms that mask the root cause. System management software tools correlate the individual error messages into a pattern to find the true cause,

Front 112

server farm

Back 112

servers are placed together in server farms or clusters, which sometimes have hundreds of servers that perform the same task.

Front 113

server virtualization

Back 113

the process of creating several logically separate servers (e.g., a Web server, an email server, a file server) on the same physical computer. The virtual servers run on the same physical computer, but appear completely separate to the network (and if one crashes it does not affect the others running on the same computer).

Front 114

Simple Network Management Protocol (SNMP)

Back 114

SNMP is the Internet network management standard, most commonly used; Originally, SNMP was developed to control and monitor the status of network devices on TCP/IP networks

Front 115

simulation

Back 115

a mathematical technique in which the network comes to life and behaves as it would under real conditions, is used to model the behavior of the communication network.

Front 116

system management software

Back 116

(sometimes called enterprise management software or a network management framework) provides the same configuration, traffic, and error information as device management systems, but can analyze the device information to diagnose patterns, not just display individual device problems.

Front 117

technology design

Back 117

examines the available technologies and assesses
which options will meet users’ needs. The designer makes some estimates about the network needs of each category of user and circuit in terms of current technology (e.g., 100Base-T, 1000Base-T) and matches needs to technologies

Front 118

traditional network design process

Back 118

design approach follows a very structured systems analysis and design process similar to that used to build application systems. It attempts to develop precise estimates of network traffic for each network user and network segment. Although
this is expensive and time consuming, it works well for static or slowly evolving networks.

Front 119

traffic analysis

Back 119

device monitors normal traffic patterns and learns what normal traffic looks like

Front 120

turnpike effect

Back 120

an expression that means that traffic increases much faster than originally forecast. It comes from the traffic forecasting that was done for the construction of the early interstate highways

Front 121

virtual server

Back 121

special device called a virtual server acts as a router at the front of the server farm; All requests are directed to the virtual server at its IP address. When a request hits the virtual server it forwards it to one specific server using its IP address. Sometimes a simple round-robin formula is used (requests go to each server one after the other in turn); in other cases, more complex formulas track how busy each server actually is. If a server crashes, the virtual server stops sending requests to it and the network continues to operate without the failed server.

Front 122

wire speed

Back 122

The fastest devices run at wire speed, which means they operate as fast as the circuits they connect and add virtually no delays.

Front 123

wish-list requirements

Back 123

list of desirable requirements that are dependent on cost and availability

Front 124

access control list (ACL)

Back 124

defines what types of packets should be routed
and what types of packets should be discarded

Front 125

application layer address

Back 125

translate the application layer address (or server name) of the destination into a network layer address and in turn translate that into a data link layer address.

Front 126

autonomous systems

Back 126

a network operated by one organization, such as IBM or Indiana University, or an organization that runs one part of the Internet.

Front 127

Border Gateway Protocol(BGP)

Back 127

dynamic distance vector exterior routing protocol used on the Internet to exchange routing information between autonomous systems—that is, large sections of the Internet. Although BGP is the preferred routing protocol between Internet sections, it is seldom used inside companies because it is large, complex, and often hard to administer.

Front 128

border router

Back 128

Each autonomous system has a border router that
connects it to the adjacent autonomous systems
and exchanges route information via Border Gateway Protocol(BGP)

Front 129

centralized routing

Back 129

all routing decisions are made by one central computer or router. Centralized routing is commonly used in host-based networks

Front 130

console port

Back 130

management port, used when first setting up a router.

Front 131

Open Shortest Path First (OSPF)

Back 131

a dynamic hybrid interior routing protocol that is commonly used on the Internet. It uses the number of computers in a route as well as network traffic and error rates to select the best route. preferred interior routing protocol used by TCP/IP.

Front 132

Enhanced Interior Gateway Routing Protocol (EIGRP)

Back 132

is a dynamic hybrid interior routing protocol developed by Cisco and is commonly used inside organizations. Hybrid means that it has some features that act like distance vector protocols and some other features that act like link-state protocols. computer or routers store their own routing table as well as the routing tables for all of their neighbors so they have a more accurate understanding of the network.

Front 133

Virtual LANs

Back 133

networks in which computers are assigned to LAN segments by software rather than by hardware.

Front 134

chassis switch

Back 134

used instead of a rack. A chassis switch enables users to plug modules directly into the switch. Each module is a certain type of network device.

Front 135

distribution layer

Back 135

is the part of the backbone that connects the LANs
together.

Front 136

core layer

Back 136

is the part of the backbone that connects the different BNs together, often from building to building

Front 137

Switched backbone networks

Back 137

use a star topology with one switch at its center. There is a switch serving each LAN (access layer) which is connected to the backbone switch at the bottom of the figure (distribution layer

Front 138

Backbone Architectures Network

Back 138

designers often think about three distinct technology layers when designing backbones. The access layer is the LAN, the distribution layer connects the LANs together, and the core layer connects the distribution-layer BNs together.

Front 139

Best Practice Backbone Design

Back 139

The best practice backbone architecture for most organizations is a switched backbone (using a rack or a chassis switch) or VLAN in the distribution layer and a routed backbone in the core layer. The recommended technology is gigabit Ethernet.

Front 140

full-mesh architecture

Back 140

every computer is connected to every other computer. Full-mesh networks are seldom used because of the extremely high cost.

Front 141

Partial-mesh architecture

Back 141

(usually called just mesh architecture), in which many, but not all, computers are connected, is far more common. Most WANs use partial-mesh topologies.

Front 142

datagram

Back 142

is a connectionless service. It adds a destination address and sequence number to each packet, in addition to information about the data stream to which the packet belongs.

Front 143

asymmetric DSL

Back 143

There are many different types . The most common type of DSL today is asymmetric DSL (ADSL). ADSL uses frequency division multiplexing to create three separate channels over the one local loop circuit. One channel is the traditional voice telephone circuit. A second channel is a relatively high-speed simplex data channel downstream from the carrier’s end office to the customer. The third channel is a slightly slower duplex data channel primarily used for upstream from the customer
to the carrier’s end office

Front 144

Internet Society (ISOC)

Back 144

open-membership professional society with more than 175 organizational and 8,000 individual members in over 100 countries, including corporations, government agencies, and foundations that have created the Internet and its technologies. Because membership in ISOC is open, anyone, including students, is welcome to join and vote on key issues facing the Internet

Front 145

Internet Engineering Task Force (IETF)

Back 145

is a large, open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. The IETF works through a series of working groups, which are organized by topic (e.g., routing, transport, security). The requests for comment (RFCs) that form the basis for Internet standards are developed by the IETF and its working groups.

Front 146

Internet Architecture Board (IAB) .

Back 146

provides strategic architectural oversight. The IAB attempts to develop conclusions on strategic
issues (e.g., top-level domain names, use of international character sets) that can be passed on as guidance to the IESG or turned into published statements or simply passed directly to the relevant IETF working group

Front 147

Internet Research Task Force (IRTF)

Back 147

operates much like the IETF through small research groups focused on specific issues. Whereas IETF working groups focus on current issues, IRTF research groups work on long-term issues related to Internet protocols, applications, architecture, and technology. The IRTF chairperson is appointed by the IAB.