Each question below shows the correct answer with a full explanation. Use these to build conceptual understanding before attempting a timed quiz.
Configuration ManagementEasy
Q1. What is a commit in version control?
- A.A personal promise or commitment to other people
- B.A production deployment to end users and clients
- C.A recorded change or set of changes to the repository✓ Correct
- D.A test execution run and its result log report
Explanation
A commit records a snapshot of changes to the repository.
Report an error in this question
Configuration ManagementEasy
Q2. What is merging in version control?
- A.Deleting branches in the system context
- B.Creating new files during implementation
- C.Combining companies throughout the project
- D.Integrating changes from one branch into another✓ Correct
Explanation
Merging combines changes from one branch into another.
Report an error in this question
Configuration ManagementMedium
Q3. What is the purpose of a Change Control Board (CCB)?
- A.A physical whiteboard in the office space and room by the organization
- B.A dedicated software testing team or group of people at every stage
- C.A development source coding team or group of people across all phases
- D.A group responsible for evaluating and approving or rejecting change requests✓ Correct
Explanation
The CCB evaluates and authorizes changes to configuration items.
Report an error in this question
Configuration ManagementEasy
Q4. What is Git?
- A.A programming language within the project
- B.A testing tool for the development team
- C.A distributed version control system✓ Correct
- D.A command during the software lifecycle
Explanation
Git is a distributed version control system.
Report an error in this question
Configuration ManagementEasy
Q5. What is a repository?
- A.A specific software testing environment and setup only in practice typically
- B.A central location where version-controlled files and their history are stored✓ Correct
- C.A production deployment server location and address as a standard approach
- D.A physical library building for books and resources for quality purposes
Explanation
A repository stores version-controlled files and their complete history.
Report an error in this question
Configuration ManagementEasy
Q6. What is a configuration item (CI)?
- A.Any artifact placed under configuration management control✓ Correct
- B.A user story in the product backlog items listing
- C.A piece of physical hardware equipment and component
- D.A specific automated test case scenario and script
Explanation
A configuration item is any artifact managed under configuration management.
Report an error in this question
Configuration ManagementEasy
Q7. What is a branch in version control?
- A.A physical tree branch in nature and the outdoors
- B.A separate line of development diverging from the main codebase✓ Correct
- C.A specific type of reported software bug and defect
- D.A deployment stage in the release pipeline process
Explanation
A branch is an independent line of development.
Report an error in this question
Configuration ManagementMedium
Q8. What is a merge conflict?
- A.A situation where two branches have competing changes that cannot be automatically merged✓ Correct
- B.A software testing failure or assertion error result according to best practices
- C.A disagreement or argument between the team members in a systematic way
- D.A production deployment failure or error issue event for the project goals
Explanation
Merge conflicts occur when branches have competing changes.
Report an error in this question
Configuration ManagementEasy
Q9. What is a change request?
- A.A formal proposal to modify a software configuration item✓ Correct
- B.A new feature request from end users and clients
- C.A request to change current employment job position
- D.A software defect bug report document filed only
Explanation
A change request proposes a modification to a configuration item.
Report an error in this question
Configuration ManagementEasy
Q10. What is version control?
- A.A software architecture and design method approach in the engineering discipline
- B.Controlling video game software versions and builds and related components
- C.A type of software testing methodology and approach to achieve project objectives
- D.A system that records changes to files over time so specific versions can be recalled✓ Correct
Explanation
Version control tracks changes to files over time.
Report an error in this question
Configuration ManagementEasy
Q11. What is Software Configuration Management (SCM)?
- A.A creational object-oriented design pattern type
- B.The process of tracking and controlling changes to software✓ Correct
- C.A source code implementation coding technique only
- D.A comprehensive software testing method type only
Explanation
SCM tracks and controls changes in software.
Report an error in this question
Configuration ManagementEasy
Q12. What is a baseline in configuration management?
- A.A specific line of application source code and logic as part of the methodology
- B.A starting position in a sports competition event for effective project outcomes
- C.A software testing benchmark result point and score in the development process
- D.A formally reviewed and agreed-upon specification serving as the basis for further development✓ Correct
Explanation
A baseline is a formally approved version serving as a reference point.
Report an error in this question
Configuration ManagementMedium
Q13. What is GitFlow?
- A.A software testing flow and process model and approach in the system context
- B.A water flow through pipes and channels and drains throughout the project
- C.A production deployment pipeline and flow and process during implementation
- D.A branching model for Git that defines a strict branching structure for projects✓ Correct
Explanation
GitFlow defines a strict branching structure for projects.
Report an error in this question
Configuration ManagementMedium
Q14. What is a software configuration audit?
- A.A financial accounting audit process and procedure only during the software lifecycle
- B.A system performance load test execution and run report for the development team
- C.A formal source code peer review session and meeting only within the project scope
- D.A review to verify that configuration items conform to specifications and standards✓ Correct
Explanation
Configuration audits verify items conform to specifications.
Report an error in this question
Configuration ManagementMedium
Q15. What is trunk-based development?
- A.A branching strategy where developers merge small, frequent updates to a core trunk or main branch✓ Correct
- B.Developing software in physical tree trunks outdoors for quality purposes in practice typically
- C.A comprehensive software testing approach and method only as a standard approach
- D.A software architecture and design method approach only by the organization
Explanation
Trunk-based development uses one main branch with small, frequent commits.
Report an error in this question
Configuration ManagementMedium
Q16. What is a build system in configuration management?
- A.A physical construction building system and process and related components
- B.A project documentation management system and process in the engineering discipline
- C.A tool that automates the process of compiling source code into executable software✓ Correct
- D.A comprehensive software testing system and tool suite to achieve project objectives
Explanation
A build system automates compiling and packaging source code.
Report an error in this question
Configuration ManagementMedium
Q17. What is release management?
- A.A comprehensive software testing method and approach type in the development process
- B.Releasing employees from their positions and roles for effective project outcomes
- C.A source code implementation coding technique and method as part of the methodology
- D.The process of planning, scheduling, and controlling software builds through different stages✓ Correct
Explanation
Release management oversees planning and deployment of software releases.
Report an error in this question
Configuration ManagementMedium
Q18. What is continuous integration in the context of SCM?
- A.Frequently merging code changes to a shared repository with automated builds and tests✓ Correct
- B.Manually merging code without any automation tools by the development process
- C.Performing one-time integration at the very end and its related activities
- D.Performing annual scheduled integration events only within the system boundary
Explanation
CI frequently merges changes with automated builds and tests.
Report an error in this question
Configuration ManagementHard
Q19. What is the concept of 'configuration identification'?
- A.Identifying individual automated test case scenarios in a systematic way
- B.Selecting and labeling configuration items and documenting their characteristics✓ Correct
- C.Identifying specific software bugs and defect reports across all phases
- D.Identifying individual team member profile records at every stage
Explanation
Configuration identification selects, labels, and documents configuration items.
Report an error in this question
Configuration ManagementHard
Q20. What is the difference between configuration management and change management?
- A.CM only involves application source code files and code by the development process
- B.Change management is always much broader in its scope within the system boundary
- C.CM manages all configuration items; change management specifically handles the change request process✓ Correct
- D.The two concepts are completely identical in all ways for the project goals according to best practices
Explanation
CM manages all items; change management focuses on the change request process.
Report an error in this question
Configuration ManagementMedium
Q21. What is a tag in version control?
- A.A price tag attached to a retail product for sale over the entire lifecycle
- B.A commit message attached to a changeset in version control for all project stakeholders
- C.A marker that identifies a specific point in the repository's history, typically a release✓ Correct
- D.A specific type of development branch in the project as defined by standards
Explanation
A tag marks a significant point in the repository's history.
Report an error in this question
Configuration ManagementMedium
Q22. What is the difference between centralized and distributed version control?
- A.Centralized version control is the newer approach today by the project team members
- B.Distributed version control has only one server overall in all development efforts
- C.The two systems are completely identical in every way within the given constraints
- D.Centralized has one server; distributed gives each developer a full copy of the repository✓ Correct
Explanation
Centralized has one server; distributed gives each developer a full copy.
Report an error in this question
Configuration ManagementHard
Q23. What is semantic versioning?
- A.Alphabetical versioning of all software release names for effective project outcomes
- B.Using random numbering for all software version names in the engineering discipline
- C.A versioning scheme using MAJOR.MINOR.PATCH to convey meaning about underlying changes✓ Correct
- D.Date-based versioning of all software release versions as part of the methodology
Explanation
SemVer uses MAJOR.MINOR.PATCH where each segment conveys change meaning.
Report an error in this question
Configuration ManagementHard
Q24. What is Infrastructure as Code (IaC)?
- A.Building physical infrastructure roads and buildings for all project stakeholders
- B.A general-purpose coding language definition and spec within the given constraints
- C.A comprehensive software testing framework and tool set in all development efforts
- D.Managing and provisioning computing infrastructure through machine-readable configuration files✓ Correct
Explanation
IaC manages infrastructure through configuration files.
Report an error in this question
Configuration ManagementHard
Q25. What is the concept of 'GitOps'?
- A.A comprehensive software testing approach and method only in practice typically as a standard approach
- B.An operational framework where Git is the single source of truth for infrastructure and application deployment✓ Correct
- C.An established coding standard and guideline set for teams by the organization at every stage
- D.Only performing basic Git operations and nothing else during implementation for quality purposes
Explanation
GitOps uses Git as the single source of truth for infrastructure and deployment.
Report an error in this question
Configuration ManagementHard
Q26. What is a monorepo strategy?
- A.Multiple separate repos per each single project type
- B.Storing multiple projects in a single version control repository✓ Correct
- C.One separate repository per individual project file
- D.Having absolutely no repository at all for the code
Explanation
A monorepo stores all projects in a single repository.
Report an error in this question
Configuration ManagementHard
Q27. What is the concept of 'configuration status accounting'?
- A.Recording and reporting the status of configuration items and change requests throughout the project✓ Correct
- B.Financial accounting and bookkeeping tasks and work in the development process
- C.Tracking developer working hours per task and activity within the project scope
- D.Counting total source code lines in the whole project during the software lifecycle
Explanation
Configuration status accounting tracks and reports the status of items and changes.
Report an error in this question
Configuration ManagementHard
Q28. What is the concept of 'immutable infrastructure'?
- A.An approach where infrastructure components are replaced rather than modified, ensuring consistency✓ Correct
- B.Permanent physical hardware installations and setups and related components
- C.Infrastructure that physically cannot ever change form by the project team members
- D.A specific type of database storage system and service to achieve project objectives
Explanation
Immutable infrastructure replaces components rather than updating them in place.
Report an error in this question
Configuration ManagementHard
Q29. What is a Software Bill of Materials (SBOM)?
- A.A project budget and financial document and report over the entire lifecycle
- B.A grocery shopping list for the team members only and its related activities
- C.A team member roster and directory listing sheet as defined by standards
- D.A formal record of the components and dependencies in a piece of software✓ Correct
Explanation
An SBOM is an inventory of all components and dependencies.
Report an error in this question
Configuration ManagementHard
Q30. What is a feature flag (feature toggle)?
- A.A physical flag or banner for signaling and marking for the development team
- B.A test indicator for pass or fail status result only in the system context
- C.A technique allowing features to be enabled or disabled without deploying new code✓ Correct
- D.A marker for identifying software bugs and issues only throughout the project
Explanation
Feature flags enable or disable features without deploying new code.
Report an error in this question