For DBAs configuring AP services, which Type do we generally choose?

Question

Options

• AType3
• BType4
• CType1
• DType2

• A
  80% (24)
• B
  13% (4)
• C
  3% (1)
• D
  3% (1)

Explanation

Type3 is the correct choice for DBAs configuring AP (Application) services because it functions as a middleware-based, pure-Java network protocol driver that doesn't require native database client libraries on each application server - making it the standard fit for application-tier service configurations where flexibility and portability across environments matter.

Why the distractors are wrong:

• Type1 uses an ODBC bridge, which is legacy, platform-dependent, and unsuitable for modern AP service configurations.
• Type2 relies on native client libraries installed locally, adding overhead and reducing portability - not practical for centralized AP service management.
• Type4 is a direct "thin" driver ideal for end-user applications connecting straight to the database, but it bypasses the middleware layer that AP services typically depend on.

Memory tip: Think "3 = Three-tier" - Type3 lives in the middle (middleware) tier, which is exactly where AP services sit between the application and the database.

No community discussion yet for this question.