Which activity does not belong to business information management?

Question

Options

• Acreating an application architecture
• Bspecifying requirements regarding the production environment architecture
• Ctranslating business policy into an information architecture

• A
  76% (28)
• B
  8% (3)
• C
  16% (6)

Explanation

Creating an application architecture (A) falls outside business information management because it is a technical/IT architecture concern - it deals with how software systems are structured and built, which belongs to the domain of IT or solution architecture, not information management.

Options B and C are distractors because both directly involve information management activities: specifying requirements for the production environment architecture (B) translates business needs into infrastructure constraints, and translating business policy into an information architecture (C) is a core information management task that bridges strategy and data/information design.

Memory tip: Think of business information management as the bridge between business goals and information/data structures - if an activity is about defining or governing how information supports the business, it fits. Application architecture is on the far "build it" side of that bridge, which is the developer/architect's job, not the information manager's.

No community discussion yet for this question.