A burst lock-sensor container in Azure Container Instances crashed and nobody has stdout or security-relevant events. What should the security engineer configure?
Select an answer to reveal the explanation.
Short Explanation
The lock-sensor ACI vanished and left no trail. Point ACI diagnostics at Log Analytics so stdout and events have a home before the next burst run.
Full Explanation
Azure Container Instances can send logs and events to a Log Analytics workspace through diagnostic or monitoring configuration so security and operations can investigate crashes. That is the ACI security-monitoring control. Rewriting the container image alone (AZ-204), assuming ACI cannot log to a workspace, or substituting only App Insights SDK patterns miss the official monitoring setup for ACI.