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
  79% (30)
• B
  13% (5)
• C
  8% (3)

Explanation

Creating an application architecture (A) falls outside business information management because it is a technical IT architecture activity - it concerns the design and structure of software applications, which belongs to the application architecture domain, not information management.

Options B and C are distractors because both are genuine information management activities: specifying requirements for the production environment ensures information systems are properly supported at the infrastructure level (still driven by information/business needs), and translating business policy into an information architecture is arguably the core purpose of business information management - bridging business intent and information design.

Memory tip: Think of business information management as the layer between business strategy and data/information. The moment an activity becomes about how software is built or structured (application architecture), you've crossed into a different domain. A good rule: if it's about what information the business needs and how it's organized, it's information management; if it's about how software is constructed, it's not.

No community discussion yet for this question.