(2023数据库系统工程师科目一71-75真题)
71~75(71)is a software package designed to store, retrieve, query and manage data. User interfaces (Uls) allows data to be created, read, updated and deleted by authorized entities. The system users include database administrators (DBAs)application programmers and end users. Most of the time,(72)are the only ones to directly interact with a system. They use(73) to deal with database schemas and descriptions, of how the data should reside in the database. They use(74) to deal with data manipulation which includes most common SQL statements such as SELECT, INSERT, UPDATE, DELETE, etc. They also focus on managing and maintaining the(75)of the database system:prevent unauthorized access to the data.
71. A.DB B.DBMS C.SQL D.DDL
72. A.database administrators (DBAs) B.application programmers C.end users D.programmers
73. A.DDL B.DML C.SQL D.MML
74. A.DDL B.DML C.SQL D.MML
75. A.maintenance B.security C.performance D.capacity
答案:B, A, A, B, B
DB(71,数据库)是一个软件包,旨在存储、检索、查询和管理数据。用户界面(Uls)允许授权实体创建、读取、更新和删除数据。系统用户包括数据库管理员(DBA)、应用程序程序员和最终用户。大多数情况下,DBA(72,数据库管理员)是唯一直接与系统交互的人。他们使用DDL(73,数据库描述语言)处理数据库模式和描述,确定数据应该如何存储在数据库中。他们使用DML(74,数据库操作语言)处理数据操作,其中包括最常见的SQL语句,如SELECT、INSERT、UPDATE、DELETE等。他们还专注于管理和维护数据库系统的安全性(75,安全性):防止未经授权的访问数据。
(2022数据库系统工程师科目一71-75真题)
71~75. Corporate decision makers require access to information from multiple such sources. Setting up queries on individual sources is both cumbersome and (71). Moreover, the sources of data may store only current data, whereas decision makers may need access to (72) data as well. A data warehouse is a repository (or archive) of information gathered from multiple sources, stored under a unified schema, at a (73) site. Once gathered, the data are stored for a long time, permitting access to historical data. Thus, data warehouses provide the user with a single consolidated (74) to data,making decision-support queries easier to write. Moreover, by accessing information for decision support from a data warehouse, the decision maker ensures that online transaction-processing systems are not (75) by the decision-support workload.
71. A.inefficient B.efficient C.easy D.uneasiness
72. A.many B.past C.big D.much
73. A.distributed B.single C.many D.data
74. A.table B.row C.system D.interface
75. A.used B.affected C.supported D.exploited
答案:A, B, A, D, B
企业决策者需要从多个这样的来源获取信息。在单个来源上设置查询既繁琐又低效(71,低效的)。此外,数据源可能只存储当前数据,而决策者可能需要访问过去(72,历史的,过去的)的数据。数据仓库是一个信息存储库(或档案),它从多个来源收集信息,并在分布式(73,分布式的)站点下以统一模式进行存储。一旦收集到数据,它们就会被长期存储,允许访问历史数据。因此,数据仓库为用户提供了一个单一的整合数据接口(74,接口),使决策支持查询更容易编写。此外,通过从数据仓库访问决策支持信息,决策者可以确保在线事务处理系统不受决策支持工作负载的影响(75,影响)。
(2021数据库系统工程师科目一71-75真题)
71~75.When we talk about a database, we must differentiate between the database (71) which is the logical design of the database, and the database (72) which is a snapshot of the data in the database at a given instant in time.The concept of a relation corresponds to the programming language notion of a variable, while the concept of a relation schema corresponds to the programming-language notion of type definition. In general, a relation schema consists of a list of (73) and their corresponding domains. The concept of a relation instance corresponds to the programming-language notion of a value of a (74). The value of a given variable may change with time, similarly the contents of a relation instance may change with time as the relation is updated.
In contrast, the (75) of a relation does not generally change.
71.A.schema B.instance C.table D.entity
72.A.schema B.table C.instance D.entity
73.A.variable B.attributes C.rows D.notions
74.A.constant B.variable C.struct D.array
75.A.table B.schema C.instance D.view
答案:A,B,B,B,B
当我们谈论数据库时,我们必须区分数据库模式(71,模式)和数据库表。数据库模式是数据库的逻辑设计,而数据库表(72,表)是数据库在给定时刻的数据快照。关系的概念对应于编程语言中变量的概念,而关系模式的概念对应于编程语言中类型定义的概念。一般来说,关系模式由属性(73,属性)列表及其相应的域组成。关系实例的概念对应于编程语言中变量(74,变量)的值的概念。给定变量的值可能会随时间变化,同样地,随着关系的更新,关系实例的内容也可能会随时间变化。相比之下,关系的模式(75,模式)通常不会改变。
(2020数据库系统工程师科目一71-75真题)
A database system is a collection of interrelated data and a set of programs that allow users to access and modify these data. A major purpose of a database system is to provide users with an (71) view of the data.That is,the system hides certain details of how the data are stored and maintained. For the system to be usable,it must retrieve data (72).The need for efficiency has led designers to use complex data (73) to represent data in the database. Since many database-system users are not computer trained, developers hide the complexity from users through several levels of abstraction, to simplify users' interactions with the system. Physical level is the lowest level of abstraction that describes (74) the data are actually stored. Logical level is the next-higher level of abstraction that describes (75) data are stored in the database, and what relationships exist among those data. View level is the highest level of abstraction that describes only part of the entire database.
71.A.abstract B.physical C.administrator D.operator
72.A.completely B.safely C.usefully D.efficiently
73.A.files B.structures C.graphs D.flows
74.A.how B.what C.which D.when
75.A.how B.what C.which D.when
答案:A, D, B, A, B
数据库系统是一组相互关联的数据和一套程序的集合,它允许用户访问和修改这些数据。数据库系统的主要目的是为用户提供数据的抽象(71,抽象的)视图。也就是说,系统隐藏了数据存储和维护的某些细节。为了使系统可用,它必须有效地(72,有效地)检索数据。对效率的需求促使设计者使用复杂的数据结构(73,结构)来表示数据库中的数据。由于许多数据库系统的用户没有接受过计算机训练,开发人员通过几个抽象级别将复杂性隐藏起来,以简化用户与系统的交互。物理级别是描述数据(74,如何)实际存储方式的最低级别的抽象。逻辑级别是描述数据库中存储了什么(75,什么)数据以及这些数据之间存在什么关系的下一个更高的抽象级别。视图级别是描述整个数据库仅部分内容的最高水平的抽象。
(2019数据库系统工程师科目一71-75真题)
71~75. The entity-relationship (E-R)data model is based on a perception of a real world that consists of a collection of basic objects, called (71) and of relationships among these objects. An entity is a "thing"or "object" in the real world that is distinguishable from other objects. Entities are described in a database by a set of (72). A relationship is an association among several entities. The set of all entities of the same type and the set of all relationships of the same type are termed an entity set and relationship set, respectively. The overall logical structure (schema) of a database can be expressed graphically by an E-R diagram, which is built up from the following components: (73)represent entity set, (74)represent attributes, etc. In addition to entities and relations, the E-R model represents certain (75) to which the contents of a database must conform. The entity-relationship model is widely used in database design.
71.A.data B.things C.entities D.objects
72.A.keys B.attributes C.records D.Rows
73.A.rectangles B.ellipses C.diamonds D.lines
74.A.rectangles B.ellipses C.diamonds D.lines
75.A.things B.objects C.conditions D.constrains
答案:C,B,A,B,D
实体-关系(E-R)数据模型是基于对现实世界的一种感知,它由一组基本的对象组成,这些对象被称为实体(71,实体),以及这些对象之间的关系。在现实世界中,实体是一个可以与其他对象区分开的“事物”或“对象”。数据库中通过一组属性(72,属性)来描述实体。关系是几个实体之间的关联。所有相同类型的实体的集合和所有相同类型的关系集合分别被称为实体集和关系集。数据库的整体逻辑结构(模式)可以通过E-R图以图形方式表示,该图由以下组件构成:矩形(73,矩形)代表实体集,椭圆形(74,椭圆形)代表属性等。除了实体和关系之外,E-R模型还表示了数据库内容必须遵守的某些约束条件(75,约束)。实体-关系模型在数据库设计中被广泛使用。
(2018数据库系统工程师科目一71-75真题)
71~75.A transaction is an action, or a series of actions, carried out
by a single user or (71) that accesses or changes the contents of
the database. A transaction should possess the four basic or so-called ACID properties: Atomicity. The "all or nothing" property. A transaction is an (72) unit that is either performed in its entirety or is not performed at all. Consistency. A transaction must transform the database from one consistent state to another consistent state. Isolation. Transactions execute independently of one another. In other words, the partial effects of (73) transactions should not be visible to other transactions. Durability. The effects of a successfully completed (committed) transaction are permanently recorded in the database and must not be lost because of a subsequent failure. The four properties above, only (74)property is the responsibility of the concurrency control subsystem to ensure. It is the responsibility of both the (75) and the application developers to ensure consistency. To guarantee the Atomicity and Durability properties after a failure,a log file is needed.
71.A.application developer B.all users C.application program D.DBMS
72.A.Indivisible B.permanent C.infrequent D.infinite
73.A.completed B.incomplete C.aborted D.committed
74.A.atomicity B.consistency C.isolation D.durability
75.A.DBMS B.DBA C.end user D.DBA
答案:C,A,B,C,A
一个事务是由单个用户或应用程序(71,应用程序)执行的一系列操作,用于访问或更改数据库的内容。一个事务应该具备四个基本的属性,也被称为ACID属性:原子性、一致性、隔离性和持久性。原子性是指一个事务要么全部完成,要么完全不完成。也就是说,一个事务是一个不可分割(72,不可分的)的单元,要么完全执行,要么不执行。一致性是指一个事务必须将数据库从一个一致的状态转换为另一个一致的状态。换句话说,不完整的(73,不完整的)事务的部分影响不应该对其他事务可见。隔离性是指事务彼此独立执行。换句话说,不完整事务的部分效果不应该对其他事务可见。持久性是指成功完成的(已提交的)事务的效果永久记录在数据库中,并且不会因为后续的失败而丢失。在上面的四个属性中,只有隔离性(74,隔离性)是由并发控制子系统来确保的。确保一致性是数据库管理系统(75,数据库管理系统)和应用程序开发人员的责任。为了在发生故障后保证原子性和持久性属性,需要一个日志文件。
(2017 数据库系统工程师科目一71-75真题)
The beauty of software is in its function, in its internal structure, and in the way in which it is created by a team. To a user a program with just the right features presented through an intuitive and (71) interface is beautiful. To a software designer, an internal structure that is partitioned in a simple and intuitive manner, and that minimizes internal coupling is beautiful. To developers and managers, a motivated team of developers making significant progress every week, and producing defect-free code,is beautiful. There is beauty on all these levels.
Our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones,watches,appliances,automobiles, toys, and tools. And need for new and better software never (72). As our civilization grows and expands, as developing nations build their infrastructures, as developed nations strive to achieve ever greater efficiencies,the need for more and more software (73) to increase. It would be a great shame if, in all that software, there was no beauty.
We know that software can be ugly. We know that it can be hard to use, unreliable, and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software systems that present their features through an awkward and cumbersome interface. We know that there are software systems that crash and misbehave. These are (74) systems. Unfortunately, as a profession, software developers tend to create more ugly systems than beautiful ones.
There is a secret at the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less time, and for less money, an an ugly one. Novice software developers don't understand this. They think that they have to do everything fast and quick. They think that beauty is (75). No! By doing things fast and quick, they make messes that make the software stiff, and hard to understand. Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical. Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least to build and maintain, and are delivered soonest.
71.A.simple B.hard C.complex D.duplicated
72.A.happens B.exists C.stops D.starts
73.A.starts B.continues C.appears D.stops
74.A.practical B.useful C.beautiful D.ugly
75.A.impractical B.perfect C.time-wasting D.practical
答案:A, C, B, D, A
软件之美在于其功能、内部结构和由团队创建的方式。对于用户来说,通过直观简单的(71,简洁的)界面展示出恰到好处的功能的程序是美丽的。对于软件设计师来说,以简单直观的方式进行分区的内部结构,以及最小化内部耦合的结构是美丽的。对于开发人员和管理人员来说,一个充满动力的团队每周都取得重大进展,并产生无缺陷的代码是美丽的。在这些层面上都有美的存在。
我们的世界需要软件——大量的软件。五十年前,软件只能在少数大型昂贵的机器上运行。三十年前,它在大多数公司和工业环境中运行。现在,我们的手机、手表、电器、汽车、玩具和工具中都有软件在运行。对新更好软件的需求从未停止过(72,停止)。随着文明的发展和扩张,发展中国家建设基础设施,发达国家努力实现更高的效率,对更多软件的需求不断(73,不断)增加。如果在所有这些软件中都没有美丽之处,那将是一种巨大的耻辱。
我们知道软件可以是丑陋的。我们知道它可能难以使用、不可靠、结构草率。我们知道有些软件系统的错综复杂且草率的内部结构使它们昂贵且难以改变。我们知道有些软件系统通过笨拙繁琐的界面展示其功能。我们知道有些软件系统崩溃或行为异常。这些都是丑陋的(74,丑陋的)系统。不幸的是,作为一项职业,软件开发人员往往创造更多的丑陋系统而不是美丽的系统。
最好的软件开发人员知道一个秘密:美丽比丑陋更便宜、更快。一个美丽的软件系统可以在较短的时间内建立和维护,而丑陋的一个则需要更多的时间和金钱。新手软件开发人员不理解这一点。他们认为他们必须快速完成所有事情。他们认为美丽是不实用的(75,不实用的)。不!通过快速完成任务,他们制造了混乱,使软件变得僵硬且难以理解。美丽的系统是灵活且易于理解的。构建和维护它们是令人愉快的。不实用的东西是丑陋的。丑陋会拖慢你的进度,使你的软件昂贵且脆弱。美丽的系统建造和维护成本最低,交付时间也最短。
数据库系统工程师考试概况
考试时间:
数据库系统工程师考试通常是在上半年五月第一个周末。
科目一的考试时间是上午9:00至11:30,科目二的考试时间是下午2:00至4:30。
考试教程:




