A user, who is authenticated externally, logs in to a remote machine and connects to the database instance. What action would you take to ensure that a user cannot connect to the database instance by merely logging in to a remote machine?

Question

Accepted Answer

C. Set the REMOTE_OS_AUTHENT parameter to FALSE Setting REMOTE_OS_AUTHENT to FALSE disables remote OS-based authentication, preventing any user from connecting to the database instance simply by logging into a remote machine. With this parameter set to FALSE, Oracle refuses OS-authenticated connections from remote clients, requiring explicit database credential verification for all remote sessions.

Answer

A. Set REMOTE_OS_ROLES to FALSE REMOTE_OS_ROLES controls whether OS groups can be used to assign Oracle roles to remote users, not whether remote OS authentication itself is permitted.

Answer

B. Set OS_ROLES parameter to FALSE OS_ROLES is not a standard Oracle initialization parameter governing remote authentication; the correct parameter for this purpose is REMOTE_OS_AUTHENT.

Answer

D. Set the REMOTE_LOGIN_PASSWORD_FILE parameter to NONE REMOTE_LOGIN_PASSWORD_FILE determines how the password file is used for SYSDBA and SYSOPER authentication, not whether remote OS-authenticated connections are permitted.

A user, who is authenticated externally, logs in to a remote machine and connects to the database instance. What action would you take to ensure that a user cannot connect to the database instance…

Question

Options

How the community answered

Why each option

Topics

Community Discussion