Q: 3
Which business requirements and process(es) should be documented as part of the application development plan? Choose 4 answers
Options
Discussion
I picked F and G along with D and E since users/stakeholders and data input/output always seemed like core business requirements to me. A (licenses) and B (schedule) feel more like project management details than requirements, unless ServiceNow wants you to treat them as part of planning docs. Not totally convinced so open to pushback if I'm misreading the intent here.
Pretty sure it's A, B, D, E. Licenses is easy to overlook but it's in SNOW planning docs. B and D make sense for business context. F and G feel right too at first, but those are more stakeholders/data specifics, not always in initial requirements. G trips people up every time. Disagree?
Option D here, not F. Tricky since F (users/stakeholders) looks tempting but the question asks for those needed in the actual application development plan, where things like licenses and project schedule matter more.
D , that's what official guide and practice exams point to here.
A B, D, E is what I saw in a similar question on my practice set. Available licenses and project schedule usually get included for planning documentation, not just business requirements. Pretty sure that's what ServiceNow expects here but not 100%.
D E, F, G maybe? Business problem and process steps for sure, but users/stakeholders and data input/output sound like standard business requirements too. Not totally sure if licenses and schedule count for this doc phase. Seen similar split on practice tests.
A,B,D,E tbh. That's the combo in SNOW learning paths for app planning, pretty sure.
A,B,D,E. Had something like this in a mock, those four matched the official ServiceNow docs best.
B , but I think the trap is skipping A. Available licenses does pop up in official blueprints for early planning, not just PM stuff. F and G sound right too but they're not usually "business requirements" in ServiceNow docs. Open to other views if anyone's got direct reference.
Feels like D, E, F, G. I always figured stakeholders and data flows would be part of core requirements. Licenses and schedule sound like project mgmt stuff to me.
Be respectful. No spam.