Configuration management and version control in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Version Control Systems

Which of the following best describes the primary purpose of a version control system (VCS)?

A To monitor network traffic and detect security breaches.

B To track and manage changes to files over time, allowing multiple people to collaborate safely.

C To automatically fix bugs in software code without human intervention.

D To compile source code into executable programs efficiently.

💡 Hint

Think about what happens when many people work on the same files and need to keep track of changes.

A version control system helps keep a history of changes, supports collaboration, and prevents conflicts by managing file versions.

📋 Factual

intermediate

Common Tools in Configuration Management

Which of the following is a widely used tool specifically designed for configuration management in software development?

A Ansible

B Git

C Docker

D Jenkins

💡 Hint

Look for the tool that automates setup and maintenance of software environments.

Ansible is a popular configuration management tool that automates software provisioning and configuration.

🚀 Application

advanced

Analyzing Branching Strategies

Consider a team using Git for version control. They want to keep the main branch stable and develop new features separately. Which branching strategy best supports this goal?

A Feature branching, where each new feature is developed in its own branch and merged into main after testing.

B Trunk-based development, where all developers commit directly to the main branch frequently.

C Forking workflow, where developers create personal copies of the repository and never merge back.

D No branching, all work is done directly on the main branch.

💡 Hint

Think about isolating new work to avoid breaking the stable code.

Feature branching isolates new features in separate branches, allowing testing before merging to keep main stable.

🔍 Analysis

advanced

Identifying Risks in Configuration Management

A company uses manual scripts to configure servers instead of automated configuration management tools. What is the most likely risk of this approach?

A Better security because scripts are customized each time.

B Faster deployment times due to manual control.

C Increased chance of inconsistent configurations and human errors across servers.

D Reduced need for documentation since scripts are simple.

💡 Hint

Consider what happens when humans repeat complex tasks manually.

Manual configuration is error-prone and can lead to servers being set up differently, causing problems.

❓ Reasoning

expert

Evaluating Version Control Commit Practices

A developer commits large changes with many unrelated updates in a single commit. What is the main disadvantage of this practice?

A It ensures all team members get the same updates at once.

B It improves code readability by grouping all changes together.

C It speeds up the deployment process by reducing commit count.

D It makes it harder to understand, review, and revert specific changes later.

💡 Hint

Think about how others read and manage changes in version control history.

Large commits with unrelated changes are difficult to review and isolate if bugs appear, complicating maintenance.

Practice

1. What is the main purpose of version control in software development?

easy

A. To write code faster

B. To test software automatically

C. To design user interfaces

D. To track and manage changes to code over time

Solution

1. Step 1: Understand version control basics

   Version control systems keep a history of changes made to code files.

2. Step 2: Identify the main goal

   The main goal is to track and manage changes so developers can collaborate and revert if needed.

3. Final Answer:

   To track and manage changes to code over time -> Option D

4. Quick Check:

   Version control = track changes [OK]

Hint: Version control means saving code changes safely [OK]

Common Mistakes:

• Confusing version control with coding speed
• Thinking it is for UI design
• Assuming it automates testing

2. Which of the following is the correct Git command to save your changes to the local repository?

easy

A. git commit

B. git clone

C. git push

D. git pull

Solution

1. Step 1: Understand Git commands

   git commit saves changes to the local repository with a message.

2. Step 2: Differentiate commands

   git push sends commits to a remote repository, git clone copies a repo, git pull fetches updates.

3. Final Answer:

   git commit -> Option A

4. Quick Check:

   Save changes locally = git commit [OK]

Hint: Commit means save locally, push means send remotely [OK]

Common Mistakes:

• Using git push to save locally
• Confusing git clone with commit
• Thinking git pull saves changes

3. Consider this Git command sequence:
git add file.txt
git commit -m "Update file"
git push origin main
What is the result of running these commands?

medium

A. The file.txt changes are sent to the remote repository branch named main

B. The file.txt changes are saved locally but not sent to the remote repository

C. The file.txt is deleted from the repository

D. The repository is cloned to your computer

Solution

1. Step 1: Analyze each command

   git add stages file.txt changes, git commit saves them locally with a message, git push sends them to remote branch main.

2. Step 2: Understand the final effect

   After these commands, the changes in file.txt are updated in the remote repository on branch main.

3. Final Answer:

   The file.txt changes are sent to the remote repository branch named main -> Option A

4. Quick Check:

   git push origin main = send changes to main branch [OK]

Hint: Push sends committed changes to remote branch [OK]

Common Mistakes:

• Thinking git push only saves locally
• Confusing git add with deleting files
• Assuming cloning happens here

4. A developer runs git commit -m "Fix bug" but gets an error saying "nothing to commit, working tree clean." What is the most likely cause?

medium

A. The repository is corrupted

B. The commit message is missing

C. No changes were staged with git add

D. The remote repository is unreachable

Solution

1. Step 1: Understand the error message

   "nothing to commit, working tree clean" means no changes are ready to be saved.

2. Step 2: Identify the cause

   Changes must be staged with git add before committing; without staging, commit has nothing to save.

3. Final Answer:

   No changes were staged with git add -> Option C

4. Quick Check:

   Commit error = no staged changes [OK]

Hint: Always git add before git commit [OK]

Common Mistakes:

• Assuming commit message is missing
• Thinking repository is corrupted
• Blaming remote repository issues

5. You want to create a new branch in Git to work on a feature without affecting the main code. Which sequence of commands correctly achieves this and switches to the new branch?

hard

A. git clone feature
git add .

B. git branch feature
git checkout feature

C. git push origin feature
git commit -m "Start feature"

D. git checkout main
git branch feature

Solution

1. Step 1: Understand branch creation and switching

   git branch feature creates a new branch named feature; git checkout feature switches to it.

2. Step 2: Evaluate options

   git branch feature git checkout feature correctly creates and switches to the new branch. git checkout main git branch feature creates branch but does not switch.

3. Final Answer:

   git branch feature git checkout feature -> Option B

4. Quick Check:

   Create and switch branch = branch + checkout [OK]

Hint: Create branch then checkout to switch [OK]

Common Mistakes:

• Not switching to the new branch after creation
• Using git push before committing
• Confusing clone with branch creation