The adapter implements an interface to the adaptee and the target

The adapter implements the adaptee interface and holds and instance of the target

The adapter implements the target interface and holds an instance of the adaptee

The adapter holds an instance of the adaptee and the interface

Create a facade to interact with the vendor system

Receive requests from the existing system and convert them into requests that make sense to the new vendor class.

Create a facade to interact with the existing system

Receive requests from the existing system and convert them into requests for the existing system

The client, the adapter and the target

The client and the adapter

The target and the adpater

The client and the target

Most examples of adapter pattern show an adapter with one adaptee, however you may well have situations where an adapter hold two or more adaptees.

Always two

One and only one

An adapter pattern will always be flexible to have multiple adaptees.

No  since they do not keep their own internal context

Yes but do not keep their own internal context

Yes but do keep their own internal context

No since they need keep their own internal context

A new state

A new inheritance

A new interface

A new action

Sub class

Super calss

Interface

Inheritance

All the actions

All the interfaces

All the states

All the static variables

Increase the number of classes

Keep the number of classes the same

Reduce the number of classes

Only move the classes around