Ooh, good catch! D is a solid option too. The need for different security permissions across plan types is a great example of a requirement driving multiple plan types.
Yeah, I'm with you on that. E feels like more of a 'nice to have' rather than a core requirement. I'd go with C as one of the answers, but I'm still trying to figure out the second one.
Hmm, C makes sense because you'd want to plan sales and salary expenses separately. But E? I'm not sure about that one. Implementing a Capital Expense module seems more like an additional feature than a requirement for multiple plan types.
I agree, this is definitely testing our knowledge of planning application design. From the options provided, I think C and E are the two correct answers.
I think this question is trying to test our understanding of the requirements that would drive the need for multiple plan types in a single planning application. The key seems to be identifying those requirements that would necessitate separate planning processes or data structures.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Helaine
8 days agoAyesha
10 days agoMartha
11 days agoIsabella
12 days agoPatrick
14 days agoMalcolm
16 days ago