Ipt quiz 1 Flashcards

1
Q

IT integration
is the process of joining software and hardware
modules into one cohesive infrastructure.
The goal is to make these systems work
together smoothly so they can share
information and processes more efficiently.

A

System Integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

common business problems

A
  • poor productivity
  • uninformed decision-making and errors
  • high cost
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

because of complicated access to
data and redundant tasks across siloed
infrastructure. Integrated systems allow for easier
access to information across the organization,
resulting in faster, more efficient workflows.

A

Poor productivity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

that might
happen because of incomplete or inaccurate data
(especially in compliance and reporting workflows).

A

Uninformed decision-making and errors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

of developing or transitioning to a new
system. System integration is often cheaper than
replacing all disjointed parts with a new single
system, not to mention the tricky process of
implementing new computer infrastructures.

A

High cost

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

System Integration Challenges

A
  • Compatibility issues
  • Security and Compliance
  • Resource Constraints
  • Maintenance and Upgrades
  • Change Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Different systems may use
different technology stacks, data formats, or protocols.
Making these systems communicate effectively can require
significant effort in terms of middleware, data
transformation, or custom interfaces.

A

Compatibility Issues

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Integrating multiple systems
can introduce vulnerabilities and create the risk of data
breaches and unauthorized access, especially if the
systems have different security protocols. Ensuring data
is secure and that the integration complies with all
relevant laws and regulations is a significant challenge.

A

Security and compliance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  • Though, as we said, it’s usually
    cheaper than building a new, comprehensive platform,
    system integration can still be resource-intensive,
    requiring significant investments of time, expertise, and
    money. Budget constraints and resource allocation can
    limit the scope of integration projects.
A

Resource constraints

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Integration
can create dependencies that make it
difficult to change or update one
system without affecting others.

A

Maintenance and upgrades

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Integrating
systems often requires changes in
business processes and workflows.
Managing these changes and ensuring
that all stakeholders are on board and
properly trained can be a significant
undertaking.

A

Change management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

SYSTEM INTEGRATION TYPES

A
  • Legacy System Integration
  • Enterprise Application Integration
  • Third-Party System Integration
  • Business to Business Integration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Integration of modern applications into
existing, outdated systems.

A

LEGACY SYSTEM INTEGRATION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Unification of different subsystems
inside one business environment.

A

ENTERPRISE APPLICATION INTEGRATION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Integration of _____ tools is a great option
when your business needs new functionality but can’t
afford custom software development or just has no
time to wait for features to be built from scratch.

A

THIRD-PARTY SYSTEM INTEGRATION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

automates
transactions and document exchange across companies.
It leads to more efficient cooperation and trade
with suppliers, customers, and partners.

A

BUSINESS-TO-BUSINESS INTEGRATION

17
Q

WAYS TO CONNECT SYSTEMS

A
  • Application Programming Interfaces
  • Middleware
  • Web Hooks
  • EDI (electronic data interchange)
18
Q

provide the most common and straightforward way to connect two systems. Sitting between
applications and web services, they enable the transmission of data and functionality in a
standardized format. Most online service providers — from social media to travel platforms
— build external APIs so that clients can easily link to their products.

A

APPLICATION PROGRAMMING
INTERFACES (APIs)

19
Q

is the hidden software layer that glues together distributed systems, applications,
services, and devices. It handles different tasks such as data management,
messaging, API management, or authentication. Cloud middleware can be accessed via
APIs. In turn, an API gateway can be considered a type of middleware between a
collection of services and systems using them.

A

MIDDLEWARE

20
Q

also known as HTTP callbacks are real-time messages, sent by one system
to another when a certain event happens. Say, accounting software may
receive webhook notifications about transactions from payment gateways
or online banking systems.

21
Q

is the exchange of
business information in a standard electronic format, that replaces
paper documents. generally happens in two ways: via a value-added
network (VAN), in which a third-party network is in charge of data
transmission, or direct connections through the Internet.

22
Q

APPROACH SYSTEM INTEGRATION

A
  • Point-to-point (star/spaghetti) model
  • Hub-and-spoke model
  • EnterpriseService Bus (ESB) model
23
Q

is the architectural pattern in which
every system is directly connected
to all other systems and apps it needs to
work in tandem and share information
with. This model can be realized via
APIs, webhooks, or custom code.

A

Point-to-point (star/spaghetti) model

24
Q

is a more advanced type of integration
architecture that addresses the issues
of point-to-point and helps to avoid
the star/spaghettimess. The connections between all subsystems are handled by a central hub (message broker), so they

A

Hub-and-spoke model

25
Q

involves the creation of a separate specialized subsystem
— that serves as
a common user interface layer connecting other subsystems.

A

Enterprise Service Bus (ESB) model

26
Q

DEPLOYMENT OPTIONS FOR INTEGRATED SYSTEMS

A
  • Integration platform as a Service (iPaaS)
  • Hybrid integration platform (HIP)
27
Q

is a set of cloud-based integration solutions mostly used
for building and deploying integrations in the cloud

A

Integration platform as a Service
(iPaaS)

28
Q

is a more universal
version of what iPaaS offers. It is an array of
integration software providing built-in capabilities to
make on-premises and cloud-based solutions work as a
single unit.

A

Hybrid integration platform (HIP)

29
Q

KEY STEPS OF SYSTEM INTEGRATION

A
  • planning and feasibility analysis
  • Architecture Modeling
  • Implementation
  • Maintenance
30
Q

is an individual or company that helps clients bridge
scattered computer subsystems from different vendors and
ensures those subsystems function in accordance with one
another. System integrators perform various tasks such as
planning, regulating, testing, and often maintaining
computer operations.

A

A system integrator (SI)