Free Microsoft GH-200 Actual Exam Questions - Question 13 Discussion

I’m thinking B might actually be the better option here. Keeping custom actions in a separate branch within the main app repo still separates concerns but avoids the overhead of managing multiple repositories. It helps with version control and coordination since it’s linked directly to the app’s lifecycle, without fragmenting teams too much. Managing separate repos (A) could get complicated if actions rely on shared code or need to sync frequently. So B offers a middle ground between isolation and integration.

D imo, mixing custom actions directly with app code can cause messy dependencies and harder tracking. Keeping them separate helps maintain clearer boundaries and easier updates.

D imo, mixing custom actions with app code can complicate deployments and versioning.

Option A, separate repos make version control way cleaner and safer.

A vs C? I think A makes more sense because if you put all actions in one repo like in C, you have to release everything together even if only one action changes. That can slow down updates and cause unnecessary dependencies. Separate repos let you manage each action’s lifecycle independently, which feels cleaner for enterprise settings with lots of teams and frequent changes. Keeping them all in one repo seems like it could lead to version conflicts or bigger release cycles.

A imo. Keeping each action in its own repo makes it easier to update and roll back independently without messing up the others. It avoids the complexity of syncing versions across unrelated actions, which can get messy fast in big teams. Plus, you don’t risk breaking unrelated parts when you change one action.

Probably A, keeping actions separate helps manage versions better.