HOTSPOT Your company uses Git as a source code control system for a complex app named App1. You plan to add a new functionality to App1. You need to design a branching model for the new functionality. Which branch lifetime and branch time should you use in the branching model? To answer, select the appropriate options in the answer area. NOTE:Each correct selection is worth one point. 
Is anyone using long-lived branches for this kind of work anymore, or is it always short-lived feature branches now? Just trying to see if there's a situation where that's not the best approach.
Short-lived feature branch here. Main reason is you only need the branch until the new functionality is done, then merge back to main. Long-lived branches are mostly for major ongoing streams or releases, which isn't the case. Sometimes people pick release branch by mistake but that's not for features. Pretty sure this matches what you'd see in real projects.
Wouldn't this be a solid case for making a short-lived feature branch? Seems like the normal pattern for adding new functionality in Git unless there's something unusual in the requirements.
Had something like this in a mock, and it was definitely about using a short-lived feature branch for new functionality. This setup lines up with agile workflows, makes merging less painful, and keeps the main branch stable. So for lifetime it's short-lived, for type it's feature. Pretty sure that's what they're after here. Agree?
