County IT wants Git branch names that support audit reviews of who changed which automation ticket. Which naming convention best supports that goal?
Select an answer to reveal the explanation.
Short Explanation
Put the ticket ID in the branch name like stamping a work order number on a manhole cover — auditors can trace the dig back to the approved request without spelunking through random nicknames.
Full Explanation
County IT audit reviews need to map source-control activity to approved change tickets. Embedding the change-ticket identifier in the branch name—for example feature/ITSM-4821-meter-sync—makes that linkage visible in MR lists, git branch output, and compliance exports without spelunking through commit messages alone. Reviewers can confirm the branch corresponds to an authorized ITSM item before merge.
Celebrity nicknames are memorable in standups but opaque to auditors and automation that keys off ticket IDs. Naming every branch temp collapses traceability and invites collisions. Encoding the branch solely as a random UUID with no ticket reference provides uniqueness without business-context linkage, which fails the audit goal stated in the stem.
Exam caveat: ticket IDs in branch names complement, not replace, ticket IDs in commit messages and MR titles. Operational check: create a branch including the ITSM key, open the MR, and verify auditors can search the repo or project for that ticket ID and find the associated commits and review record. Ticket-bearing names also help automation: chatops and MR templates can parse ITSM-4821-style tokens to link pipelines to the service desk. Random or vanity names force manual correlation that fails under audit pressure when dozens of automation branches are open.