Null Object pattern in LLD - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Null Object class that implements the same interface.

LLD

class NullLogger:
    def log(self, message):
        [1]

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

Apass

Bprint(message)

Creturn message

Draise Exception('Not implemented')

Attempts:

3 left

💡 Hint

Common Mistakes

Using print or return instead of pass.

The Null Object's method should do nothing, so pass is correct.

2fill in blank

medium

Complete the code to use the Null Object pattern to avoid null checks.

LLD

def process(logger):
    logger.[1]('Start processing')

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

Alog

Bwrite

Cprint

Dsend

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names not defined in the interface.

The method to call on the logger is log as defined in the interface.

3fill in blank

hard

Fix the error in the Null Object implementation to correctly override the interface method.

LLD

class NullNotifier:
    def notify(self):
        [1]

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

Araise NotImplementedError()

Bprint('Notification sent')

Creturn True

Dpass

Attempts:

3 left

💡 Hint

Common Mistakes

Raising exceptions or printing output in Null Object methods.

The Null Object should override the method and do nothing, so pass is correct.

4fill in blank

hard

Fill both blanks to complete the factory method that returns a Null Object when input is None.

LLD

def get_logger(logger):
    if logger is None:
        return [1]()
    else:
        return [2]

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

ANullLogger

Blogger

CLogger

DNone

Attempts:

3 left

💡 Hint

Common Mistakes

Returning None instead of Null Object instance.

If logger is None, return an instance of NullLogger, else return the given logger.

5fill in blank

hard

Fill all three blanks to implement a Null Object pattern with a dictionary comprehension filtering active users.

LLD

active_users = {user: [1] for user, status in users.items() if status [2] 'active' and user != [3]

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

ANullNotifier()

B==

CNone

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong operators or values in comprehension.

Assign NullNotifier() as the value, filter users where status is 'active', and exclude users equal to None.

Practice

1. What is the main purpose of the Null Object pattern in system design?

easy

A. To encrypt sensitive data before storage

B. To create multiple instances of an object for load balancing

C. To optimize database queries by caching null values

D. To replace null references with an object that does nothing but follows the expected interface

Solution

1. Step 1: Understand the problem with null references

   Null references can cause errors like null pointer exceptions when methods are called on them.

2. Step 2: Explain how Null Object pattern solves this

   The pattern replaces null with a harmless object that implements the same interface but performs no action, avoiding errors.

3. Final Answer:

   To replace null references with an object that does nothing but follows the expected interface -> Option D

4. Quick Check:

   Null Object pattern = harmless object instead of null [OK]

Hint: Null Object means safe empty object, not null itself [OK]

Common Mistakes:

• Confusing Null Object with caching or encryption
• Thinking it creates multiple instances for load balancing
• Assuming it optimizes database queries

2. Which of the following is the correct way to implement a Null Object in a class hierarchy?

easy

A. Create a subclass that overrides methods with empty implementations

B. Use a global variable set to null

C. Throw exceptions in the Null Object methods

D. Return null from all methods in the Null Object

Solution

1. Step 1: Identify how Null Object should behave

   It should implement the same interface but provide harmless (empty) behavior.

2. Step 2: Choose the correct implementation approach

   Creating a subclass that overrides methods with empty implementations fits the pattern.

3. Final Answer:

   Create a subclass that overrides methods with empty implementations -> Option A

4. Quick Check:

   Null Object subclass overrides methods safely [OK]

Hint: Null Object overrides methods with empty bodies [OK]

Common Mistakes:

• Using null variables instead of objects
• Throwing exceptions defeats Null Object purpose
• Returning null causes errors again

3. Consider this code snippet using Null Object pattern:

class Logger {
  log(message) { console.log(message); }
}

class NullLogger {
  log(message) { /* do nothing */ }
}

function process(data, logger) {
  logger.log('Start');
  // process data
  logger.log('End');
}

const logger = new NullLogger();
process('input', logger);

What will be the output when this code runs?

medium

A. Logs 'Start' and 'End' messages to console

B. No output will be printed

C. Throws an error because NullLogger does not log

D. Logs only 'Start' message

Solution

1. Step 1: Analyze NullLogger behavior

   NullLogger's log method does nothing, so no console output occurs.

2. Step 2: Trace process function calls

   process calls logger.log twice, but since logger is NullLogger, no output is printed.

3. Final Answer:

   No output will be printed -> Option B

4. Quick Check:

   NullLogger logs nothing = no output [OK]

Hint: Null Object methods do nothing, so no output [OK]

Common Mistakes:

• Assuming NullLogger logs messages
• Expecting errors from NullLogger
• Thinking partial logs appear

4. You have a Null Object implementation but still get null pointer exceptions in your system. What is the most likely cause?

medium

A. Some parts of the code still use null instead of the Null Object

B. The Null Object throws exceptions intentionally

C. The Null Object does not implement the required interface

D. The Null Object caches null values incorrectly

Solution

1. Step 1: Understand Null Object pattern goal

   It replaces null references to avoid null pointer exceptions.

2. Step 2: Identify why exceptions still occur

   If some code still uses null directly, exceptions will happen despite Null Object presence.

3. Final Answer:

   Some parts of the code still use null instead of the Null Object -> Option A

4. Quick Check:

   Null Object must replace all nulls to avoid exceptions [OK]

Hint: All nulls must be replaced by Null Object [OK]

Common Mistakes:

• Assuming Null Object throws exceptions
• Ignoring interface implementation correctness
• Confusing caching with Null Object usage

5. In a large-scale system, how does using the Null Object pattern improve system design and scalability?

hard

A. It requires complex synchronization, making the system slower

B. It increases memory usage by creating many null objects, reducing performance

C. It reduces conditional checks and prevents null-related errors, simplifying code and improving reliability

D. It replaces all objects with nulls to save resources

Solution

1. Step 1: Identify benefits of Null Object in large systems

   By replacing nulls, it removes many if-null checks and prevents errors, making code cleaner.

2. Step 2: Understand impact on scalability and reliability

   Simpler code with fewer errors means easier maintenance and better system stability at scale.

3. Final Answer:

   It reduces conditional checks and prevents null-related errors, simplifying code and improving reliability -> Option C

4. Quick Check:

   Null Object simplifies code and boosts reliability [OK]

Hint: Null Object reduces checks, improves reliability [OK]

Common Mistakes:

• Thinking Null Object wastes memory excessively
• Assuming it slows system due to synchronization
• Believing it replaces all objects with nulls