Tools / Microsoft Threat Modeling Tool (TMT) Interview questions
Why is version-controlling.tm7 files important in a microservices environment?
Microservices architectures change frequently - new dependencies get added, data stores move, services split - and an un-versioned .tm7 file drifts out of sync with reality just as quickly, silently invalidating the threats it describes without any warning from the tool itself.
Storing the model file in the same repository as the service's code or infrastructure-as-code lets you diff model changes directly against architecture changes in the same pull request history, tie a specific model revision to a specific release for audit purposes, and - most usefully - catch the common gap where a change touches the code but nobody remembered to touch the model, since that gap becomes visible the moment a reviewer notices an architecture-affecting PR with no corresponding model diff.
More Related questions...