【题目62】
已知算法A的运行时间函数为T(n)=8T(n/2)+n，其中n表示问题的规模，则该算法的时间复杂度为（62）。另已知算法B的运行时间函数为T(n)=XT(n/4)+n，其中n表示问题的规模。对充分大的n，若要算法B比算法A快，则X的最大值为（63）。 A、θ(n) B、θ(nlgn) C、θ(n) D、θ(n)
【题目63】
已知算法A的运行时间函数为T(n)=8T(n/2)+n2，其中n表示问题的规模，则该算法的时间复杂度为（62）。另已知算法B的运行时间函数为T(n)=XT(n/4)+n2，其中n表示问题的规模。对充分大的n，若要算法B比算法A快，则X的最大值为（63）。 A、15 B、17 C、63 D、65
【题目64】
在某应用中，需要先排序一组大规模的记录，其关键字为整数。若这组记录的关键字基本上有序，则适宜采用（64）排序算法。若这组记录的关键字的取值均在0到9之间（含），则适宜采用（65）排序算法。 A、插入 B、归并 C、快速 D、计数 【题目65】
在某应用中，需要先排序一组大规模的记录，其关键字为整数。若这组记录的关键字基本上
21
32
2
2
有序，则适宜采用（64）排序算法。若这组记录的关键字的取值均在0到9之间（含），则适宜采用（65）排序算法。 A、插入 B、归并 C、快速 D、基数
【题目66】
集线器与网桥的区别是：（66）。
A、集线器不能检测发送冲突，而网桥可以裣测冲突 B、集线器是物理层设备，而网桥是数据链路层设备 C、网桥只有两个端口，而集线器是一种多端口网桥 D、网桥是物理层设备，而集线器是数据链路层设备
【题目67】
POP3协议采用（67）模式，客户端代理与POP3服务器通过建立TCP连接来传送数据。 A、Browser/Server B、Client/Server C、Peer to Peer D、Peer to Server
【题目68】
TCP使用的流量控制协议是（68）。 A、固定大小的滑动窗口协议 B、后退N帧的ARQ协议 C、可变大小的滑动窗口协议 D、停等协议
22
【题目69】
以下4种路由中，（69）路由的子网掩码是255.255.255.255。 A、远程网络 B、静态 C、默认 D、主机
【题目70】
以下关于层次化局域网模型中核心层的叙述，正确的是（70）。 A、为了保障安全性，对分组要进行有效性检查 B、将分组从一个区域高速地转发到另一个区域 C、由多台二、三层交换机组成 D、提供多条路径来缓解通信瓶颈
【题目71】
In a world where it seems we already have too much to do,and too many things to think about, it seems the last thing we need is something new that we have to learn.But use cases do solve a problem with requirements:with （71） declarative requirements it's hard to describe steps and sequences of events.Use cases,stated simply, allow description of sequences of events that, taken together, lead to a system doing something useful.As simple as this sounds,this is important. When confronted only with a pile of requiements, it's often（72）to make sense of what the authors of the requirements really wanted the system to do.In the preceding example, use cases reduce the ambiguity of the requirements by specifying exactly when and under what conditions certain behavior occurs;as such, the sequence of the behaviors can be regarded as a requirement. Use cases are particularly well suited to capture approaches. Although this may sound simple, the fact is that （73） requirement capture approaches, with their emphasis on declarative requirements and \statements,completely fail to capture fail to capture the （74） of the system's
23
behavior. Use cases are a simple yet powerful way to express the behavior of the system in way that all stakeholders can easily understand.But,like anything, use cases come with their own problems, and as useful as they are,they can be （75）. The result is something that is as bad, if not worse, that the original problem.Therein it's important to utilize use cases effectively without creating a greater problem than the one you started with. A、plenty B、loose C、extra D、strict
【题目72】
In a world where it seems we already have too much to do,and too many things to think about, it seems the last thing we need is something new that we have to learn.But use cases do solve a problem with requirements:with （71） declarative requirements it's hard to describe steps and sequences of events.Use cases,stated simply, allow description of sequences of events that, taken together, lead to a system doing something useful.As simple as this sounds,this is important. When confronted only with a pile of requiements, it's often（72）to make sense of what the authors of the requirements really wanted the system to do.In the preceding example, use cases reduce the ambiguity of the requirements by specifying exactly when and under what conditions certain behavior occurs;as such, the sequence of the behaviors can be regarded as a requirement. Use cases are particularly well suited to capture approaches. Although this may sound simple, the fact is that （73） requirement capture approaches, with their emphasis on declarative requirements and \statements,completely fail to capture fail to capture the （74） of the system's behavior. Use cases are a simple yet powerful way to express the behavior of the system in way that all stakeholders can easily understand.But,like anything, use cases come with their own problems, and as useful as they are,they can be （75）.
24
The result is something that is as bad, if not worse, that the original problem.Therein it's important to utilize use cases effectively without creating a greater problem than the one you started with. A、impossible B、possible C、sensible D、practical
【题目73】
In a world where it seems we already have too much to do,and too many things to think about, it seems the last thing we need is something new that we have to learn.But use cases do solve a problem with requirements:with （71） declarative requirements it's hard to describe steps and sequences of events.Use cases,stated simply, allow description of sequences of events that, taken together, lead to a system doing something useful.As simple as this sounds,this is important. When confronted only with a pile of requiements, it's often（72）to make sense of what the authors of the requirements really wanted the system to do.In the preceding example, use cases reduce the ambiguity of the requirements by specifying exactly when and under what conditions certain behavior occurs;as such, the sequence of the behaviors can be regarded as a requirement. Use cases are particularly well suited to capture approaches. Although this may sound simple, the fact is that （73） requirement capture approaches, with their emphasis on declarative requirements and \statements,completely fail to capture fail to capture the （74） of the system's behavior. Use cases are a simple yet powerful way to express the behavior of the system in way that all stakeholders can easily understand.But,like anything, use cases come with their own problems, and as useful as they are,they can be （75）. The result is something that is as bad, if not worse, that the original problem.Therein it's important to utilize use cases effectively without creating a greater problem than the one you started with.
25
相关推荐：
loading