Explore topic-wise InterviewSolutions in .

GPOs store group policy SETTINGS in two LOCATIONS: a Group Policy container (GPC) (preferred) and a Group Policy template (GPT). The GPC is an Active Directory OBJECT that stores version information, status information, and other policy information (for example, application objects).

The GPT is used for file-based data and stores software policy, SCRIPT, and deployment information. The GPT is located on the system volume folder of the domain controller. A GPO can be associated with one or more Active Directory containers, such as a site, domain, or organizational unit. Multiple containers can be associated with the same GPO, and a single container can have more than one associated GPO.

GPOs store group policy settings in two locations: a Group Policy container (GPC) (preferred) and a Group Policy template (GPT). The GPC is an Active Directory object that stores version information, status information, and other policy information (for example, application objects).

The GPT is used for file-based data and stores software policy, script, and deployment information. The GPT is located on the system volume folder of the domain controller. A GPO can be associated with one or more Active Directory containers, such as a site, domain, or organizational unit. Multiple containers can be associated with the same GPO, and a single container can have more than one associated GPO.

MODEL: provides the central functionality of the APPLICATION and is aware of each of its dependent VIEW and controller components.
View: corresponds to a particular style and format of presentation of information to the user.The view CREATES its associated controller.
Controller: accepts user input in the form of EVENTS that trigger the execution of operations within the model.

Model: provides the central functionality of the application and is aware of each of its dependent view and controller components.
View: corresponds to a particular style and format of presentation of information to the user.The view creates its associated controller.
Controller: accepts user input in the form of events that trigger the execution of operations within the model.

Frameworks are partially COMPLETED software systems that MAY be TARGETED at a SPECIFIED TYPE of application.

Frameworks are partially completed software systems that may be targeted at a specified type of application.

Three type of Design patterns are:
• CREATIONAL pattern
• STRUCTURAL pattern
• BEHAVIOURAL pattern.

Three type of Design patterns are:
• Creational pattern
• Structural pattern
• Behavioural pattern.

KEY principles that underlie patterns are:
• abstraction
• ENCAPSULATION
• information hiding
• modularization
• separation of concerns
• COUPLING and cohesion
• Sufficiency
• Completeness and primitiveness
• Separation of policy and implementation
• Separation of interface and implementation
• SINGLE point of reference
• Divide and conquer.

Key principles that underlie patterns are:
• abstraction
• encapsulation
• information hiding
• modularization
• separation of concerns
• Coupling and cohesion
• Sufficiency
• Completeness and primitiveness
• Separation of policy and implementation
• Separation of interface and implementation
• Single point of reference
• Divide and conquer.

The non-functional properties of a SOFTWARE architecture are:
• changeability
• interoperability
• EFFICIENCY
• RELIABILITY
• testability
• REUSABILITY.

The non-functional properties of a software architecture are:
• changeability
• interoperability
• efficiency
• reliability
• testability
• reusability.

BROKER: Use a broker class RESPONSIBLE for MATERIALIZING instances of each class from the database.
Proxy: Proxy OBJECTS act as PLACEHOLDERS for the real objects, e.g. IntCampaigns in Locations.

Broker: Use a broker class responsible for materializing instances of each class from the database.
Proxy: Proxy objects act as placeholders for the real objects, e.g. IntCampaigns in Locations.

Relational DBMS: Complex objects have to be taken apart and the parts stored in different TABLES are called relational database management SYSTEM.
Object DBMS: Object DATABASES are closely LINKED to PROGRAMMING languages with ways of navigating through the database.

Relational DBMS: Complex objects have to be taken apart and the parts stored in different tables are called relational database management system.
Object DBMS: Object databases are closely linked to programming languages with ways of navigating through the database.

The THREE step of normalization are:
• First NORMAL form
• Second normal form
• THIRD normal form.

The three step of normalization are:
• First normal form
• Second normal form
• Third normal form.

There are three TYPES of file organization. These are:
• SERIAL organization
• SEQUENTIAL organization
• Random organization.

There are three types of file organization. These are:
• Serial organization
• Sequential organization
• Random organization.

There are THREE TYPES of FILE access methods. These are:
• Serial access
• Index-sequential access
• Direct access.

There are three types of file access methods. These are:
• Serial access
• Index-sequential access
• Direct access.

Backing up Active Directory is essential to maintain an Active Directory database. You can back upActive Directory by using the Graphical User Interface (GUI) and command-line tools that theWindows Server 2003 family provides.
You frequently backup the system state data on domain controllers so that you can restore the most current data. By establishing a REGULAR backup schedule, you have a better CHANCE of recovering data when necessary.
To ensure a good backup includes at least the system state data and contents of the system disk, you must be aware of the tombstone lifetime. By default, the tombstone is 60 DAYS. Any backup older than 60 days is not a good backup. Plan to backup at least two domain controllers in each domain, one of at least one backup to enable an AUTHORITATIVE restore of the data when necessary.

Backing up Active Directory is essential to maintain an Active Directory database. You can back upActive Directory by using the Graphical User Interface (GUI) and command-line tools that theWindows Server 2003 family provides.
You frequently backup the system state data on domain controllers so that you can restore the most current data. By establishing a regular backup schedule, you have a better chance of recovering data when necessary.
To ensure a good backup includes at least the system state data and contents of the system disk, you must be aware of the tombstone lifetime. By default, the tombstone is 60 days. Any backup older than 60 days is not a good backup. Plan to backup at least two domain controllers in each domain, one of at least one backup to enable an authoritative restore of the data when necessary.

XML SIGNATURE is recommended by W3C. It acts as a digital signature for XML documents. This technology is USED by various technologies such as SAML, SOAP, etc.

XML signature is recommended by w3c. It acts as a digital signature for XML documents. This technology is used by various technologies such as SAML, SOAP, etc.

There are THREE TYPES of DBMS. These are:
• RELATIONAL DATABASES
• Object databases
• Object-relational databases.

There are three types of DBMS. These are:
• Relational databases
• Object databases
• Object-relational databases.

Dynamical behavior VIEW plays a very important in determining RELATIONSHIPS and behavior of the system. This view DEPICTS collaboration among OBJECTS and the effective changes to the internal states of objects. This includes activity, sequence and state machine diagrams.

Dynamical behavior view plays a very important in determining relationships and behavior of the system. This view depicts collaboration among objects and the effective changes to the internal states of objects. This includes activity, sequence and state machine diagrams.

A relationship between two classes where one class offers the interface of the other but does not NECESSARILY have the same STRUCTURE of the other. COMMONLY used to show that a class SUPPORTS an interface. WRITTEN as a stereotype: «realize».

A relationship between two classes where one class offers the interface of the other but does not necessarily have the same structure of the other. Commonly used to show that a class supports an interface. Written as a stereotype: «realize».

That part of the boundary between TWO interacting SYSTEMS across which they communicate, the set of all signatures for the public OPERATIONS of a CLASS or PACKAGE.

That part of the boundary between two interacting systems across which they communicate, the set of all signatures for the public operations of a class or package.

A constraint that has to be enforced to ensure that the information SYSTEM HOLDS data that is mutually CONSISTENT and is MANIPULATED correctly.

A constraint that has to be enforced to ensure that the information system holds data that is mutually consistent and is manipulated correctly.

The COMPONENTS of MVC architecture are:
• Model
• VIEW
• CONTROLLER

The components of MVC architecture are:
• Model
• View
• Controller

Referential INTEGRITY: Referential integrity ENSURES that an object identifier in one object ACTUALLY refers to an object that EXISTS.
Dependency constraints: Dependency constraints ensure that attribute dependencies, values are maintained CONSISTENTLY, where the value of one attribute is calculated from other attributes, are maintained consistently.
Domain integrity: Domain integrity ensures that attributes only hold permissible values.

Referential Integrity: Referential integrity ensures that an object identifier in one object actually refers to an object that exists.
Dependency constraints: Dependency constraints ensure that attribute dependencies, values are maintained consistently, where the value of one attribute is calculated from other attributes, are maintained consistently.
Domain integrity: Domain integrity ensures that attributes only hold permissible values.

Component diagram: a diagram that SHOWS the ORGANIZATION of and dependencies among components. One of two UML implementation DIAGRAMS (q.v.).
Deployment diagram: A diagram that shows the run-time configuration of processing NODES (q.v.) and the components, processes and objects that are LOCATED on them. One of two UML implementation diagrams (q.v.).

Component diagram: a diagram that shows the organization of and dependencies among components. One of two UML implementation diagrams (q.v.).
Deployment diagram: A diagram that shows the run-time configuration of processing nodes (q.v.) and the components, processes and objects that are located on them. One of two UML implementation diagrams (q.v.).

There are TWO TYPES of TESTS. These are:
• BLACK box testing and
• White box testing

There are two types of tests. These are:
• Black box testing and
• White box testing

Write programs that CREATE instances of classes and SEND them MESSAGES to TEST operations EXECUTE correctly is called test harnesses.

Write programs that create instances of classes and send them messages to test operations execute correctly is called test harnesses.

The FOUR main strategies for switching over to the new system are as FOLLOWS:
• Direct changeover
• Parallel RUNNING
• PHASE changeover
• PILOT project.

The four main strategies for switching over to the new system are as follows:
• Direct changeover
• Parallel running
• Phase changeover
• Pilot project.

TWO STYLES of COMMUNICATION are:
• Client-server communication.
• Peer-peer communication.

Two styles of communication are:
• Client-server communication.
• Peer-peer communication.

Cohesion: a measure of the degree to which an element of a MODEL CONTRIBUTES to a single purpose.
Coupling: relates to the degree of interconnectedness between design COMPONENTS and is reflected by the NUMBER of links and the degree of interaction an OBJECT has with other objects.

Cohesion: a measure of the degree to which an element of a model contributes to a single purpose.
Coupling: relates to the degree of interconnectedness between design components and is reflected by the number of links and the degree of interaction an object has with other objects.

The same model—the class model—is used through the life of the PROJECT During design, additional detail is added to the analysis classes, and EXTRA classes are added to provide the supporting functionality for the user interface and data management Other diagrams are also ELABORATED in design activities.

The same model—the class model—is used through the life of the project During design, additional detail is added to the analysis classes, and extra classes are added to provide the supporting functionality for the user interface and data management Other diagrams are also elaborated in design activities.

If an OBJECT MAY be in TWO or more states at the same time, then these states are CONCURRENT states.

If an object may be in two or more states at the same time, then these states are concurrent states.

Two approaches may be USED:
• BEHAVIOURAL approach
• LIFE CYCLE approach

Two approaches may be used:
• Behavioural approach
• Life cycle approach

There are four TYPES of EVENT:
• A change
• A call event
• A signal event
• An elapsed-time event

There are four types of event:
• A change
• A call event
• A signal event
• An elapsed-time event

Event: An event is occurrence of a stimulus that can trigger a state change and that is relevant to the OBJECT.
State: A state reflects condition of an object at a given MOMENT. The state of an object is determined by values of its attributes and presence or absence of links to other objects.
TRANSITION: The movement from one state to ANOTHER state is called transition. A transition is TRIGGERED by an event. A transition may start and end at the same state.

Event: An event is occurrence of a stimulus that can trigger a state change and that is relevant to the object.
State: A state reflects condition of an object at a given moment. The state of an object is determined by values of its attributes and presence or absence of links to other objects.
Transition: The movement from one state to another state is called transition. A transition is triggered by an event. A transition may start and end at the same state.

THREE components of most OCL EXPRESSION are:
• CONTEXT.
• Property.
• Operation.

Three components of most OCL Expression are:
• Context.
• Property.
• Operation.

A formal language that supplements the graphical notations of UML. OCL is generally used to give PRECISE definitions for OPERATION logic, or for PROPERTIES such as invariants (q.v.).

A formal language that supplements the graphical notations of UML. OCL is generally used to give precise definitions for operation logic, or for properties such as invariants (q.v.).

Algorithmic techniques are:

• Suitable where users understand the PROCEDURE for arriving at a result.
• Can be constructed top-down, to HANDLE arbitrarily COMPLEX FUNCTIONALITY.

EXAMPLES:

• Structured English.
• Activity Diagrams.

Algorithmic techniques are:

Examples:

Non-algorithmic techniques are:
• Appropriate where correct result MATTERS more than method to arrive at it.
• Decision TREE: complex decisions, multiple CRITERIA and steps (not described further here).
• Decision table: similar applications to decision tree.
• Pre- and Post-condition PAIRS: suitable where precise logic is unimportant or uncertain.

Non-algorithmic techniques are:
• Appropriate where correct result matters more than method to arrive at it.
• Decision tree: complex decisions, multiple criteria and steps (not described further here).
• Decision table: similar applications to decision tree.
• Pre- and Post-condition pairs: suitable where precise logic is unimportant or uncertain.

TWO CATEGORY of LOGICAL SPECIFICATION are:
• ALGORITHMIC.
• Non-algorithmic.

Two category of logical specification are:
• Algorithmic.
• Non-algorithmic.

A BLACK box description of a SERVICE (of a class or sub-system) that SPECIFIES the RESULTS of the service and the conditions under which it will be provided.

A black box description of a service (of a class or sub-system) that specifies the results of the service and the conditions under which it will be provided.

A lifeline is a vertical DASHED line that represents the existence of an object on an INTERACTION SEQUENCE diagrams. An object symbol containing the object’s NAME is placed at the top of a lifeline.

A lifeline is a vertical dashed line that represents the existence of an object on an interaction sequence diagrams. An object symbol containing the object’s name is placed at the top of a lifeline.

The focus of control indicates times during ACTIVATION when processing is TAKING PLACE within that OBJECT. Parts of an object activation that are not within the focus of control represent PERIODS when, for example, an operation is waiting for a return from another object.

The focus of control indicates times during activation when processing is taking place within that object. Parts of an object activation that are not within the focus of control represent periods when, for example, an operation is waiting for a return from another object.

Sequence diagram shows an INTERACTION between objects ARRANGED in a time sequence. Sequence diagram can be drawn at different levels of detail and also to meet different PURPOSES at several STAGES in the DEVELOPMENT life cycle.

Sequence diagram shows an interaction between objects arranged in a time sequence. Sequence diagram can be drawn at different levels of detail and also to meet different purposes at several stages in the development life cycle.

An INTERACTION is defined in the context of COLLABORATION. It specifies the communication PATTERNS between the roles in the Collaboration.

An Interaction is defined in the context of Collaboration. It specifies the communication patterns between the roles in the Collaboration.

COMPONENT is an executable SOFTWARE MODULE with a well-defined interface and IDENTITY.

Component is an executable software module with a well-defined interface and identity.

A relationship between two model ELEMENTS, such that a CHANGE in one ELEMENT MAY require a change in the dependent element.

A relationship between two model elements, such that a change in one element may require a change in the dependent element.

NIH Syndrome: Some SOFTWARE developers are not inclined to trust software that was WRITTEN elsewhere.

NIH Syndrome: Some software developers are not inclined to trust software that was written elsewhere.

MULTIPLE inheritance OCCURS when a SUBCLASS INHERITS from more than one generalization hierarchy. All features are inherited from every superclass.

Multiple inheritance occurs when a subclass inherits from more than one generalization hierarchy. All features are inherited from every superclass.

The elements of PATTERN are:
• CONTEXT.
• FORCES.
• SOFTWARE configuration.

The elements of pattern are:
• Context.
• Forces.
• Software configuration.

Documents unsuccessful attempts at providing SOLUTIONS to CERTAIN recurring PROBLEMS but INCLUDES reworked solutions that are effective.

Documents unsuccessful attempts at providing solutions to certain recurring problems but includes reworked solutions that are effective.

Collaboration: the structure and links between a group of instances that participate in a behaviour. The behaviour can be that of an OPERATION or a use case (or any other behavioral CLASSIFIER in UML).
Collaboration DIAGRAM: a collaboration diagram SHOWS an interaction between objects and the CONTEXT of the interaction in terms of the links between the objects. 

Collaboration: the structure and links between a group of instances that participate in a behaviour. The behaviour can be that of an operation or a use case (or any other behavioral classifier in UML).
Collaboration diagram: a collaboration diagram shows an interaction between objects and the context of the interaction in terms of the links between the objects. 

CRC STANDS for Class–Responsibility–Collaboration. CRC CARDS help to model interaction between objects.

CRC stands for Class–Responsibility–Collaboration. CRC cards help to model interaction between objects.

A UML DIAGRAM that SHOWS classes with their ATTRIBUTES and operations, together with the associations between classes.

A UML diagram that shows classes with their attributes and operations, together with the associations between classes.