structure domain

域（Domain）

Domain域

Windows环境下，Weblogic系统中Domain的配置参数文件是（）。

A:Domain所在目录下\config\config.xml B:Domain所在目录下\bin\setDomainEnv.cmd C:Domain所在目录下\bin\commEnv.cmd D:Domain所在目录下\config\commEnv.cmd

在基于Windows2003的APG中，GlobalCatalog在一个Domain中的作用是（）.

A:包含在同一个Domain中所有DC的AD数据 B:当属于其他域的用户在本域登录时，对其进行解析 C:保存UniversalGroups的信息 D:以上都不对

利用VLAN技术可以把物理上连接的网络从逻辑上划分为多个不同的虚拟子网，可以对各个子网实施不同的管理策略。以下是某台交换机(Switch)的部分配置过程，其中空缺处的命令/参数可能是 (48) 。
Switch #vlan database
Switch (vlan) #vtp
Switch (vlan) # (48)
Changing VTP domain name from NULL to Server1
Switch (vlan) # exit

A:vtp Server B:vtp domain Server1 C:vtp domain Server D:vtp domain

利用VLAN技术可以把物理上连接的网络从逻辑上划分为多个不同的虚拟子网，可以对各个子网实施不同的管理策略。以下是某台交换机(Switch)的部分配置过程，其中空缺处的命令/参数可能是（）。
Switch #vlan database
Switch (vlan) #vtp
Switch (vlan) # （）
Changing VTP domain name from NULL to Server1
Switch (vlan) # exit

A:vtp Server B:vtp domain Server1 C:vtp domain Server D:vtp domain

The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （1）defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （2）in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The（3） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （4）may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （5）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem

The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (1) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (2) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (3) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (4) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (5) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem

The software architecture is a set of software components, subsystems, relationships,interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （） defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （） in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The （） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （） may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem