nerdexam
(ISC)2

CISSP · Question #388

If a content management system (CSM) is implemented, which one of the following would occur?

The correct answer is C. Developers would no longer have access to production systems. A Change/Configuration Management System (CMS) enforces separation of duties by ensuring developers work only in development/test environments and cannot directly access or modify production systems.

Submitted by thandi_sa· Mar 5, 2026Software Development Security

Question

If a content management system (CSM) is implemented, which one of the following would occur?

Options

  • AThe test and production systems would be riming the same software
  • BThe applications placed into production would be secure
  • CDevelopers would no longer have access to production systems
  • DPatching the systems would be completed mere quickly

How the community answered

(39 responses)
  • A
    3% (1)
  • B
    5% (2)
  • C
    90% (35)
  • D
    3% (1)

Why each option

A Change/Configuration Management System (CMS) enforces separation of duties by ensuring developers work only in development/test environments and cannot directly access or modify production systems.

AThe test and production systems would be riming the same software

A CMS does not guarantee that test and production systems run identical software versions; in fact, test environments may intentionally run newer or different versions to validate changes before promotion.

BThe applications placed into production would be secure

A CMS controls how changes are deployed but does not inherently guarantee that applications placed into production are secure, as security depends on the code quality, testing, and security review processes themselves.

CDevelopers would no longer have access to production systemsCorrect

A core security principle of a CMS is enforcing separation of duties and least privilege by restricting developer access to production environments. Changes must be formally reviewed, approved, and promoted through a controlled pipeline (dev → test → production), preventing unauthorized or accidental modifications to live systems by developers.

DPatching the systems would be completed mere quickly

A CMS introduces formal change control processes that typically add approval steps and documentation requirements, which can slow down patching rather than accelerating it.

Concept tested: Change management separation of duties in production environments

Source: https://www.nist.gov/publications/guide-enterprise-patch-management-planning-preventive-maintenance-technology

Topics

#Content Management System#Separation of duties#SDLC security#Production access control

Community Discussion

No community discussion yet for this question.

Full CISSP Practice