CAS-002 · Question #883
Customers have recently reported incomplete purchase history and other anomalies while accessing their account history on the web server farm. Upon investigation, it has been determined that there…
The correct answer is A. Implement change control practices at the organization level. Version mismatches caused by developers directly modifying production servers indicate an absence of formal change control, which enforces a structured and auditable release process.
Question
Customers have recently reported incomplete purchase history and other anomalies while accessing their account history on the web server farm. Upon investigation, it has been determined that there are version mismatches of key e-commerce applications on the production web servers. The development team has direct access to the production servers and is most likely the cause of the different release versions. Which of the following process level solutions would address this problem?
Options
- AImplement change control practices at the organization level.
- BAdjust the firewall ACL to prohibit development from directly accessing the production server
- CUpdate the vulnerability management plan to address data discrepancy issues.
- DChange development methodology from strict waterfall to agile.
How the community answered
(28 responses)- A82% (23)
- B4% (1)
- C11% (3)
- D4% (1)
Why each option
Version mismatches caused by developers directly modifying production servers indicate an absence of formal change control, which enforces a structured and auditable release process.
Implementing change control practices requires all modifications to production systems to go through a formal approval, testing, and documentation process before deployment, eliminating unauthorized direct access that causes inconsistent application versions across the server farm.
Restricting firewall ACLs addresses network-level access but does not establish the process controls and approval workflows needed to govern legitimate deployments through proper channels.
A vulnerability management plan is scoped to identifying and remediating security weaknesses, not to controlling software release consistency caused by unmanaged direct deployments.
Switching from waterfall to agile modifies the development methodology but does not prevent developers from bypassing a release pipeline and pushing changes directly to production.
Concept tested: Change control to prevent unauthorized production deployments
Source: https://learn.microsoft.com/en-us/azure/devops/boards/change-management/change-management-overview
Topics
Community Discussion
No community discussion yet for this question.