摘要：对于【数据库系统工程师】软考考试而言，试题无疑是最重要的学习资料之一。在软考备考过程中，吃透试题、掌握试题所考知识点、熟悉试题的出题思路，对我们提升分数的效果是最明显的，通过对试题的反复练习，还可以查漏补缺。今天，给大家带来【2013年5月 数据库系统工程师 上午题】部分试题的详解，一起来看看吧~



1、随着网站知名度的不断提高，网站访问量逐渐上升，网站负荷越来越重，针对此问题一方面可通过升级网站服务器的软硬件，另一方面可以通过集群技术，如DNS负载均衡技术来解决。在Windows的DNS服务器中通过（ ）操作可以确保域名解析并实现负载均衡。
A、 启用循环，启动转发器指向每个Web服务器
B、 禁止循环，启动转发器指向每个Web服务器
C、 禁止循环，添加每个Web服务器的主机记录
D、 启用循环，添加每个Web服务器的主机记录

答案:D
答题解析:

DNS负载均衡是通过循环复用实现的，若发现主机名的多个地址资源记录，则可用它循环使用包含在查询应答中的主机资源记录。要使DNS循环复用正常工作，首先需在相应的正向查找区域中注册所查询名称的多个主机资源记录(如图所示)，并在DNS服务器属性的[高级]选项卡中，选中[启用循环]复选框(如图所示)。如果未选中该复选框(即禁止循环复用)，则相应DNS查询的响应顺序取决于应答列表中各条资源记录在区域中存储的静态排序。接着，还需在DNS服务器的“正向查找区域”中添加每个Web服务器的主机(A)资源记录。

2、So it is today. Schedule disaster, functional misfits, and system bugs all arise because the left hand doesn't know what the right hand is doing. As work （请作答此空）, the several teams slowly change the functions, sizes, and speeds of their own programs, and they explicitly or implicitly （ ） their assumptions about the inputs available and the uses to be made of the outputs.For example, the implementer of a program-overlaying function may run into problems and reduce speed relying on statistics that show how （ ） this function will arise in application programs. Meanwhile, back at the ranch, his neighbor may be designing a major part of the supervisor so that it critically depends upon the speed of this function. This change in speed itself becomes a major specification change, and it needs to be proclaimed abroad and weighed from a system point of view.How, then, shall teams （ ） with one another? In as many ways as possible.Informally. Good telephone service and a clear definition of intergroup dependencies will encourage the hundreds of calls upon which common interpretation of written documents depends.Meetings. Regular project meetings, with one team after another giving technical riefings, are （ ）. Hundreds of minor misunderstandings get smoked out this way.Workbook. A formal project workbook must be started at the beginning.
A、 starts
B、 proceeds
C、 stops
D、 speeds

答案:B
答题解析:

无

3、So it is today. Schedule disaster, functional misfits, and system bugs all arise because the left hand doesn't know what the right hand is doing. As work （ ）, the several teams slowly change the functions, sizes, and speeds of their own programs, and they explicitly or implicitly （请作答此空） their assumptions about the inputs available and the uses to be made of the outputs.For example, the implementer of a program-overlaying function may run into problems and reduce speed relying on statistics that show how （ ） this function will arise in application programs. Meanwhile, back at the ranch, his neighbor may be designing a major part of the supervisor so that it critically depends upon the speed of this function. This change in speed itself becomes a major specification change, and it needs to be proclaimed abroad and weighed from a system point of view.How, then, shall teams （ ） with one another? In as many ways as possible.Informally. Good telephone service and a clear definition of intergroup dependencies will encourage the hundreds of calls upon which common interpretation of written documents depends.Meetings. Regular project meetings, with one team after another giving technical riefings, are （ ）. Hundreds of minor misunderstandings get smoked out this way.Workbook. A formal project workbook must be started at the beginning.
A、 change
B、 proceed
C、 smooth
D、 hide

答案:A
答题解析:

无

查看完整试题>>>