Question |
Answer |
A function of the TCP sequence number is: To associate a chronological number with each TCP segment, allowing the receiver to properly reorder the individual segments of data start learning
|
|
|
|
|
A function of the TCP sequence number is: To inform the sender of the next expected chronological sequence number of the TCP segment start learning
|
|
|
|
|
A function of the TCP sequence number is: To reassemble IP fragments start learning
|
|
|
|
|
A function of the TCP sequence number is: To increment the hop count on all TCP segments start learning
|
|
|
|
|
A server port of UDP or TCP 53 is typically associated with what service?: HTTP start learning
|
|
|
|
|
A server port of UDP or TCP 53 is typically associated with what service?: DNS start learning
|
|
|
|
|
A server port of UDP or TCP 53 is typically associated with what service?: FTP start learning
|
|
|
|
|
A server port of UDP or TCP 53 is typically associated with what service?: RPC start learning
|
|
|
|
|
A TCP flag of RESET indicates: An intention to open a new TCP connection start learning
|
|
|
|
|
A TCP flag of RESET indicates: An intention to gracefully close and acknowledge the termination of both sides of the connection start learning
|
|
|
|
|
A TCP flag of RESET indicates: An intention to abort a TCP connection start learning
|
|
|
|
|
A TCP flag of RESET indicates: An intention to close the connection after all in-transit data is received start learning
|
|
|
|
|
A testbed is a bed that can be tested to see if it is comfortable start learning
|
|
|
|
|
A testbed is a platform for conducting rigorous, transparent, and replicable testing of scientific theories, computational tools and new technologies start learning
|
|
|
|
|
A testbed is the Spirent Test Center start learning
|
|
|
|
|
A testbed is a dedicated server that runs components of PlanetLab services start learning
|
|
|
|
|
A value of 6 in the protocol field of the IP header represents: An embedded protocol of ICMP follows the IP header start learning
|
|
|
|
|
A value of 6 in the protocol field of the IP header represents: An embedded protocol of UDP follows the IP header start learning
|
|
|
|
|
A value of 6 in the protocol field of the IP header represents: An embedded protocol of TCP follows the IP header start learning
|
|
|
|
|
A value of 6 in the protocol field of the IP header represents: An embedded protocol of TCP precedes the IP header start learning
|
|
|
|
|
Application nodes: maintain the set of network interface (e.g. eth0, wlan0) in the network node start learning
|
|
|
|
|
Application nodes: are often modeled as compound modules containing separate modules for queues, classes MAC, and PHY protocols start learning
|
|
|
|
|
Application nodes: are represented by compound modules which are connected to the network layer protocol other network interfaces in the wired case start learning
|
|
|
|
|
Application nodes: model the user behavior as well as the application program (e.g. browser), and the application layer protocol (e.g. HTTP) start learning
|
|
|
|
|
[!] ARP protocol: maps a network layer protocol address to a data link layer hardware address start learning
|
|
|
|
|
[!] ARP protocol: is used to provide secure connections across the Internet start learning
|
|
|
|
|
[!] ARP protocol: is used to resolve IP address to the corresponding Ethernt address start learning
|
|
|
|
|
[!] ARP protocol: is used to automatically provide IP addresses to network computers start learning
|
|
|
|
|
CSMA: stands for Computer Shared Medium Access start learning
|
|
|
|
|
CSMA: stands for Carrier Sense Multiple Access start learning
|
|
|
|
|
CSMA: is a protocol in which a node uses a token which gives transmission privilege on shared medium start learning
|
|
|
|
|
CSMA: is a protocol which a node verifies the absence of other traffic before transmitting on the shared transmission medium start learning
|
|
|
|
|
[!] CSMA/CA: stands for Computer Shared Medium Access with Collision Avoidance start learning
|
|
|
|
|
[!] CSMA/CA: stands for Carrier Sense Multiple Access with Collision Avoidance start learning
|
|
|
|
|
[!] CSMA/CA: is used to improve the performance of the CSMA start learning
|
|
|
|
|
[!] CSMA/CA: is a protocol which a node verifies the absence of other traffic before transmitting on the shred transmission medium start learning
|
|
|
|
|
EtherAppClient: is a module implementing the CSMA protocol start learning
|
|
|
|
|
EtherAppClient: is a module implementing an Ethernet application that only receives packets start learning
|
|
|
|
|
EtherAppClient: is a traffic generator the periodically sends messages (Ethernet frames) start learning
|
|
|
|
|
EtherAppClient: accepts connections from EtherAppServer on a specified port start learning
|
|
|
|
|
[!] EtherAppServer: is a module implementing the CSMA protocol start learning
|
|
|
|
|
[!] EtherAppServer: is a module implementing an Ethernet application that only receives packets start learning
|
|
|
|
|
[!] EtherAppServer: generates frames containing EthernetAppResp chunks start learning
|
|
|
|
|
[!] EtherAppServer: accepts connections on a specified port start learning
|
|
|
|
|
[!] INET supports: nodes mobility start learning
|
|
|
|
|
[!] INET supports: simulation visualization start learning
|
|
|
|
|
[!] INET supports: external frameworks start learning
|
|
|
|
|
[!] INET supports: Javascript plugins start learning
|
|
|
|
|
Ipv4NetworkConfigurator: supports manual routes and automatic routes start learning
|
|
|
|
|
Ipv4NetworkConfigurator: supports manual and automatic link configurations e.g. bandwidth, delays start learning
|
|
|
|
|
Ipv4NetworkConfigurator: assigns IPv4 addresses and sets up static routing for an IPv4 network start learning
|
|
|
|
|
Ipv4NetworkConfigurator: supports both manual and automatic address assignment start learning
|
|
|
|
|
[!] Ipv4RoutingTable: supports manual routes and automatic routes start learning
|
|
|
|
|
[!] Ipv4RoutingTable: supports manual and automatic link configurations e.g. bandwidth, delays start learning
|
|
|
|
|
[!] Ipv4RoutingTable: stores a routing table start learning
|
|
|
|
|
[!] Ipv4RoutingTable: supports both manual and automatic routes assignment start learning
|
|
|
|
|
Parameters applied to the simulation may be submitted in: configuration file, e.g. *ini start learning
|
|
|
|
|
Parameters applied to the simulation may be submitted in: topology file e.g. *ned start learning
|
|
|
|
|
Parameters applied to the simulation may be submitted in: in the simulation code *. cpp start learning
|
|
|
|
|
Parameters applied to the simulation may be submitted in: in the other way start learning
|
|
|
|
|
PhysicalEnvironment: arranges nodes in a physical environment start learning
|
|
|
|
|
PhysicalEnvironment: measures temperature of a physical environment start learning
|
|
|
|
|
PhysicalEnvironment: models the effect of a physical environment on radio signal propagation start learning
|
|
|
|
|
PhysicalEnvironment: defines a set of physical objects start learning
|
|
|
|
|
Results of the simulation are saved as: Arrays, lists and scalars start learning
|
|
|
|
|
Results of the simulation are saved as: Vectors, scalars and animations start learning
|
|
|
|
|
Results of the simulation are saved as: Vectors and scalars start learning
|
|
|
|
|
Results of the simulation are saved as: Arrays, vectors and lists start learning
|
|
|
|
|
Round-trip time (RTT): is the measurement of the time taken by an object to travel a distance through a medium start learning
|
|
|
|
|
Round-trip time (RTT): is the length of time it takes for a signal to travel in one direction start learning
|
|
|
|
|
Round-trip time (RTT): specifies the latency for a bit of data to travel across the network from on communication endpoint to another start learning
|
|
|
|
|
Round-trip time (RTT): is the amount of time it takes for a signal to be sent plus the amount of time for acknowledgement of the signal having been received start learning
|
|
|
|
|
StandardHost node contains the most common Internet protocols such as: LTE start learning
|
|
|
|
|
StandardHost node contains the most common Internet protocols such as: TCP start learning
|
|
|
|
|
StandardHost node contains the most common Internet protocols such as: UDP start learning
|
|
|
|
|
StandardHost node contains the most common Internet protocols such as: BGP start learning
|
|
|
|
|
TCP typically begins a session with: The three-way handshake of client to server with SYN set, the server response of SYN/ACK, and the client acknowledgement of ACK start learning
|
|
|
|
|
TCP typically begins a session with: The three-way handshake of server to client with SYN set, the clientresponse of SYN/ACK, and the server acknowledgement of ACK start learning
|
|
|
|
|
TCP typically begins a session with: TCP is not connection oriented so no handshake is required start learning
|
|
|
|
|
TCP typically begins a session with: A handshake consisting of the client request to the server with SYN set and a server response of a SYN start learning
|
|
|
|
|
TcpBasicClientApp: accepts any number of incoming TCP connections start learning
|
|
|
|
|
TcpBasicClientApp: sends back the messages that arrive to it start learning
|
|
|
|
|
TcpBasicClientApp: is a client for a generic request-response style protocol over TCP start learning
|
|
|
|
|
TcpBasicClientApp: communicates with a server sessions start learning
|
|
|
|
|
TCPSinkAPP: listens on an TCP port, and sends back each received packet to its sender start learning
|
|
|
|
|
TCPSinkAPP: generates traffic for a TCP application start learning
|
|
|
|
|
TCPSinkAPP: accepts any number of incoming TCP connections, and discard whatever arrives on start learning
|
|
|
|
|
TCPSinkAPP: sinks TCP packets and leaves the others (e.g. TCP packets) start learning
|
|
|
|
|
[!] The DUT is a: device under test start learning
|
|
|
|
|
[!] The DUT is a: device UDP traffic start learning
|
|
|
|
|
[!] The DUT is a: driver urgent transfer start learning
|
|
|
|
|
[!] The DUT is a: Spirent Test Center interface start learning
|
|
|
|
|
The components of the testbed are: experimental subsystem start learning
|
|
|
|
|
The components of the testbed are: comfortable mattress start learning
|
|
|
|
|
The components of the testbed are: monitoring subsystem start learning
|
|
|
|
|
The components of the testbed are: wireless subsystem start learning
|
|
|
|
|
The following languages are used for description of a simulation: Protel start learning
|
|
|
|
|
The following languages are used for description of a simulation: VHDL start learning
|
|
|
|
|
The following languages are used for description of a simulation: Proto-C start learning
|
|
|
|
|
The following languages are used for description of a simulation: C/C++ start learning
|
|
|
|
|
The ISO/OSI model consists of three layers. start learning
|
|
|
|
|
The ISO/OSI model consists of five layers. start learning
|
|
|
|
|
The ISO/OSI model consists of seven layers. start learning
|
|
|
|
|
The ISO/OSI model consists of eight layers. start learning
|
|
|
|
|
The slice is a: set of allocated resources distributed across PlanetLab. start learning
|
|
|
|
|
The slice is a: set of allocated resources on a single PlanetLab node. start learning
|
|
|
|
|
The slice is a: physical location where PlanetLab nodes are located. start learning
|
|
|
|
|
The slice is a: dedicated server that runs components of PlanetLab services. start learning
|
|
|
|
|
The sliver is a: set of allocated resources distributed across PlanetLab. start learning
|
|
|
|
|
The sliver is a: slice (set of allocated resources) running on a specific node start learning
|
|
|
|
|
The sliver is a: set of allocated resources on a single PlanetLab node start learning
|
|
|
|
|
The sliver is a: physical location where PlanetLab nodes are located. start learning
|
|
|
|
|
The silver is a: dedicated server that runs components of PlanetLab services. start learning
|
|
|
|
|
[!] The Stream Block is a: “summary” definition, it can represent a single stream on a single port, or 1000s of stream across 100s ports start learning
|
|
|
|
|
[!] The Stream Block is a: Spirent chassis start learning
|
|
|
|
|
[!] The Stream Block is a: router start learning
|
|
|
|
|
[!] The Stream Block is a: single stream on s single port start learning
|
|
|
|
|
The TCP is a |connection-oriented| protocol start learning
|
|
|
|
|
The TCP is a |reliable| protocol start learning
|
|
|
|
|
The TCP is a |both a and b| protocol start learning
|
|
|
|
|
The TCP is a |encypted| protocol start learning
|
|
|
|
|
The TCP is a |plain text| protocol start learning
|
|
|
|
|
The TCP is a |none of the above| protocol start learning
|
|
|
|
|
The TCP/IP model consists of |three| layers start learning
|
|
|
|
|
The TCP/IP model consists of |four| layers start learning
|
|
|
|
|
The TCP/IP model consists of |five| layers start learning
|
|
|
|
|
The TCP/IP model consists of |seven| layers start learning
|
|
|
|
|
To run the Omnet++ executable, you need an: omnetpp. ini start learning
|
|
|
|
|
To run the Omnet++ executable, you need an: omnetpp. inf start learning
|
|
|
|
|
To run the Omnet++ executable, you need an: omnetpp. txt start learning
|
|
|
|
|
To run the Omnet++ executable, you need an: omnetpp. vec start learning
|
|
|
|
|
Using the Stream Block Editor of the Spirent Test Center we can define: the Ethernet frame start learning
|
|
|
|
|
Using the Stream Block Editor of the Spirent Test Center we can define: the UDP header start learning
|
|
|
|
|
Using the Stream Block Editor of the Spirent Test Center we can define: the IPv4 header: the gateway in the UDP header start learning
|
|
|
|
|
Using the Stream Block Editor of the Spirent Test Center we can define: the destination MAC address in UDP header start learning
|
|
|
|
|
Using the Stream Block Editor of the Spirent Test Center we can define start learning
|
|
Using the Stream Block Editor of the Spirent Test Center we can define
|
|
|
UDPSink: listens on an UDP port, and sends back each received packet to its sender start learning
|
|
|
|
|
UDPSink: generates traffic for a UDP application start learning
|
|
|
|
|
UDPSink: consumes and prints packets received from the UDP module start learning
|
|
|
|
|
UDPSink: sinks UDP packets and leaves the other (e.g. TCP packets) start learning
|
|
|
|
|
What is a typical response from a host that receives a UDP packet on a non-listening port?: A UDP reset flag set to the sender start learning
|
|
|
|
|
What is a typical response from a host that receives a UDP packet on a non-listening port?: A UDP FIN flag set to the sender start learning
|
|
|
|
|
What is a typical response from a host that receives a UDP packet on a non-listening port?: An ICMP port unreachable message to the sender start learning
|
|
|
|
|
What is a typical response from a host that receives a UDP packet on a non-listening port?: A UDP port unreachable message to the sender start learning
|
|
|
|
|
What is the function of a router?: It determines the entire route for an IP packet from source to destination host start learning
|
|
|
|
|
What is the function of a router?: It uses ARP to route the packet to the next hop start learning
|
|
|
|
|
What is the function of a router?: It uses DNS to route the packet to the next hop start learning
|
|
|
|
|
What is the function of a router?: It attempts to move the IP packet one hop closer to the destination start learning
|
|
|
|
|
What is the output of the Omnet++ simulation?: The simulation results are recorded into output scalar (. sca) file start learning
|
|
|
|
|
What is the output of the Omnet++ simulation?: The simulation results are recorded into output vector (. vec) file start learning
|
|
|
|
|
What is the output of the Omnet++ simulation?: The simulation results are recorded into output vector (. vec) and output scalar (. sca) files start learning
|
|
|
|
|
What is the output of the Omnet++ simulation?: none of the above start learning
|
|
|
|
|
[!] Which are predefined geographical (?) scales of network topologies?: world start learning
|
|
|
|
|
[!] Which are predefined geographical (?) scales of network topologies?: enterprise start learning
|
|
|
|
|
[!] Which are predefined geographical (?) scales of network topologies?: campus start learning
|
|
|
|
|
[!] Which are predefined geographical (?) scales of network topologies?: office start learning
|
|
|
|
|
Which of the following best characterizes TCP versus UDP (in most cases)?: TCP is less reliable and quicker start learning
|
|
|
|
|
Which of the following best characterizes TCP versus UDP (in most cases)?: TCP is slower, more reliable, and requires more overhead start learning
|
|
|
|
|
Which of the following best characterizes TCP versus UDP (in most cases)?: TCP is faster, more reliable, and more streamlined start learning
|
|
|
|
|
Which of the following best characterizes TCP versus UDP (in most cases)?: TCP is less reliable and connection-oriented start learning
|
|
|
|
|
Which topics were NOT covered by twelve pdf manuals available on the Platform?: TCP start learning
|
|
|
|
|
Which topics were NOT covered by twelve pdf manuals available on the Platform?: WiFi start learning
|
|
|
|
|
Which topics were NOT covered by twelve pdf manuals available on the Platform?: LTE start learning
|
|
|
|
|
Which topics were NOT covered by twelve pdf manuals available on the Platform?: Queuing disciplines start learning
|
|
|
|
|