When preparing a microservice for deployment that requires multiple sensitive configurations, which approach would ensure the secure and environment-agnostic management of these settings?
Embed the configurations into the application code within the container image
Declare sensitive environment variables within the build specification file of the container
Dynamically inject the configurations using a secrets management service at container startup
Fetch the configurations from the host's instance metadata service upon container initialization