nerdexam
Oracle

1Z0-083 · Question #34

Which two statements are true about the Oracle Database server architecture?

The correct answer is C. Each server process has its own User Global Area (UGA). D. A connection represents the state of a user's login to an instance. D is correct because a connection represents the state of a user's login to an Oracle Database instance - it is the established communication link that persists as long as the user is logged in. C is correct because in dedicated server mode, each server process has its own PGA…

Oracle Database Architecture

Question

Which two statements are true about the Oracle Database server architecture?

Options

  • AAn Oracle Database server process represents the state of a user's login to an instance.
  • BAn Oracle Database server process is always associated with a session.
  • CEach server process has its own User Global Area (UGA).
  • DA connection represents the state of a user's login to an instance.
  • EThe entire data dictionary is always cached in the large pool.

How the community answered

(55 responses)
  • A
    5% (3)
  • B
    11% (6)
  • C
    80% (44)
  • E
    4% (2)

Explanation

D is correct because a connection represents the state of a user's login to an Oracle Database instance - it is the established communication link that persists as long as the user is logged in. C is correct because in dedicated server mode, each server process has its own PGA, and the UGA (which stores session-specific cursor states, sort areas, etc.) resides within that PGA, making it exclusive to that process.

Why the distractors are wrong:

  • A confuses a server process (an OS-level process that executes SQL) with the connection, which is the entity that actually represents the login state.
  • B is false in shared server mode - a single server process can serve multiple sessions, so the 1:1 relationship doesn't always hold.
  • E is a classic trap: the data dictionary is cached in the shared pool (dictionary cache), not the large pool. The large pool is reserved for RMAN, parallel query buffers, and shared server UGA storage.

Memory tip: Think "Connection = Current login state" and associate UGA with the server process by remembering dedicated = dedicated memory - each dedicated server process owns its own UGA inside its PGA. For E, remember the large pool does large jobs (backups, parallel ops), not data dictionary lookups.

Topics

#Server Processes#Connections and Sessions#User Global Area (UGA)#Instance Architecture

Community Discussion

No community discussion yet for this question.

Full 1Z0-083 Practice