AZ400-Q: deploy a binary safely
A legacy application is released as a signed binary and deployment script, not a container. What should the pipeline verify before a protected deployment?
- A) That the binary filename is short.
- B) Artifact identity/signature or integrity evidence, version/provenance, deployment script inputs, and the target environment’s approval/check requirements. ✓
- C) That every developer has local admin.
- D) That the old binary is deleted first.
Answer: B. Binary delivery still needs provenance, integrity, controlled automation, and environment governance.
Why not the others: Filename/local admin/deletion do not establish a safe release boundary.