Which statement reflects the handling of generic and shared IDs in access control?

Which statement reflects the handling of generic and shared IDs in access control?

• A. Generic User IDs Are Disabled Or Removed
• B. Generic User IDs Can Be Used For Convenience
• C. Shared IDs Exist For Critical Functions
• D. Group IDs Are Required For System Administration

Answer: (B)

The idea being tested is how to manage generic and shared IDs so that operations run smoothly without losing accountability. The statement that generic user IDs can be used for convenience reflects a real-world need: service accounts and shared credentials are often used to run automated tasks, batch jobs, or system services that don’t correspond to a single person. When these IDs are present, they must be governed tightly. This means giving them only the minimum privileges necessary (least privilege), keeping them separate from personal user accounts, documenting their exact purpose, and enforcing strong authentication. Most importantly, every action taken under a generic or shared ID should be logged and attributable to a responsible owner, so activity can be traced even though the account isn’t tied to one individual. Credential rotation, restricted interactive access, and regular reviews of who and what uses these IDs are essential safeguards. So, recognizing that generic IDs exist for convenience, but still applying strict controls and monitoring, reflects the practical yet secure handling described by the correct choice.

The idea being tested is how to manage generic and shared IDs so that operations run smoothly without losing accountability. The statement that generic user IDs can be used for convenience reflects a real-world need: service accounts and shared credentials are often used to run automated tasks, batch jobs, or system services that don’t correspond to a single person. When these IDs are present, they must be governed tightly. This means giving them only the minimum privileges necessary (least privilege), keeping them separate from personal user accounts, documenting their exact purpose, and enforcing strong authentication. Most importantly, every action taken under a generic or shared ID should be logged and attributable to a responsible owner, so activity can be traced even though the account isn’t tied to one individual. Credential rotation, restricted interactive access, and regular reviews of who and what uses these IDs are essential safeguards. So, recognizing that generic IDs exist for convenience, but still applying strict controls and monitoring, reflects the practical yet secure handling described by the correct choice.