A county uses infrastructure pipelines so security logging sinks deploy with every new app. What DevOps alignment is that?

A county that uses infrastructure pipelines so security logging sinks deploy with every new app is aligning DevOps with shift-left security automation. When a bureau ships a new service, the same pipeline provisions the logging destination, retention settings, and shipper config instead of hoping telemetry appears later. That pattern makes audit-ready logs a default property of municipal releases and shrinks the window where new apps run without SOC visibility.

Why the other options fail by concept: Shift-right security automation so logging sinks deploy with municipal app pipelines keeps automation downstream in runtime instead of built in, so new apps can still launch without the required logging sinks. Shift-left security monitoring so logging sinks deploy with municipal app pipelines moves monitoring earlier but only watches for issues and does not automate logging-sink provisioning, so sinks still won't ship consistently with each new app. Shift-left security auditing so logging sinks deploy with municipal app pipelines checks compliance earlier in isolation but does not automate provisioning, so it does nothing to embed logging sinks into the application release pipeline.

Exam caveat: Shipping sinks with apps does not by itself ensure correct parsing, alerting, or retention compliance; content and detection work must still consume the new logs. Operational check: add logging-sink modules to the app pipeline checklist, fail builds that omit required sinks, and verify events land in the county SIEM before marking the release complete.