INFORMATION-TECHNOLOGY-MANAGEMENT Practice Questions

Operational CRM focuses on the automation of customer-facing processes such as sales, marketing, and customer service. Contact management is a foundational technology within this domain. It is designed to capture, store, and manage comprehensive data about customers and prospects, including contact details, interaction history, and activities. This centralized repository is crucial for sales teams to track leads, manage relationships, and identify potential customers for future sales efforts, directly addressing both functions mentioned in the question.

A. Cross-selling: This is a sales strategy that uses customer data to sell additional products, not the technology that maintains the data itself.

B. Campaign management: This technology focuses on designing and executing marketing campaigns for customer segments, rather than the fundamental management of individual contact and prospect data.

C. Call scripting: This is a specific tool providing pre-written dialogues for agents during calls; it does not manage customer data or identify prospects.

1. Laudon

K. C.

& Laudon

J. P. (2020). Management Information Systems: Managing the Digital Firm (16th ed.). Pearson. In Chapter 9

"Achieving Operational Excellence and Customer Intimacy: Enterprise Applications

" the section on Sales Force Automation (SFA) describes contact management systems as a key capability for tracking all contact and prospect data (pp. 356-357).

2. Buttle

F.

& Maklan

S. (2019). Customer Relationship Management: Concepts and Technologies (4th ed.). Routledge. Chapter 2

"Strategic CRM

" explains that operational CRM includes sales force automation

which has contact management as a core function for maintaining a record of customers

prospects

and their interaction history.

3. Payne

A.

& Frow

P. (2005). A Strategic Framework for Customer Relationship Management. Journal of Marketing

69(4)

167–176. The framework presented distinguishes operational CRM as the automation of customer-facing processes. Contact management is an implicit

fundamental element of the "customer interaction management process" within the operational sphere (p. 172). https://doi.org/10.1509/jmkg.2005.69.4.167

Workflow automation is a core feature of modern CRM systems designed to streamline and automate business processes. In the context of customer support, this feature uses rule-based logic to manage the lifecycle of a customer issue. This includes automatically routing incoming support tickets to the appropriate agent or department based on criteria like issue type or customer priority, and escalating tickets to a higher support tier if they are not resolved within a specified timeframe. This digitization of processes ensures efficiency, consistency, and timely resolution of customer inquiries.

B. Response queue analytics: This feature involves the analysis and reporting of data from support queues (e.g., wait times, resolution rates), rather than the execution of the routing and escalation processes themselves.

C. Channel preference management: This is concerned with tracking and using a customer's preferred method of communication (e.g., email, phone, chat), not with the internal handling of a support ticket.

D. Interaction history management: This feature provides a consolidated view of all past communications and transactions with a customer to give context to agents, but it does not automate the workflow of a current ticket.

---

1. Payne

A.

& Frow

P. (2005). A strategic framework for customer relationship management. Journal of Marketing

69(4)

167-176. In Section "The CRM Process Element

" the authors discuss how technology enables the automation of customer-facing processes

such as customer service and support

which inherently includes the logic for routing and managing inquiries. (p. 171). https://doi.org/10.1509/jmkg.2005.69.4.167

2. Buta

S. (2016). The role of CRM in business. Annals of the „Constantin Brâncuși” University of Târgu Jiu

Economy Series

1(1)

130-133. The paper describes Operational CRM and its component

Service Automation

stating it "helps in managing customer service requests

complaints

and product returns... It can be used to assign the service requests to the most appropriate service agent or employee." This describes automated ticket routing. (p. 132

Section 3.1.3).

3. Chalmeta

R. (2006). Methodology for customer relationship management. Journal of Systems and Software

79(7)

1015-1024. The author discusses the technological components of CRM

highlighting that operational CRM automates processes. Within the service module

functionalities for "incident management" include rules for assignment and escalation

which are forms of workflow automation. (p. 1019

Section 3.2). https://doi.org/10.1016/j.jss.2005.10.018

Reducing the movement of workers, raw materials, and equipment is a fundamental principle of lean operations, specifically targeting the elimination of "waste of motion" and "waste of transportation." Minimizing these non-value-added activities leads to a more streamlined workflow, which directly enhances operational efficiency by reducing process time and resource consumption. Concurrently, a simplified and more organized physical layout with less movement reduces the opportunities for accidents, collisions, and ergonomic strain, thereby improving workplace safety.

B. It reduces the need to train employees in multiple roles.

This is incorrect. Process optimization through reduced movement is independent of employee skill sets. Lean methodologies often advocate for cross-training to increase workforce flexibility.

C. It allows for more variation in workflow paths.

This is the opposite of the intended outcome. The goal is to standardize and optimize workflow paths to eliminate variation, which is a source of inefficiency and defects.

D. It enables greater flexibility in resource allocation.

This is incorrect. By standardizing movement and creating highly optimized, specific workflows, this practice can reduce the immediate flexibility of how resources are allocated within that process.

1. Hopp

W. J.

& Spearman

M. L. (2004). To Pull or Not to Pull: What Is the Question? Manufacturing & Service Operations Management

6(2)

133–148. In Section 3.1

"The River of Inventory Analogy

" the authors discuss how lean principles

including the reduction of waste like unnecessary transportation

improve process flow and efficiency. The reduction of chaotic movement is implicitly linked to a more controlled and safer environment. https://doi.org/10.1287/msom.1030.0028

2. Shah

R.

& Ward

P. T. (2007). Defining and developing measures of lean production. Journal of Operations Management

25(4)

785-805. On page 791

the authors discuss the components of a lean production system

which includes eliminating waste (Muda). The waste of "unnecessary transportation" and "unnecessary motion" are key targets. Eliminating them directly shortens lead times (improving efficiency) and simplifies processes (improving safety). https://doi.org/10.1016/j.jom.2007.01.019

3. Liker

J. K. (2004). The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer. As cited in numerous academic analyses of lean systems

Principle 5 focuses on building a culture to get quality right the first time

which involves standardizing tasks and processes. Standardized work minimizes motion and defines the most efficient and safest sequence of operations. This concept is foundational in university operations management curricula. (e.g.

MIT OCW

15.763J Manufacturing System and Supply Chain Design

Lecture 5: The Toyota Production System).

Offshore outsourcing, by definition, involves collaborating with teams in different countries, which almost invariably means operating across different time zones. This "temporal distance" is a primary and direct consequence that creates significant operational challenges. It complicates synchronous communication, such as scheduling real-time meetings and collaborative work sessions. Teams must develop specific strategies, like "follow-the-sun" models or asynchronous communication protocols, to mitigate the inherent delays and coordination difficulties. These time zone issues directly impact project management, team cohesion, and the speed of decision-making and problem resolution.

A. Longer feedback cycles are a common symptom of time zone differences and cultural distance, rather than the fundamental consequence itself.

B. Increased management overhead is a valid but broader consequence that encompasses managing time zones, cultural differences, and contracts, making it less specific than option D.

C. "Offshore growth challenges" is an ambiguous phrase that is not a direct, universally recognized consequence of the practice itself.

1. Carmel

E.

& Agarwal

R. (2001). Tactical Approaches for Alleviating Distance in Global Software Development. IEEE Software

18(2)

22–29. In Section "The Effects of Distance

" the authors identify "temporal distance" (time zone difference) as a key challenge

stating

"The most obvious effect of temporal distance is the difficulty in finding a common time to communicate synchronously" (p. 24). https://doi.org/10.1109/52.914734

2. Oshri

I.

Kotlarsky

J.

& Willcocks

L. P. (2015). The Handbook of Global Outsourcing and Offshoring (3rd ed.). Palgrave Macmillan. Chapter 4

"Managing Dispersed Teams

" discusses the challenges of geographical and temporal dispersion. It highlights that time zone differences necessitate structured communication patterns and can impede the informal interactions crucial for resolving complex issues (pp. 88-90).

3. Khan

S. U.

Niazi

M.

& Ahmad

R. (2011). Factors influencing clients in the selection of offshore software development outsourcing vendors. In Software Engineering and Advanced Applications (SEAA)

2011 37th EUROMICRO Conference on (pp. 293-300). IEEE. The study identifies communication and coordination as major risk factors

noting that "time zone difference is a major issue in communication" (Section IV

Part C). https://doi.org/10.1109/SEAA.2011.50

Enterprise Resource Planning (ERP) systems are designed to be the central nervous system of an organization. They integrate core business processes—such as finance, manufacturing/production, supply chain (including inventory), and human resources—into a single, unified system. By using a common database and shared data definitions, an ERP system eliminates information silos between departments. This allows for seamless data flow and improved coordination, which directly addresses the company's need to unify its inventory, production, and financial reporting functions.

A. Digital inventory logging utility: This is a point solution that only addresses inventory management and does not integrate production or financial systems.

B. Team collaboration scheduling: This software focuses on managing people, tasks, and communication, not integrating core business operational processes.

C. Departmental metrics dashboard tool: This tool visualizes data from different systems but does not integrate the underlying processes or databases themselves.

1. Davenport

T. H. (1998). Putting the enterprise into the enterprise system. Harvard Business Review

76(4)

121–131. In Section "The Promise of Enterprise Systems

" the author states

"At the heart of an enterprise system is a single comprehensive database... The system collects data from and feeds data into all of the company’s business processes... a company can achieve a high level of integration." (p. 122).

2. Monk

E.

& Wagner

B. (2013). Concepts in Enterprise Resource Planning (4th ed.). Cengage Learning. Chapter 1

"Business Functions and Business Processes

" explains that ERP software supports the efficient operation of business processes by integrating tasks related to sales

marketing

manufacturing

logistics

accounting

and staffing.

3. Massachusetts Institute of Technology OpenCourseWare. (2004). 15.561 Information Systems

Lecture 9: Enterprise Systems. Retrieved from MIT OCW. The lecture notes define ERP systems as those that "integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs." (Slide 4).

4. Oracle. (n.d.). What is ERP?. Oracle Corporation. Retrieved from https://www.oracle.com/erp/what-is-erp/. The official documentation states

"Enterprise Resource Planning (ERP) refers to a type of software that organizations use to manage day-to-day business activities such as accounting

procurement... and supply chain operations."

A storyboard is a visual, narrative-based tool used in the early stages of design. Its primary advantage in a time-constrained environment, such as a rapid design challenge, is its ability to communicate a proposed solution or user experience quickly and effectively. By using a sequence of simple sketches or images, teams can convey complex interactions and user flows without investing time in building a functional prototype. This visual storytelling approach ensures all stakeholders, regardless of their technical background, can easily understand and provide feedback on the core concept, fostering rapid iteration and alignment.

B. Storyboards are a low-fidelity technique intended to be created quickly with minimal resources, such as a whiteboard or paper, making this statement the opposite of an advantage.

C. Storyboards are a design and communication artifact that precedes the development phase; they illustrate user interaction concepts and do not involve any coding or programming.

D. Storyboards are used for exploration and ideation, not finalization. They help teams test concepts and gather feedback to inform the final design, which requires much higher fidelity.

1. Stanford University

Hasso Plattner Institute of Design (d.school). Bootcamp Bootleg. (2018). On page 33

under "Storyboard

" the method is described as a tool to "craft a compelling story to communicate your idea" and to "show

don't tell

" highlighting its function as a rapid communication tool.

2. Massachusetts Institute of Technology (MIT) OpenCourseWare. 6.831: User Interface Design and Implementation

Lecture 3: Low-Fi Prototyping. (Fall 2011). Slide 21 lists advantages of storyboards

including being "Fast" and "Cheap

" and their purpose is to "Show how your interface accomplishes a user goal

" which underscores their role in efficient communication.

3. Rosson

M. B.

& Carroll

J. M. (2002). Usability Engineering: Scenario-Based Development of Human-Computer Interaction. Morgan Kaufmann Publishers. In Chapter 4

"Scenarios in the Design Process

" the authors discuss how storyboards and scenario-based representations serve as "a concrete communication medium among stakeholders" (p. 98)

facilitating shared understanding early in the design lifecycle.

The primary purpose of Project Communication Management is to ensure the timely and appropriate planning, collection, creation, distribution, storage, retrieval, management, and monitoring of project information. This knowledge area focuses on creating an effective communication link between project stakeholders. Its core objective is to ensure that the right people (stakeholders) receive the right information at the right time through the appropriate channels, thereby facilitating understanding, decision-making, and overall project success.

A. This is the primary purpose of Project Quality Management, which establishes policies and objectives to ensure deliverables meet specified requirements.

C. This is a function of Project Risk Management, which involves identifying, analyzing, and responding to potential threats and opportunities for the project.

D. This is a function of Project Resource Management, which uses tools like a Responsibility Assignment Matrix (RAM) to clarify roles and responsibilities.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 10: Project Communications Management

Introduction

p. 359. The guide states

"Project Communications Management includes the processes required to ensure timely and appropriate planning

collection

creation

distribution

storage

retrieval

management

control

monitoring

and the ultimate disposition of project information."

2. Larson

E. W.

& Gray

C. F. (2021). Project Management: The Managerial Process (8th ed.). McGraw-Hill Education. Chapter 10

"Communication

" discusses that the goal is to "provide the right people the right information at the right time."

3. MIT OpenCourseWare. (2006). 1.040/1.401/ESD.051 Project Management

Fall 2006. Lecture Notes

Lecture 10: Project Control. The notes define Communications Management as ensuring "timely and appropriate generation

collection

dissemination

storage

and ultimate disposition of project information

" which directly supports the core function of connecting stakeholders with relevant information. (Available at: https://ocw.mit.edu)

The Systems Development Life Cycle (SDLC) is a structured process used to develop information systems. The entire cycle is initiated in response to a recognized business need. This need can manifest as a problem to be solved (e.g., inefficient processes), an opportunity to be seized (e.g., entering a new market), or a directive to be followed (e.g., new government regulations). This fundamental business requirement is the catalyst that triggers the formal SDLC process, beginning with the planning phase where the scope and feasibility of addressing the need are evaluated.

A. Budget approval: This is a critical checkpoint, typically within the planning or analysis phase, but it occurs only after a business need has been identified and a preliminary proposal is made.

B. Stakeholder buy-in: Gaining support from stakeholders is an ongoing activity that starts in the early phases, but it is a consequence of presenting a defined business need, not the trigger itself.

C. Planning: Planning is the first formal phase of the SDLC. The need to plan is prompted by the pre-existing business need that the proposed system aims to address.

1. Valacich

J. S.

& George

J. F. (2020). Modern Systems Analysis and Design (9th ed.). Pearson. In Chapter 2

"The Origins of Software

" the text explains that projects are identified and selected to respond to a need

problem

or opportunity within the organization (pp. 34-36). This identification of a business need precedes the formal project initiation and planning.

2. Dennis

A.

Wixom

B. H.

& Roth

R. M. (2018). Systems Analysis and Design (7th ed.). Wiley. Chapter 1

"The Systems Analyst and Information Systems Development

" states that projects begin with a "system request

" which is a document describing the business reasons for building a system. This "business reason" is the identified business need (p. 6).

3. Massachusetts Institute of Technology. (2002). 15.564 Information Management: From Strategy to Implementation

Lecture Notes. MIT OpenCourseWare. Lecture 1

"Introduction

" frames IT projects as solutions to business problems or enablers of business strategy

establishing the business context as the starting point for any development effort.

Encryption is the process of converting readable data (plaintext) into an unreadable format (ciphertext) using an algorithm and a cryptographic key. Only individuals with the correct decryption key can revert the ciphertext back to its original, readable form. This method directly prevents unauthorized users from understanding the data's content, even if they manage to gain access to the file or storage medium itself. It is a fundamental control for ensuring data confidentiality both at rest (stored) and in transit (being transmitted).

A. Steganography: This method focuses on concealing the existence of data within another file or medium, not on making the data itself unreadable. If discovered, the hidden data is typically in its original, readable format.

B. Data masking: This technique creates a structurally similar but inauthentic version of data, primarily for use in non-production environments like testing or training. It protects the original data by replacing it, not by making it unreadable to unauthorized users in a live system.

C. Access control lists (ACLs): ACLs are a form of authorization that determines who is allowed to access a specific file or resource. They prevent access to the data object but do not protect the data's readability if the access controls are bypassed (e.g., physical theft of a hard drive).

1. National Institute of Standards and Technology (NIST). (2020). Special Publication (SP) 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations. Section: SC-28 Protection of Information at Rest. The control description states

"The information system protects the confidentiality and integrity of the following information at rest: [Assignment: organization-defined information at rest]" often through the use of encryption.

2. Saltzer

J. H.

& Schroeder

M. D. (1975). The Protection of Information in Computer Systems. Proceedings of the IEEE

63(9)

1278–1308. (A foundational academic paper referenced in many university security courses). Section I.B.3

"Cryptographic Sealing

" describes encryption as a primary method for ensuring privacy against unauthorized reading. Available via MIT's DSpace: https://dspace.mit.edu/handle/1721.1/46463

3. Perrig

A.

& Song

D. (2014). MIT OpenCourseWare 6.858 Computer Systems Security

Fall 2014. Lecture 1: Introduction & Threat Models. The lecture notes differentiate between access control mechanisms (which can fail) and cryptography (encryption) as a method to protect data content regardless of access.

4. Kaur

M.

& Singh

A. (2014). A Review of Data Masking as a Tool for Data Protection. International Journal of Advanced Research in Computer Science and Software Engineering

4(1)

818-821. This paper defines data masking as a process of "hiding original data with modified content (characters or other data)

" primarily for creating safe test data

distinguishing it from encryption for live data protection.

5. Provos

N.

& Honeyman

P. (2003). Hide and Seek: An Introduction to Steganography. IEEE Security & Privacy

1(3)

32-44. https://doi.org/10.1109/MSECP.2003.1203220. This article clarifies that steganography's goal is to hide communication

making it distinct from cryptography

which aims to make communication unintelligible.

A manufacturing Enterprise Resource Planning (ERP) system is designed to integrate and manage core business processes. A fundamental function within this context is production planning and scheduling. This module helps organize and optimize the allocation of materials, machinery, and labor to meet production targets efficiently. By creating detailed production schedules, the system directly improves internal operations by minimizing downtime, managing inventory levels (work-in-process), and ensuring timely completion of manufacturing orders, thereby enhancing overall operational efficiency and resource utilization.

A. Managing team training certifications is a primary function of a Human Resources Management System (HRMS), not a core manufacturing operations function of an ERP.

C. Tracking customer order delivery satisfaction is a function of a Customer Relationship Management (CRM) system, which focuses on external customer interactions, not internal production processes.

D. Forecasting retail demand patterns is a function associated with Supply Chain Management (SCM) or Business Intelligence (BI) systems, which analyze external market data to inform production.

1. Umble

E. J.

Haft

R. R.

& Umble

M. M. (2003). Enterprise resource planning: Implementation procedures and critical success factors. European Journal of Operational Research

146(2)

241-257. In Section 2

"What is ERP?"

the authors list "production planning" as a key functional module of an ERP system designed to integrate a company's core business processes. (https://doi.org/10.1016/S0377-2217(02)00547-7)

2. Jacobs

F. R.

& Weston Jr

F. C. (2007). Enterprise resource planning (ERP)—A brief history. Journal of Operations Management

25(2)

357-363. On page 360

the paper describes the evolution from MRP to MRP II (the direct predecessor of manufacturing ERP)

noting the expansion to include functions like "scheduling of the factory."

3. MIT OpenCourseWare. (2016). 15.762 Supply Chain Planning

Lecture 5: Enterprise Resource Planning (ERP). Massachusetts Institute of Technology. The lecture notes explicitly identify the Production Planning (PP) module as a core component of ERP systems

responsible for managing and controlling the manufacturing activities of a company

including scheduling.