"Work can be isolated in development branches by feature, organization, or temporary collaboration."
Development isolation not necessarily isolated by features.
D is the answer.
https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/branching-strategies-with-tfvc?view=azure-devops#feature-isolation
Feature isolation is a special derivation of the development isolation, allowing you to branch one or more feature branches from main, as shown, or from your dev branches.
When you need to work on a particular feature, it might be a good idea to create a feature branch.
Keep the lifetime of feature work and the associated feature branch short-lived. Forward integrate (FI) changes from the parent branch frequently. Reverse integrate (RI) back to the parent only when some agreed team criteria, for example definition of done, is met. Rollback of features on main can be costly and may reset testing.
Answer: D. feature isolation.
Explanation:
To support developing new functionality in isolation, a branching strategy that isolates new feature development in branches should be used. This allows changes to be made to a feature without affecting other development efforts. Once a feature is completed, the changes can be merged back into the main branch.
The best branching strategy for the investment planning applications suite would be "feature isolation." This strategy would allow for the development of new functionality in isolation, as required by the technical requirements. With feature isolation, developers can work on different features concurrently and merge them into the main branch when they are ready. This approach allows for better collaboration and faster development, while minimizing the risk of conflicts and bugs when merging code. Additionally, it allows the team to use the principle of least privilege, as well as giving the Team Leaders the ability to create new packages and edit the permissions of package feeds.
https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/branching-strategies-with-tfvc?view=azure-devops#feature-isolation
"Feature isolation is a special derivation of the development isolation, allowing you to branch one or more feature branches from main, as shown, or from your dev branches."
Answer is D
I think that the question is not complete. It is a part of Litware questions with the described scenario ("A branching strategy that supports developing new functionality in isolation must be used").
Development isolation strategy have individual branches for development and Support changes. whereas feature isolation - branch will be used only for the functionality
upvoted 6 times
...
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
031920
Highly Voted 2 years, 11 months agorrongcheng
Highly Voted 3 years agozellck
Most Recent 4 weeks, 1 day agoMadbo
2 months, 1 week agomrg998
5 months, 1 week agobudha
7 months agosyu31svc
11 months agoEltooth
1 year, 1 month agordemontis
1 year, 3 months agoSara_Mo
1 year, 5 months agoScreamingHand
1 year, 8 months agovglearn
2 years, 4 months agosomedude
3 years, 1 month agowarchoon
5 months, 4 weeks agoJakeCallham
3 years agolalithasms
3 years ago