Parks bots must pick up new content-safety thresholds without redeploying containers. What capability is required?
Select an answer to reveal the explanation.
Short Explanation
Dynamic refresh is the parks desk updating the rule sheet mid-shift—bots reread App Configuration without rolling a new container.
Full Explanation
Parks bots that must pick up new content-safety thresholds without redeploying containers need dynamic refresh against Azure App Configuration. Dynamic refresh (sentinel key and/or polling interval) lets the running process reload configuration when thresholds change, so content-safety blocks, severity cutoffs, or groundedness gates update mid-shift without a Container Apps revision solely for config. That capability is what turns App Configuration into a live control plane for municipal AI policy rather than a boot-time snapshot.
Requiring a full container rebuild whenever any threshold changes fails the no-redeploy requirement and couples safety policy to image release cadence—too slow for urgent parks-moderation tightening after an incident. Freezing configuration at first boot and ignoring later App Configuration updates fails by disabling the very refresh path the scenario needs; bots keep enforcing stale thresholds until restart. Shipping thresholds only inside immutable Docker tags with no runtime refresh fails for the same reason as rebuilds: every policy tweak becomes a new tag and rollout, and emergency threshold changes wait on registry and revision traffic shifting.
Exam caveat: dynamic refresh still needs the app to subscribe correctly (sentinel monitoring, cache expiration, and failure handling if App Configuration is unreachable). Distinguish refresh of non-secret thresholds from secret rotation in Key Vault—different stores and different clients. Also, refresh does not remove the need to validate that new thresholds still allow legitimate parks queries while blocking disallowed content.
Operational check: enable refresh with a sentinel key, update content-safety thresholds in App Configuration, wait for the interval or sentinel change, and verify parks bots enforce the new thresholds without a container rebuild; simulate App Configuration blips to ensure the app keeps last-known-good policy rather than crashing open.