One of these statements about the key elements of a good configuration process is NOT true.
Click on the arrows to vote for the correct answer
A. B. C. D.C.
Configuration management isn't about preventing change but ensuring the integrity of IT resources by preventing unauthorised or improper changes.
According to the Official ISC2 guide to the CISSP exam, a good CM process is one that can: (1) accommodate change; (2) accommodate the reuse of proven standards and best practices; (3) ensure that all requirements remain clear, concise, and valid; (4) ensure changes, standards, and requirements are communicated promptly and precisely; and (5) ensure that the results conform to each instance of the product.
Configuration management - Configuration management (CM) is the detailed recording and updating of information that describes an enterprise's computer systems and networks, including all hardware and software components.
Such information typically includes the versions and updates that have been applied to installed software packages and the locations and network addresses of hardware devices.
Special configuration management software is available.
When a system needs a hardware or software upgrade, a computer technician can accesses the configuration management program and database to see what is currently installed.
The technician can then make a more informed decision about the upgrade needed.
An advantage of a configuration management application is that the entire collection of systems can be reviewed to make sure any changes made to one system do not adversely affect any of the other systems Configuration management is also used in software development, where it is called Unified Configuration Management (UCM)
Using UCM, developers can keep track of the source code, documentation, problems, changes requested, and changes made.
Change management - In a computer system environment, change management refers to a systematic approach to keeping track of the details of the system (for example, what operating system release is running on each computer and which fixes have been applied).
Sure, I'll provide a detailed explanation for each option.
A. Accommodate the reuse of proven standards and best practices This statement is true. A good configuration process should incorporate proven standards and best practices as much as possible. This can help ensure that the system is configured in a secure and efficient manner and reduce the risk of errors or vulnerabilities.
B. Ensure that all requirements remain clear, concise, and valid This statement is also true. Clear, concise, and valid requirements are essential for a good configuration process. They help ensure that the system is configured to meet the intended business or operational goals and that the configuration is maintained correctly over time.
C. Control modifications to system hardware in order to prevent resource changes This statement is not true. The wording is a bit unclear, but assuming it means preventing modifications to hardware resources, this is not necessarily a key element of a good configuration process. While hardware modifications can impact the configuration of a system, they are not always relevant or necessary to control as part of the configuration process. The key focus of a configuration process should be on software and system settings.
D. Ensure changes, standards, and requirements are communicated promptly and precisely. This statement is true. Effective communication is crucial to a good configuration process. Changes to the configuration, new standards or requirements, and any other relevant information should be communicated promptly and precisely to all relevant stakeholders to ensure that everyone is on the same page and that the system is configured correctly.