Test environments and data in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the environment used for testing microservices.

Microservices

environment = "[1]"

Drag options to blanks, or click blank then click option'

Atesting

Bproduction

Cdevelopment

Dstaging

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'production' instead of 'testing' environment.

Confusing 'development' with 'testing' environment.

The testing environment is specifically used to run tests on microservices before deployment.

2fill in blank

medium

Complete the code to select the appropriate data type for test data isolation in microservices.

Microservices

test_data_type = "[1]"

Drag options to blanks, or click blank then click option'

Aarchived

Bshared

Clive

Disolated

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'shared' test data causing test interference.

Using 'live' data risking production data corruption.

Isolated test data ensures tests do not affect each other or production data.

3fill in blank

hard

Fix the error in the test environment setup code to correctly configure the database URL.

Microservices

db_url = "jdbc:mysql://[1]:3306/testdb"

Drag options to blanks, or click blank then click option'

Aprod-db-server

Blocalhost

Ctest-db-server

Ddev-db-server

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'prod-db-server' in test environment causing data risks.

Using 'localhost' when tests require a dedicated test database.

The test environment should connect to the test-db-server to avoid affecting production data.

4fill in blank

hard

Fill both blanks to create a test data setup that resets and seeds the database before tests.

Microservices

def setup_test_data():
    [1]()
    [2]()

Drag options to blanks, or click blank then click option'

Areset_database

Bseed_database

Cbackup_database

Dconnect_database

Attempts:

3 left

💡 Hint

Common Mistakes

Calling backup or connect functions instead of reset and seed.

Reversing the order of reset and seed functions.

First, reset_database() clears old data, then seed_database() adds fresh test data.

5fill in blank

hard

Fill all three blanks to configure environment variables for test microservice deployment.

Microservices

config = {
    "ENV": "[1]",
    "DB_HOST": "[2]",
    "LOG_LEVEL": "[3]"
}

Drag options to blanks, or click blank then click option'

Atesting

Btest-db-server

CDEBUG

Dproduction

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'production' environment in test config.

Setting log level to INFO or ERROR instead of DEBUG.

The environment is set to testing, database host to test-db-server, and log level to DEBUG for detailed test logs.

Practice

1. Why is it important to use separate test environments in microservices development?

easy

A. To speed up the production deployment process

B. To keep testing isolated and avoid affecting real users

C. To reduce the number of microservices needed

D. To allow direct access to live customer data

Solution

1. Step 1: Understand the purpose of test environments

   Test environments are designed to isolate testing activities from the live system to prevent disruptions.

2. Step 2: Identify the impact on real users

   Using separate environments ensures that bugs or errors during testing do not affect real users or live data.

3. Final Answer:

   To keep testing isolated and avoid affecting real users -> Option B

4. Quick Check:

   Test isolation = Avoid affecting real users [OK]

Hint: Test environments protect live users by isolating tests [OK]

Common Mistakes:

• Thinking test environments speed up production
• Believing test environments reduce microservice count
• Assuming test environments use live customer data

2. Which of the following is the correct way to represent a test environment URL in a microservices config file?

easy

A. "https://live.api.example.com"

B. "https://api.production.example.com"

C. "http://test.api.example.com"

D. "ftp://test.api.example.com"

Solution

1. Step 1: Identify the correct protocol and domain for test environment

   Test environments usually use HTTP or HTTPS with a subdomain indicating test or staging, like test.api.example.com.

2. Step 2: Check for correct URL format

   "http://test.api.example.com" uses HTTP and a test subdomain, which is typical for test environments. "https://api.production.example.com" and C point to production/live URLs, and D uses FTP which is uncommon for APIs.

3. Final Answer:

   "http://test.api.example.com" -> Option C

4. Quick Check:

   Test URL = HTTP + test subdomain [OK]

Hint: Test URLs often use 'test' subdomain and HTTP/HTTPS [OK]

Common Mistakes:

• Using production URLs for test environments
• Using unsupported protocols like FTP for APIs
• Omitting quotes or using invalid URL formats

3. Given the following test data setup for a microservice, what will be the output of the test log?

test_data = [{"id": 1, "name": "Alice"}, {"id": 2, "name": "Bob"}]
for user in test_data:
    if user["id"] == 2:
        print(f"User found: {user['name']}")
    else:
        print("User not found")

medium

A. User not found
User found: Bob

B. User found: Alice
User found: Bob

C. User found: Bob
User not found

D. User not found
User not found

Solution

1. Step 1: Analyze the loop over test_data

   The loop checks each user dictionary. For user with id 1, it prints "User not found" because id != 2. For user with id 2, it prints "User found: Bob".

2. Step 2: Determine the printed output order

   First iteration prints "User not found", second prints "User found: Bob".

3. Final Answer:

   User not found User found: Bob -> Option A

4. Quick Check:

   Check id == 2 prints name, else prints not found [OK]

Hint: Check condition inside loop carefully for each item [OK]

Common Mistakes:

• Assuming both users print 'User found'
• Mixing order of output lines
• Confusing user id and name in condition

4. A developer wrote this test environment configuration snippet:

env = {
  "DATABASE_URL": "prod-db.example.com",
  "API_KEY": "test-key-123"
}

# Test connection
if env["DATABASE_URL"].startswith("test"):
  print("Connected to test database")
else:
  print("Connected to production database")

What is the bug in this code?

medium

A. DATABASE_URL points to production but check expects 'test' prefix

B. API_KEY should not be in test environment config

C. The print statements are reversed

D. The env dictionary keys are missing quotes

Solution

1. Step 1: Review DATABASE_URL value and condition

   DATABASE_URL is set to "prod-db.example.com" but the code checks if it starts with "test" to identify test DB.

2. Step 2: Identify mismatch causing wrong output

   Since DATABASE_URL does not start with "test", the else branch runs, printing "Connected to production database" even if this is meant to be a test config.

3. Final Answer:

   DATABASE_URL points to production but check expects 'test' prefix -> Option A

4. Quick Check:

   Config value mismatch causes wrong environment detection [OK]

Hint: Match config values with condition checks exactly [OK]

Common Mistakes:

• Ignoring the DATABASE_URL value mismatch
• Thinking API_KEY causes the bug
• Assuming print statements are swapped
• Overlooking correct dictionary syntax

5. You need to design a test environment for a microservices system that uses sensitive user data. Which approach best balances realistic testing and data safety?

hard

A. Use production data directly in the test environment with restricted access

B. Use outdated production backups as test data without masking

C. Skip test data and test only with empty datasets

D. Generate synthetic test data that mimics production data patterns without real user info

Solution

1. Step 1: Consider data safety requirements

   Using real production data risks exposing sensitive info. Outdated backups or empty data reduce realism.

2. Step 2: Evaluate test data realism and safety

   Synthetic data that mimics real patterns but contains no real user info provides safe and realistic testing.

3. Final Answer:

   Generate synthetic test data that mimics production data patterns without real user info -> Option D

4. Quick Check:

   Safe + realistic test data = synthetic data [OK]

Hint: Use synthetic data to protect privacy and keep tests real [OK]

Common Mistakes:

• Using real production data risking privacy
• Using old backups without masking sensitive info
• Testing only with empty datasets misses real bugs