問題文
A group already connected its version control system and assumes that covers its external automation server too, because the pipelines are defined in the same repositories. Why is that assumption wrong?
選択肢
- The assumption is correct; no separate onboarding exists, because the automation server is discovered through the pipeline definitions that reference it inside the repositories.
- The assumption is correct for pipeline definitions but wrong for build artifacts, since artifacts are produced outside the repository and therefore require the container registry integration rather than the automation server integration.
- Definitions stored in the repository are visible, but the server's own instance and job configuration are not, and those are where a different class of risk lives.
- The version control integration covers the server only if the server runs inside the same cloud account, which is the case for most self-hosted automation servers in practice.