When a profile assigned to a user is dropped, the Profile attribute for that user in the DBC.UsersV view is set to NULL. Upon the user's next logon, the system applies the system-level defaults for any attributes that would have been controlled by the profile. This includes password attributes such as expiration, complexity, and lockout rules, which are defined in the DBC.SysSecDefaults table and are visible through the DBC.SecurityDefaultsV view. The logon process will succeed, but with these system-wide security settings enforced.

A. While the user's profile setting in the data dictionary does become NULL, this is the cause, not the full effect. The question asks what happens when the user logs on, and this option only describes the state change, not the resulting behavior.

C. The system does not issue a warning message in this scenario. It transparently applies the system-level default settings for the session without notifying the user of the change.

D. Once a profile is dropped, it ceases to exist, and none of its specifications, including SPOOL or DEFAULT DATABASE, can be applied. The user will revert to their own defined attributes from the CREATE/MODIFY USER statement or system defaults.

1. Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, Release 17.20 (B035-1144-172K).

Section: "DROP PROFILE"

Content: "When you drop a profile, any user or profile that was assigned the dropped profile is reassigned to have no profile (the value of the Profile column in DBC.Users is NULL)." This supports the initial state change that leads to the behavior described in the correct answer.

2. Teradata Vantage™ - Security Administration, Release 17.20 (B035-1100-172K).

Chapter 6: "Managing User Passwords", Section: "Password Controls Precedence"

Content: This section explains that if a user is not assigned a profile (i.e., the profile is NULL), the system-level password controls defined in DBC.SysSecDefaults apply. This directly validates that the attributes from DBC.SecurityDefaultsV (the view on DBC.SysSecDefaults) will be used.