Configuration Management Questions and Answers

Q: Select the components from the following which contributes in the building of software configuration management (SCM) :(i) Software configuration identification (SCI)(ii) Change control(iii) Configuration status accounting(iv) Configuration audit

All four contribute, so the answer is (i), (ii), (iii) and (iv).Software configuration management rests on identifying the configuration items, the work products to be controlled (i); controlling changes to them through a formal change-control process (ii); recording and reporting the status of each item and change, configuration status accounting (iii); and auditing that the configuration actually matches its documentation and that approved changes were made correctly (iv). These are the classic SCM functions.Each of the other options leaves out at least one of them.

Q: The concurrent version system (CVS) is widely used for version control, where it is originally designed for source code, but useful for any text-based file, then CVS system must perform :(i) Establishing a simple repository.(ii) Maintains all version of a file in a single named file by storing only the difference between progressive version of the original file.(iii) Protect against simultaneous changes to a file by establishing different directories for each developer thus insulating one from another.(iv) The CVS merges changes when each developer completes the work.

CVS performs all four, so the answer is (i), (ii), (iii) and (iv).Pressman's description of the Concurrent Versions System lists exactly these: it establishes a simple repository; it keeps all versions of a file in a single named file by storing only the differences between successive versions; it protects against simultaneous changes by giving each developer a separate working directory; and it merges the changes when each developer finishes.Each three-item option leaves out one of these functions.

Q: Software Configuration Management (SCM) provides systematic evolution of a software under development and provides for :(i) Visibility(ii) Controlled change(iii) Traceability(iv) Monitoring

The key is (i), (ii), (iii) and (iv), all four, and the exact list could not be traced to a source.Software configuration management keeps track of the items that make up a system and how they change. Visibility means everyone can see the state of each item and version. Controlled change means a change is requested, reviewed and approved before it is made. Traceability links a version back to the change request and forward to what depends on it. Monitoring is keeping watch on the changes and the status of configuration items. All four are standard aims of SCM.The other options each leave out at least one of these aims, so the option listing all four, C, is the answer.

Q: Which of the following scenario necessitates file locking to be enabled by an Integrated Development Environment (IDE) ?

File locking is needed to prevent concurrent access to a source code file.When several developers or processes might edit the same file at the same time, one person's changes could overwrite another's. Locking lets only one editor change the file at a time, so updates are not lost.Privacy and protection against unauthorised access are matters of permissions and access control, not locking. Versioning is handled by a version control system, which records successive versions whether or not a lock is held.

Q: .................. procedures are concerned with analysing the costs and benefits of proposed changes, approving those changes that are worthwhile and tracking which components of the system have been changed.

These are change management procedures.Change management analyses the costs and benefits of proposed changes, approves those that are worthwhile and tracks which components of the system have been changed, so that evolution is controlled and documented.Cost estimation predicts the effort and cost of development, testing checks the software for defects, and 'software' is not a procedure at all. None of them covers approving and tracking changes.

Q: What is the purpose of version control in software engineering ?

Version control is used to track the changes made to software code and manage multiple versions.A version control system such as Git records every change to the code with who made it and when, lets developers work in parallel on branches and merge their work, and allows any earlier version to be restored.It does not make the software run faster, it cannot guarantee freedom from bugs (that is the role of testing), and it has nothing to do with the user interface.

Select the components from the following which contributes in the building of software configuration management (SCM) :

(i) Software configuration identification (SCI)
(ii) Change control
(iii) Configuration status accounting
(iv) Configuration audit

A.(ii) and (iv)
B.(i), (ii), (iii) and (iv)
C.(i), (ii) and (iii)
D.(i), (iii) and (iv)

Exam Year(s)

MH SET - 2019, SET Exam - 2019,

Answer: B

All four contribute, so the answer is (i), (ii), (iii) and (iv).

Software configuration management rests on identifying the configuration items, the work products to be controlled (i); controlling changes to them through a formal change-control process (ii); recording and reporting the status of each item and change, configuration status accounting (iii); and auditing that the configuration actually matches its documentation and that approved changes were made correctly (iv). These are the classic SCM functions.

Each of the other options leaves out at least one of them.

Discuss in Forum

The concurrent version system (CVS) is widely used for version control, where it is originally designed for source code, but useful for any text-based file, then CVS system must perform :

(i) Establishing a simple repository.
(ii) Maintains all version of a file in a single named file by storing only the difference between progressive version of the original file.
(iii) Protect against simultaneous changes to a file by establishing different directories for each developer thus insulating one from another.
(iv) The CVS merges changes when each developer completes the work.

A.(i), (ii) and (iii)
B.(i), (ii), (iii) and (iv)
C.(i), (ii) and (iv)
D.(ii), (iii) and (iv)

Exam Year(s)

MH SET - 2020, SET Exam - 2020,

Answer: B

CVS performs all four, so the answer is (i), (ii), (iii) and (iv).

Pressman's description of the Concurrent Versions System lists exactly these: it establishes a simple repository; it keeps all versions of a file in a single named file by storing only the differences between successive versions; it protects against simultaneous changes by giving each developer a separate working directory; and it merges the changes when each developer finishes.

Each three-item option leaves out one of these functions.

Discuss in Forum

During the change control process, which of the following activities are required to be initiated ?

(i) While software configuration identification (SCI) is under development it can change freely since it is not under SCM.
(ii) While under review, the software configuration identification (SCI) is considered to be "Frozen".
(iii) Once SCI is reviewed and approved, it is entered into a library; the SCI is now formally under SCM.
(iv) Check in-check out process : once the change has been approved, the SCI has to be checked out from the library for change; once the change has been implemented, the SCI must be checked in to the library.

A.(i), (ii), (iii) and (iv)
B.(ii), (iii) and (iv)
C.(i), (ii) and (iii)
D.(i) and (iv)

Exam Year(s)

MH SET - 2021, SET Exam - 2021,

Answer: A

All four statements belong to the change control process, so the answer is (i), (ii), (iii) and (iv).

In software configuration management, a configuration item can change freely while it is being developed, since it is not yet under SCM (i). While it undergoes formal technical review it is treated as frozen (ii). Once reviewed and approved it becomes a baseline and is entered into the project library, after which it is formally under SCM (iii). From then on, changes go through check-out and check-in: an approved change checks the item out of the library and checks the modified version back in, which provides access and synchronisation control (iv).

Each option that leaves a statement out omits a genuine stage of the process.

Discuss in Forum

Software Configuration Management (SCM) provides systematic evolution of a software under development and provides for :

(i) Visibility
(ii) Controlled change
(iii) Traceability
(iv) Monitoring

A.(i), (ii) and (iii)
B.(i), (ii) and (iv)
C.(i), (ii), (iii) and (iv)
D.(ii) and (iii)

Exam Year(s)

MH SET - 2023, SET Exam - 2023,

Answer: C

The key is (i), (ii), (iii) and (iv), all four, and the exact list could not be traced to a source.

Software configuration management keeps track of the items that make up a system and how they change. Visibility means everyone can see the state of each item and version. Controlled change means a change is requested, reviewed and approved before it is made. Traceability links a version back to the change request and forward to what depends on it. Monitoring is keeping watch on the changes and the status of configuration items. All four are standard aims of SCM.

The other options each leave out at least one of these aims, so the option listing all four, C, is the answer.

Discuss in Forum

Which of the following scenario necessitates file locking to be enabled by an Integrated Development Environment (IDE) ?

A.To ensure the privacy of a source code file
B.To prevent un-authorized access to a source code file
C.To prevent concurrent access to a source code file
D.To enable proper versioning of a source code file

Exam Year(s)

MH SET - 2025, SET Exam - 2025,

Answer: C

File locking is needed to prevent concurrent access to a source code file.

When several developers or processes might edit the same file at the same time, one person's changes could overwrite another's. Locking lets only one editor change the file at a time, so updates are not lost.

Privacy and protection against unauthorised access are matters of permissions and access control, not locking. Versioning is handled by a version control system, which records successive versions whether or not a lock is held.

Discuss in Forum

.................. procedures are concerned with analysing the costs and benefits of proposed changes, approving those changes that are worthwhile and tracking which components of the system have been changed.

A.Change management
B.Cost estimation
C.Software
D.Testing

Exam Year(s)

MH SET - 2025, SET Exam - 2025,

Answer: A

These are change management procedures.

Change management analyses the costs and benefits of proposed changes, approves those that are worthwhile and tracks which components of the system have been changed, so that evolution is controlled and documented.

Cost estimation predicts the effort and cost of development, testing checks the software for defects, and 'software' is not a procedure at all. None of them covers approving and tracking changes.

Discuss in Forum

What is the purpose of version control in software engineering ?

A.To track the changes made to software code and manage multiple versions
B.To speed up the execution of the software
C.To ensure that the software is free from bugs
D.To improve the user interface of the software

Exam Year(s)

Tripura Public Service Commission - 2025,

Answer: A

Version control is used to track the changes made to software code and manage multiple versions.

A version control system such as Git records every change to the code with who made it and when, lets developers work in parallel on branches and merge their work, and allows any earlier version to be restored.

It does not make the software run faster, it cannot guarantee freedom from bugs (that is the role of testing), and it has nothing to do with the user interface.

Discuss in Forum

______ establishes information about when, why and by whom changes are made in a software.

A.Software Configuration Management.
B.Change Control.
C.Version Control.
D.An Audit Trail.

Exam Year(s)

UGC NET - 2012,

Answer: D

An audit trail establishes the information about when, why and by whom changes are made in a software. It is the record of the changes made to the items under configuration management, which allows the history to be traced. Software configuration management is the whole discipline, change control is the process of approving and making the changes, and version control is the naming and storing of the versions, so each of these is wider than or different from the record asked for. The keyed answer is an audit trail.

Discuss in Forum

Software Configuration Management is the discipline for systematically controlling

A.the changes due to the evolution of work products as the project proceeds.
B.the changes due to defects (bugs) being found and then fixed.
C.the changes due to requirement changes
D.all of the above

Exam Year(s)

UGC NET - 2013,

Answer: D

Software Configuration Management controls all the kinds of change listed, so 'all of the above' is correct. It systematically manages changes in work products as the project evolves, changes caused by defects that are found and fixed, and changes caused by revised requirements.

Each of the first three statements is true but incomplete by itself, since SCM does not restrict itself to just one cause of change. That is why the combined option is the right choice.

Discuss in Forum

10.

A process which defines a series of tasks that have the following four primary objectives is known as

1. to identify all items that collectively define the software configuration.
2. to manage changes to one or more of these items.
3. to facilitate the construction of different versions of an application.
4. to ensure that software quality is maintained as the configuration evolves over time.

A.Software Quality Management Process
B.Software Configuration Management Process
C.Software Version Management Process
D.Software Change Management Process

Exam Year(s)

UGC NET - 2013,

Answer: B

The process described is Software Configuration Management. Its stated aims, identifying the items that make up the software configuration, managing changes to them, helping to build different versions of an application and ensuring quality is kept as the configuration evolves, are exactly the objectives of configuration management.

Quality management concerns the wider quality system; version management is only one activity inside configuration management; and change management covers only the second objective, not all four.

Discuss in Forum

Loading…

Topics

Other Subjects

Tags: Configuration Management Questions and Answers || Configuration Management MCQ Questions and Answers || Configuration Management GK Questions and Answers || Configuration Management GK MCQ Questions || Configuration Management Multiple Choice Questions and Answers || Configuration Management GK || GK on Configuration Management || Software Engineering Questions and Answers || Software Engineering MCQ Questions and Answers || Software Engineering GK Questions and Answers || GK on Software Engineering

Configuration Management Questions and Answers

Topics

Other Subjects

About Us

Stay informed about all important Dates & Notifications