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

B vs A, B keeps things modular and doesn’t rely on Docker specifics.

Probably B since running a dedicated action in parallel keeps things modular without extra infra.

I’m with option A because using service containers is straightforward and avoids the overhead of managing parallel jobs or external environments. It’s the cleanest way to get a fresh Postgres instance. A

A is simplest since it uses built-in service containers without extra setup.

A/B? I get why A is popular, since service containers are super easy to set up and give you a clean Postgres instance automatically. But B’s approach with actions/postgres in a parallel job might be cleaner if you want more control or need to reuse the DB setup elsewhere. Still, A feels more maintainable overall because it’s baked into the workflow without juggling extra jobs. C and D seem off since the question stresses no extra infrastructure and simplicity.

Option A seems simplest since service containers spin up a fresh Postgres automatically without extra manual cleanup or complex environment setups. That matches the “empty” DB requirement better than B.

Probably A. Service containers are built right into GitHub Actions, so no extra setup needed beyond declaring the container. It spins up a fresh Postgres instance every time, which matches the “empty” database requirement nicely. Plus, it keeps things simple since you don’t have to manage separate jobs or worry about data sharing between jobs.

B might work, but running it in a parallel job adds complexity and you’d have to ensure the DB is clean and accessible from other jobs, which isn’t straightforward without extra config. So overall, A feels like the cleanest and most maintainable option

B tbh feels like a good choice too. Running the actions/postgres in a parallel job keeps things modular and easier to debug separately from the main workflow, plus no extra setup beyond the action itself. A is great but sometimes service containers can have limitations or quirks that complicate things. C and D seem off since C says it’s impossible, which isn’t true, and D adds complexity with environments that’s not really simpler or more maintainable here. So B looks like a solid alternative to A without needing external infra.

A seems easiest since service containers are built-in and quick to set up.