Access controls are meant to protect facilities and computers as well as people.
In some situations, the objectives of physical access controls and the protection of people's lives may come into conflict. In theses situations, a person's life always takes precedence.
Many physical security controls make entry into and out of a facility hard, if not impossible.
However, special consideration needs to be taken when this could affect lives. In an information processing facility, different types of locks can be used and piggybacking should be prevented, but the issue here with automatic locks is that they can either be configured as fail-safe or fail-secure.
Since there should only be one access door to an information processing facility, the automatic lock to the only door to a man-operated room must be configured to allow people out in case of emergency, hence to be fail-safe (sometimes called fail-open), meaning that upon fire alarm activation or electric power failure, the locking device unlocks. This is because the solenoid that maintains power to the lock to keep it in a locked state fails and thus opens or unlocks the electronic lock.
Fail Secure works just the other way. The lock device is in a locked or secure state with no power applied. Upon authorized entry, a solinoid unlocks the lock temporarily. Thus in a
Fail Secure lock, loss of power of fire alarm activation causes the lock to remain in a secure mode.
Reference(s) used for this question:
Harris, Shon (2012-10-18). CISSP All-in-One Exam Guide, 6th Edition (p. 451). McGraw-
Hill. Kindle Edition.
and
Hernandez CISSP, Steven (2012-12-21). Official (ISC)2 Guide to the CISSP CBK, Third
Edition ((ISC)2 Press) (Kindle Locations 20249-20251). Auerbach Publications. Kindle Edition.

The class A address range is 1.0.0.0 to 126.255.255.255. The class B address range is 128.0.0.0 to 191.255.255.255. The class C address range is from 192.0.0.0 to 223.255.255.255. The class D address range is 244.0.0.0 to 239.255.255.255, and is used for multicast packets. Sources: Designing Network Security by Merike Kaeo (Cisco Press, 1999) and CCNA Study Guide by Todd Lammle, Donald Porter, and James Chellis (Sybex, 1999).

The change that should be made to the resource's access to the production operating system (OS) directory structure to support the least privilege security principle when a resource is transferring within the organization from a production support system administration role to a developer role is from Administrator privileges to No Access privileges. The least privilege security principle is a security principle or practice that states that the access or use of a system, network, or resource, by the users, devices, or processes, should be limited or restricted to the minimum or necessary level or amount, that is required or sufficient to perform or complete their assigned or authorized tasks or functions. The least privilege security principle can help to ensure the security, efficiency, or performance of the system, network, or resource, as well as to protect the system, network, or resource from various security threats or risks, such as unauthorized access, data leakage, or privilege escalation. The least privilege security principle can be implemented or enforced by using various security mechanisms or functions, such as access control lists, role-based access control, or separation of duties, that can define, regulate, or restrict the access or use of the system, network, or resource, by the users, devices, or processes, based on a set of rules, policies, or criteria. The change that should be made to the resource's access to the production operating system (OS) directory structure to support the least privilege security principle when a resource is transferring within the organization from a production support system administration role to a developer role is from Administrator privileges to No Access privileges. Administrator privileges are the highest or most powerful level or type of privileges or permissions that can be granted or assigned to a user, device, or process, that can allow or enable them to access or use the system, network, or resource, without any limitation, restriction, or supervision, as well as to perform or execute any action, operation, or function, on the system, network, or resource, such as creating, modifying, deleting, or configuring the system, network, or resource. No Access privileges are the lowest or least level or type of privileges or permissions that can be granted or assigned to a user, device, or process, that can deny or prevent them from accessing or using the system, network, or resource, as well as from performing or executing any action, operation, or function, on the system, network, or resource. The resource's access to the production operating system (OS) directory structure should be changed from Administrator privileges to No Access privileges, to support the least privilege security principle, when the resource is transferring within the organization from a production support system administration role to a developer role, because the resource no longer needs or requires the Administrator privileges to perform or complete their new or current tasks or functions, as a developer, and the resource should not have any access or use of the production operating system (OS) directory structure, as a developer, to prevent or avoid any potential security problems or issues, such as data corruption, system malfunction, or configuration error, that may affect the production operating system (OS) directory structure. From Read Only privileges to No Access privileges, from Author privileges to Administrator privileges, or from No Access privileges to Author privileges are not the changes that should be made to the resource's access to the production operating system (OS) directory structure to support the least privilege security principle when a resource is transferring within the organization from a production support system administration role to a developer role, as they are either more related to the other levels or types of privileges or permissions, such as Read Only privileges, which can allow or enable the user, device, or process to view or read the system, network, or resource, but not to modify or change the system, network, or resource, or Author privileges, which can allow or enable the user, device, or process to create or modify the system, network, or resource, but not to delete or configure the system, network, or resource, that may not be appropriate, necessary, or sufficient for the resource to perform or complete their new or current tasks or functions, as a developer, or to the other roles or positions, such as a production support system administrator, which may have different or distinct tasks or functions, responsibilities or accountabilities, or requirements or expectations, from a developer, that may affect or determine the level or type of privileges or permissions that should be granted or assigned to the resource to access or use the production operating system (OS) directory structure. References: CISSP All-in-One Exam Guide, Eighth Edition, Chapter 5: Identity and Access Management, page 281; CISSP Official (ISC)2 Practice Tests, Third Edition, Domain 5: Identity and Access Management, Question 5.13, page 223.