{
  "context": "Tests whether the response explains cache invalidation strategies and recommends an appropriate one.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Explains write-through or write-behind",
      "description": "Describes write-through (update cache on write) or write-behind (async cache update) as strategies",
      "max_score": 10
    },
    {
      "name": "Explains cache-aside with invalidation",
      "description": "Describes cache-aside (lazy loading) with explicit invalidation on write (delete cache key on update)",
      "max_score": 10
    },
    {
      "name": "Recommends invalidation on write for this case",
      "description": "Recommends actively invalidating (deleting or updating) the cache entry when the user updates their profile, not just waiting for TTL",
      "max_score": 12
    },
    {
      "name": "Addresses consistency vs performance tradeoff",
      "description": "Discusses the tradeoff between cache freshness and read performance, or mentions eventual consistency",
      "max_score": 10
    },
    {
      "name": "No incorrect information",
      "description": "Caching patterns and Redis behavior are described correctly",
      "max_score": 12
    }
  ]
}