Q: 7
You need to configure the RailStatusUpdater cloud flow. What should you do?
Options
Discussion
Option B makes the most sense, since using an environment variable lets you change the config in one place instead of editing every step. Official docs and practice questions push this pattern for maintainability. Pretty sure B is best here, but open to correction.
Option B makes sense, environment variables mean you only update in one spot instead of every action. Saw this approach recommended on practice tests. Pretty sure that's what Microsoft wants for maintainability, but open if anyone disagrees.
Honestly, Microsoft loves throwing in manual update distractors like C but it's B every time for real exams.
A is wrong, C. Saw something like this in another practice and picking C makes sense if you want a quick fix and don't need reusability. Not the best for long-term but works for small changes. Thoughts?
B tbh
B or C? B seems right for maintainability but not totally sure if it's asking about just single setup.
These vendor scenarios always load up distractors like C just to trip people, but it's B for config every time.
Had something like this in a mock. B is the way to go since using environment variables makes updating config easy and scalable instead of editing every single action.
B , since environment variables let you change config in one spot. C is more of a trap answer here.
C/D?
Be respectful. No spam.