"Managing roles and privileges has its challenges because the user could be a database administrator seeking access to specific tables or objects. As part of our security best practices, I assign rules by role membership by group. I find this to be the best way of managing privileges, this way privileges can be revoked or granted to a group as a whole. I'm intimately familiar with a Greenplum database and how it works. For example, Greenplum requires a UNIX user ID to initialize and access the Greenplum database. This protocol is pretty standard in the industry, and widely used for creating new rules, and protecting passwords in the Greenplum database."

"If you look at various network infrastructures and architectures within companies, you will find a variety of user/role attributes. One of the user roles that I keep a close watch on is giving access to SUPERUSERS. I like to limit access to SU's for a number of reasons, one of the biggest is SU's bypass all access privilege checks in Greenplum dataset. In my humble opinion, I think only administrators should have that access since we are intimately involved in the protection and security of the organization."

There are numerous occasions when someone needs an important document for something like a proposal, and the only place the data needed is on a server or drive that requires administrative access. If you've ever needed to access folders or files that are locked or inaccessible, you understand this issue. When answering this question, you need to point out that you always follow protocol when granting admin-level permission to a user. This demonstrates your adherence to company cyber security policies, and your understanding of how having admin access can cause serious security breaches. You may want to note that your old and two exceptions to this role, but only with the appropriate approval by individuals with authority to grant this.