Legacy system modernization in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Legacy System Risks

Which of the following is the most common risk associated with maintaining legacy systems?

A Easier integration with modern cloud services

B Improved system performance from older, stable code

C Lower maintenance costs because the system is well understood

D Increased security vulnerabilities due to outdated software components

💡 Hint

Think about how old software might not receive updates or patches.

Legacy systems often use outdated software components that no longer receive security updates, making them vulnerable to attacks.

🚀 Application

intermediate

Choosing Modernization Strategies

A company wants to update its legacy system without disrupting current operations. Which modernization approach best fits this goal?

A Encapsulation by wrapping legacy components with APIs

B Complete system rewrite from scratch

C Immediate replacement with a new off-the-shelf product

D Ignoring the legacy system and building a parallel system

💡 Hint

Consider approaches that allow old and new systems to work together.

Encapsulation wraps legacy components with APIs, enabling gradual modernization without disrupting existing operations.

🔍 Analysis

advanced

Analyzing Modernization Impact

What is a likely consequence of refactoring legacy code to improve modularity?

A Reduced need for testing after changes

B Decreased system flexibility and harder future updates

C Increased risk of introducing new bugs due to code changes

D Immediate elimination of all legacy system dependencies

💡 Hint

Think about what happens when you change old code.

Refactoring legacy code can introduce new bugs because the code is changed, even though it improves modularity and maintainability.

❓ Comparison

advanced

Comparing Modernization Techniques

Which statement correctly compares 'rehosting' and 'refactoring' in legacy system modernization?

A Rehosting moves the system to new infrastructure with minimal changes; refactoring changes code to improve design

B Rehosting involves changing code structure; refactoring moves the system to new hardware without code changes

C Both rehosting and refactoring require complete system rewrites

D Refactoring is faster and cheaper than rehosting because it avoids infrastructure changes

💡 Hint

Focus on what each technique changes: code or infrastructure.

Rehosting moves legacy systems to new infrastructure with minimal code changes, while refactoring changes the code to improve its design and maintainability.

❓ Reasoning

expert

Evaluating Modernization Outcomes

A legacy system modernization project used a 'strangler pattern' to gradually replace old components. After completion, what is the expected state of the system?

A The legacy system runs in parallel indefinitely with no new components added

B The legacy system is completely replaced by new components with no downtime during transition

C The legacy system is abandoned and all data is manually migrated to a new system at once

D The legacy system is rewritten entirely before any new components are introduced

💡 Hint

Consider how the strangler pattern replaces parts step-by-step.

The strangler pattern gradually replaces legacy components with new ones, allowing the system to be fully modernized without downtime.

Practice

1. What is the main goal of legacy system modernization?

easy

A. To update old software to work better with new technology

B. To create entirely new software from scratch

C. To remove all old data from the system

D. To reduce the number of users accessing the system

Solution

1. Step 1: Understand the purpose of legacy system modernization

   Legacy system modernization aims to improve old software so it works well with current technology.

2. Step 2: Compare options with this purpose

   Only To update old software to work better with new technology matches this goal; others describe different actions.

3. Final Answer:

   To update old software to work better with new technology -> Option A

4. Quick Check:

   Legacy modernization = update old software [OK]

Hint: Focus on improving old software, not replacing it [OK]

Common Mistakes:

• Confusing modernization with creating new software
• Thinking it means deleting old data
• Assuming it reduces user access

2. Which of the following is a common method used in legacy system modernization?

easy

A. Reducing system memory

B. Deleting all user accounts

C. Ignoring security updates

D. Rewriting code to improve compatibility

Solution

1. Step 1: Identify common modernization methods

   Rewriting code is a typical way to make old software work better with new systems.

2. Step 2: Eliminate incorrect options

   Deleting users, ignoring security, or reducing memory do not help modernization.

3. Final Answer:

   Rewriting code to improve compatibility -> Option D

4. Quick Check:

   Modernization method = rewriting code [OK]

Hint: Look for options that improve software function [OK]

Common Mistakes:

• Choosing options that harm system function
• Confusing modernization with system cleanup
• Ignoring security improvements

3. Consider this scenario: A company moves its legacy software to the cloud and updates the user interface. What is the most likely result?

medium

A. The software becomes slower and less secure

B. The software works better with modern devices and is easier to use

C. The software loses all its data

D. The software stops working completely

Solution

1. Step 1: Understand effects of cloud migration and UI update

   Moving to the cloud usually improves access and performance; updating UI improves usability.

2. Step 2: Evaluate each option against expected effects

   The software works better with modern devices and is easier to use matches expected improvements; others describe negative or unlikely outcomes.

3. Final Answer:

   The software works better with modern devices and is easier to use -> Option B

4. Quick Check:

   Cloud + UI update = better use [OK]

Hint: Cloud + UI update usually improves software [OK]

Common Mistakes:

• Assuming cloud migration causes data loss
• Thinking UI updates slow software
• Believing software will stop working

4. A legacy system modernization project failed because the updated software was incompatible with existing hardware. What is the most likely cause?

medium

A. The user interface was improved

B. The software was rewritten perfectly

C. The modernization ignored hardware compatibility requirements

D. The system was moved to the cloud successfully

Solution

1. Step 1: Analyze the failure reason

   The failure was due to incompatibility with hardware, meaning hardware needs were overlooked.

2. Step 2: Match cause with options

   Only The modernization ignored hardware compatibility requirements explains ignoring hardware compatibility; others describe unrelated or positive actions.

3. Final Answer:

   The modernization ignored hardware compatibility requirements -> Option C

4. Quick Check:

   Failure cause = ignored hardware needs [OK]

Hint: Check if hardware needs were considered [OK]

Common Mistakes:

• Blaming successful cloud move
• Confusing UI improvement with failure cause
• Assuming perfect rewriting prevents all issues

5. A company wants to modernize a legacy system that has critical data and many users. Which approach best balances safety and improvement?

hard

A. Use a phased approach: update parts step-by-step while keeping the old system running

B. Move the system to the cloud without testing

C. Rewrite the entire system at once and switch immediately

D. Delete old data to speed up modernization

Solution

1. Step 1: Consider risks of modernization with critical data and users

   Changing everything at once risks data loss and downtime; safety is important.

2. Step 2: Evaluate approaches for safety and improvement

   Phased updates allow testing and reduce risk, keeping old system as backup.

3. Final Answer:

   Use a phased approach: update parts step-by-step while keeping the old system running -> Option A

4. Quick Check:

   Phased modernization = safe and effective [OK]

Hint: Update step-by-step to avoid risks [OK]

Common Mistakes:

• Switching all at once causing downtime
• Skipping testing before cloud move
• Deleting data unnecessarily