Which of the following statements regarding the application of the State Repository pattern is false?

Question

Options

• AState data can be temporarily written to and then later retrieved from a dedicated state repository.
• BCaching large amounts of state data in memory negatively impacts scalability.
• CA state repository is not useful for supporting long-running service activities.
• DDatabase technology is typically used for the implementation of a state repository.

• A
  16% (8)
• B
  4% (2)
• C
  74% (37)
• D
  6% (3)

Explanation

Option C is false because the State Repository pattern is specifically designed to support long-running service activities - it's one of the pattern's primary use cases. When a service runs over an extended period, it can persist intermediate state to the repository, allowing it to resume correctly after delays, failures, or handoffs between service instances.

Why the distractors are true (and therefore wrong answers):

• A is true: temporarily writing and later retrieving state is exactly the core mechanic of the pattern.
• B is true: holding large state volumes in memory reduces service scalability, which is precisely why offloading state to an external repository is beneficial.
• D is true: relational and NoSQL databases are the standard implementation vehicle for state repositories.

Memory tip: Think of the State Repository as a "save game" feature for services. Long-running processes especially need a place to save progress - so anything claiming a state repository is not useful for long-running activities is the opposite of true.

No community discussion yet for this question.