Examkin

Patch and Configuration Management

42 soru

Tüm türler42Çoktan seçmeli20Çoklu seçim11Sıralama11
Soru 1Soru →

To enforce strict endpoint security across a hybrid workforce, a security team is designing a host health validation strategy to enforce configuration baselines and patch management standards. Which of the following technical controls directly ensure that endpoints maintain verified baseline configurations and patch levels? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploying configuration management agents to continuously audit workstation settings against established security baselines and automatically remediate configuration drift; Implementing Network Access Control (NAC) posture assessment to check endpoint operating system patch levels against mandatory patch compliance SLAs before granting network access

Cevap

Deploying automated configuration management agents to remediate baseline drift and implementing Network Access Control (NAC) posture assessments to verify patch compliance.
Maintaining secure host states requires verifying both software patch levels and baseline configurations. Automated configuration management agents detect and correct unauthorized setting changes (configuration drift), while posture assessment mechanisms (such as NAC) evaluate patch levels against defined SLAs to ensure non-compliant systems are isolated or updated prior to granting network access.

Adım Adım Çözüm

1
Identify mechanisms that enforce configuration baselines and remediate configuration drift on endpoints.
Automated configuration management agents continuously monitor system settings and restore non-compliant settings back to authorized baselines.
Baseline enforcement requires local or agent-based auditing and automated remediation.
2
Identify mechanisms that validate endpoint patch compliance during network admission.
Network Access Control (NAC) posture assessments check host patch status against organization SLAs prior to network authorization.
NAC posture checks prevent unpatched or vulnerable systems from joining the corporate network.

Anahtar Kavram

Continuous configuration baseline auditing, drift remediation, and endpoint patch compliance validation.
Soru 2Soru →

During a routine security audit, a security analyst discovers that several Linux web servers hosted in an Infrastructure as a Service (IaaS) environment have diverged from the enterprise's hardened configuration baseline after manual hotfixes were applied by system administrators. Which of the following implementation strategies best provides automated drift detection and continuously enforces the designated configuration baseline across the server fleet?

Cevabı ve açıklamayı göster

Cevap: Deploying configuration management tools utilizing declarative state files operating in enforcement mode

Cevap

Deploying configuration management tools utilizing declarative state files operating in enforcement mode
The correct response utilizes declarative configuration management (such as Ansible, Puppet, or Chef) operating in enforcement mode. These tools continuously audit the system's current state against an authoritative configuration baseline and automatically remediate any detected drift back to the defined security state.

Adım Adım Çözüm

1
Analyze the problem requirements
Identified the need to remediate manual configuration drift on IaaS Linux web servers automatically and continuously.
Manual changes lead to unapproved deviations from established security baselines.
2
Evaluate the cloud shared responsibility model and control capabilities
Eliminated relying on the CSP for OS configuration as IaaS places OS management responsibilities on the customer. Eliminated network firewalls and HIPS as they do not provide automated state remediation.
Control selection must directly address host OS configuration enforcement.
3
Select the appropriate configuration management mechanism
Chosen configuration management software executing declarative policy files in enforcement mode.
Declarative tools regularly check system state against the baseline artifact and automatically overwrite unapproved manual edits back to the approved state.

Anahtar Kavram

Configuration Baseline Drift Remediation
Soru 3Soru →

A security analyst is establishing a patch and configuration management procedure for an air-gapped Industrial Control System (ICS) network following the disclosure of a critical firmware vulnerability. Which of the following technical controls and procedural steps should the analyst execute to ensure safe patch deployment and maintain system baselines? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Validate patches in an isolated staging environment using offline installation media verified with cryptographic hashes prior to deployment.; Archive verified offline baseline configuration backups and maintain documented roll-back plans for all managed controllers before executing updates.

Cevap

The correct procedures are validating patches in an isolated staging environment using cryptographically verified offline media, and archiving verified offline baseline configuration backups with documented roll-back plans prior to update execution.
In air-gapped industrial environments, patch and configuration management requires verifying file integrity via cryptographic hashes, testing updates in a staging environment prior to production release, and securing baseline configurations with tested roll-back mechanisms to ensure high availability and prevent unexpected system outages.

Adım Adım Çözüm

1
Analyze environment constraints and patch management prerequisites for specialized networks.
Identified that an air-gapped ICS network cannot rely on direct internet connectivity or unverified media.
Air-gapped systems require offline patch distribution mechanisms with strong integrity verification.
2
Select appropriate staging, verification, and roll-back controls.
Offline hash verification in a mirror environment combined with baseline configuration archiving ensures safe deployment and rapid restoration if instability occurs.
Pre-deployment testing mitigates operational disruption, and baseline backups enable roll-back during unexpected configuration drift.

Anahtar Kavram

Air-gapped Patch and Configuration Management Lifecycle
Soru 4Soru →

A security engineer at a utility organization oversees a fleet of distributed industrial edge gateways. Following a vendor firmware patch rollout, a security audit reveals that multiple gateways experienced configuration drift, automatically re-enabling legacy, unencrypted management protocols that violate organizational hardening standards. The engineer must implement a solution that continuously detects non-compliant settings and automatically restores all gateways to their authorized security baseline without manual intervention. Which of the following is the BEST solution to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy an automated configuration orchestration tool enforcing declarative baseline templates to continuously audit and remediate unauthorized setting changes.

Cevap

Deploying an automated configuration orchestration tool enforcing declarative baseline templates is the best solution because it continuously monitors for configuration drift and automatically restores system settings to the authorized security baseline without manual intervention.
Deploying an automated configuration orchestration tool using declarative baseline templates directly addresses configuration drift. It continuously audits device configurations against the golden baseline standard and automatically enforces compliance by reverting unauthorized setting changes, ensuring endpoints remain hardened without requiring manual intervention.

Adım Adım Çözüm

1
Analyze organizational requirements
Identified the need for continuous configuration drift detection and automated remediation to enforce hardening baselines.
The scenario highlights host-level setting changes resulting from a patch deployment that must be automatically rectified.
2
Evaluate control types for configuration management
Configuration orchestration (such as IaC or configuration management agents) directly maintains system state against baseline templates.
Preventive and compensating network controls (NIPS, firewalls) or periodic detective tools (vulnerability scanners) do not restore local endpoint baselines automatically.
3
Select the optimal solution
Chosen automated configuration orchestration tool enforcing declarative templates.
This fulfills both continuous auditing and automated remediation requirements.

Anahtar Kavram

Configuration Baseline Enforcement and Automated Drift Remediation
Tahmini Süre:2m 0s
Soru 5Soru →

An organization notices that several corporate laptops used by remote employees have failed to apply a critical operating system security patch dispatched by the patch management server. Investigation reveals that the employees continuously opted to defer the required system restart, causing their devices to fall out of compliance with the enterprise security configuration baseline. Which of the following technical controls would most effectively enforce compliance and ensure the required patch installation before granting endpoints access to internal network resources?

Cevabı ve açıklamayı göster

Cevap: Configure Network Access Control posture assessment policies to isolate non-compliant devices to a remediation network until the update is installed.

Cevap

Configure Network Access Control posture assessment policies to isolate non-compliant devices to a remediation network until the update is installed.
Network Access Control (NAC) posture assessment performs pre-admission or continuous checks on connecting devices to verify compliance with configuration baselines (such as installed OS patches and updates). Devices failing posture checks are placed in a quarantined or remediation network segment where required updates can be completed before full network access is granted.

Adım Adım Çözüm

1
Analyze the security operational requirement
Identified the core requirement: enforcing patch compliance and reboot completion on non-compliant endpoints before allowing access to network resources.
Remote devices falling behind on security baselines create vulnerable entry points into the enterprise network.
2
Evaluate technical controls for posture evaluation and enforcement
Network Access Control (NAC) posture checking validates patch status, antivirus signatures, and configurations during host connection.
If an endpoint fails the health check (posture assessment), NAC can restrict access or place the device into a quarantined remediation VLAN where patches and restarts are executed automatically.
3
Distinguish between technical enforcement and administrative or misapplied controls
Select the NAC posture assessment control over WAF rules, system rollbacks, or administrative reminders.
NAC provides automated technical enforcement directly aligned with patch management and host configuration baseline compliance.

Anahtar Kavram

Endpoint Posture Assessment and Remediation via Network Access Control (NAC)
Tahmini Süre:1m 30s
Soru 6Soru →

A security administrator is establishing a baseline security workflow to ensure that all newly deployed workstations meet organizational security standards and remain protected against known software flaws. Which of the following operational practices should the administrator implement to maintain system integrity and compliance? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Establishing standardized configuration baselines across all workstation images prior to deployment; Implementing an automated patch management process to deploy verified vendor updates regularly

Cevap

The administrator should establish standardized configuration baselines across workstation images and implement an automated patch management process.
Establishing secure configuration baselines ensures consistent secure state defaults upon deployment, while implementing automated patch management maintains system security by applying vendor updates to resolve software flaws continuous across the lifecycle.

Adım Adım Çözüm

1
Identify baseline configuration needs
Creating initial configuration baselines ensures all workstations start in a secure, uniform state.
Prevents configuration drift and default misconfigurations across newly deployed systems.
2
Implement centralized automated patching
Ongoing automated patching updates operating systems and applications with the latest security fixes.
Reduces security risks associated with known unpatched vulnerabilities over time.

Anahtar Kavram

Patch and Configuration Management
Tahmini Süre:1m 0s
Soru 7Soru →

A security team managing an isolated air-gapped operational technology (OT) network discovers widespread configuration drift across engineering workstations during a compliance audit. Simultaneously, a critical zero-day vulnerability advisory requires immediate software updates on these systems. Which of the following procedures should the security team implement to remediate the configuration drift while safely deploying emergency security patches? (Select TWO).

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Establish a validated baseline using configuration audit scripts in an isolated staging environment before applying signed offline patch packages via inspected media.; Conduct a formal change advisory board (CAB) review to approve emergency deployment windows and verified system rollback points prior to production deployment.

Cevap

The security team should establish a validated configuration baseline in an isolated staging environment using signed offline patch packages, and conduct a formal change advisory board review with defined rollback points before updating production systems.
Remediating configuration drift and vulnerabilities in air-gapped environments requires staging offline, cryptographically signed updates to maintain network isolation, alongside rigorous change control processes including rollback planning to protect operational stability.

Adım Adım Çözüm

1
Evaluate patch deployment methods compatible with air-gapped security boundaries.
Identify that offline, cryptographically signed patch packages tested on staging environments preserve network isolation while remediating vulnerabilities.
Direct internet or cloud connections undermine the security posture of air-gapped industrial environments.
2
Integrate emergency remediation with formal change management processes.
Obtain Change Advisory Board approval and verify restore/rollback capabilities prior to modifying production configurations.
Operational technology environments require strict change governance to prevent system instability during emergency patch deployment.
3
Reject ineffective compensating controls and unauthorized architecture changes.
Discard options suggesting temporary network bridging or using IPS rules as permanent replacements for OS software patches.
Compensating controls do not eliminate underlying software flaws or baseline drift, and bridging networks violates isolation requirements.

Anahtar Kavram

Air-Gapped Patch Management and Configuration Baseline Enforcement
Soru 8Soru →

A security engineer at a financial institution is reviewing a post-incident report for a critical web application server that was compromised. The investigation revealed that during an off-hours emergency software update, a vendor-supplied deployment script overwritten local system security parameters, reverting the server to an unhardened default baseline. Although the application vulnerability itself was successfully patched, administrative services were inadvertently exposed to the public network. Which of the following operational controls would best prevent this type of configuration drift during future patch deployments?

Cevabı ve açıklamayı göster

Cevap: Enforce continuous automated configuration management using declarative policy manifests to validate and remediate host state post-deployment.

Cevap

Enforcing continuous automated configuration management using declarative policy manifests to validate and remediate host state post-deployment is the correct action.
Automated configuration management tools operating with declarative state definitions continuously audit managed endpoints against designated security baselines. If a patch deployment script alters configuration parameters, the configuration management agent detects the variance (drift) and automatically enforces the mandated secure baseline.

Adım Adım Çözüm

1
Analyze the incident root cause.
The compromise resulted from configuration drift, specifically unhardened default settings being restored by a patch installation script.
Identifying that the failure was a configuration drift issue narrows down the required solution to baseline maintenance controls rather than patch acquisition or perimeter filtering.
2
Evaluate control options against configuration drift prevention.
Automated configuration management tools (such as Ansible, Puppet, or Chef) enforce declarative baselines and correct unauthorized modifications automatically.
Declarative tools ensure that host settings match the defined security standard regardless of changes made by intermediate patch scripts.

Anahtar Kavram

Configuration Baseline Enforcement and Drift Detection
Soru 9Soru →

An enterprise organization operating an immutable containerized infrastructure discovers a critical zero-day vulnerability in its base operating system image across multiple microservices. What is the correct chronological sequence of steps the security operations team must perform to remediate this vulnerability while maintaining configuration integrity and change control compliance?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins with identifying affected container repositories using SBOM telemetry, updating base image directives in source manifests, executing automated regression testing in a staging environment, obtaining formal Change Advisory Board authorization backed by test metrics and rollback plans, and concluding with a canary deployment to production accompanied by continuous configuration baseline auditing.
The sequence correctly reflects standard enterprise patch management for immutable environments: initial asset scoping using Software Bill of Materials (SBOM) data occurs first; updates are committed to Infrastructure-as-Code manifests; pre-deployment automated regression testing in staging provides the mandatory verification evidence needed for Change Advisory Board (CAB) approval; and production deployment proceeds via canary release paired with ongoing configuration drift auditing.

Adım Adım Çözüm

1
Inventory and scope analysis
Identification of all vulnerable container image dependencies across microservices
Scoping via SBOM data ensures accurate mapping of all affected artifacts before initiating code alterations.
2
Infrastructure-as-Code (IaC) configuration update
Updated base image version committed to source repository development branch
Immutable infrastructure dictates that patches are declared in source code manifests rather than applied to active workloads.
3
Pre-deployment validation in staging
Empirical confirmation of patch stability and security control effectiveness
Staging verification prevents broken builds or incompatible patches from impacting live enterprise operations.
4
Change control governance
Formal approval granted by the Change Advisory Board (CAB)
Enterprise governance requires empirical test documentation and risk mitigation plans prior to production release.
5
Production rollout and baseline auditing
Controlled canary rollout and ongoing detection of configuration drift
Gradual rollout mitigates deployment blast radius, while ongoing auditing ensures production containers match the approved baseline.

Anahtar Kavram

Enterprise Patch and Configuration Management Lifecycle for Immutable Infrastructure
Soru 10Soru →

A security analyst is preparing to roll out a critical operating system update across an enterprise environment. To minimize operational risk and prevent application incompatibility during deployment, which of the following actions should be performed FIRST?

Cevabı ve açıklamayı göster

Cevap: Test the update in a representative non-production staging environment.

Cevap

Testing the update in a representative non-production staging environment.
Testing patches in a representative staging environment ensures that potential software conflicts, performance issues, or system crashes are identified and resolved before updates are introduced into live operational environments.

Adım Adım Çözüm

1
Identify the primary goal of patch management testing controls.
Recognize that software patches must be validated prior to broad deployment to avoid unexpected downtime.
Unvalidated patches may introduce bugs or break critical dependencies.
2
Determine the appropriate initial environment for patch execution.
Select a isolated staging or sandbox environment that mirrors production configurations.
Staging testing confirms stability and application compatibility safely before production rollout.

Anahtar Kavram

Patch Testing and Staging Environment Validation
Tahmini Süre:1m 0s
Soru 11Soru →

A security administrator needs to apply a critical security update to enterprise web servers. What is the correct sequence of steps the administrator should follow to complete the patch management workflow?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence for the patch management process is: 1) Identify and acquire the security patch, 2) Validate and test the patch in a non-production staging environment, 3) Submit a change request for approval by the Change Advisory Board, and 4) Deploy the patch to production servers.
The standard enterprise patch management lifecycle progresses logically from patch discovery and acquisition, to non-production staging validation, followed by formal governance approval from the Change Advisory Board, and concluding with scheduled deployment to production systems.

Adım Adım Çözüm

1
Identify and acquire the security patch from a verified vendor source.
The authentic security update is retrieved and verified.
You must obtain and verify the update before testing or scheduling deployment.
2
Validate and test the security patch in a non-production staging environment.
Patch stability, performance impact, and compatibility are verified.
Staging validation detects software conflicts without jeopardizing live production services.
3
Submit a change request for review and approval by the Change Advisory Board (CAB).
Formal authorization and back-out plans are officially documented and approved.
Enterprise change governance requires technical test evidence before approving live modifications.
4
Deploy the patch to production servers during an authorized maintenance window.
Production systems are updated with minimal disruption to users.
Deployment occurs only after validation and governance requirements are fully satisfied.

Anahtar Kavram

Standard Enterprise Patch Management Lifecycle
Soru 12Soru →

A security operations team discovers that critical production servers frequently experience configuration drift due to uncoordinated hotfixes applied by system administrators during emergency outage incidents. Although automated configuration auditing tools successfully flag these non-compliant system states during nightly scans, security engineers cannot readily distinguish between unauthorized vulnerabilities and approved emergency hotfixes. Which of the following solutions should the security team implement to effectively manage configuration drift while maintaining audit compliance for emergency changes?

Cevabı ve açıklamayı göster

Cevap: Integrate automated configuration management systems with the service management database to dynamically reconcile live endpoint baseline scans against authorized emergency change requests.

Cevap

Integrate automated configuration management systems with the service management database to dynamically reconcile live endpoint baseline scans against authorized emergency change requests.
Integrating automated configuration monitoring tools with the service management database (CMDB) bridges the gap between technical drift detection and administrative change management. When an emergency hotfix alters a server baseline, the configuration management tool checks the CMDB for a corresponding approved emergency change ticket. If a valid ticket exists, the baseline variation is recognized as authorized drift; if no ticket exists, it is treated as unauthorized configuration drift requiring remediation.

Adım Adım Çözüm

1
Analyze the operational problem
Identify that the core issue is an inability to correlate live configuration drift with legitimate emergency change documentation.
Security operations need continuous automated verification without breaking emergency change management workflows.
2
Evaluate patch and configuration management governance
Determine that linking configuration assessment tools with formal IT service management (ITSM/CMDB) tracking enables real-time verification of baseline exceptions.
Automated reconciliation ensures unauthorized drift is highlighted for remediation while authorized emergency hotfixes are automatically reconciled against open change tickets.
3
Differentiate governance roles and control functions
Reject responses that misclassify control categories (detective vs. preventive), misapply network mitigations to system states, or break role separation.
Maintaining proper security control classification and role boundaries is critical for enterprise security posture.

Anahtar Kavram

Configuration Drift and Automated Baseline Reconciliation
Soru 13Soru →

An enterprise security policy requires that any unauthorized changes to server system configurations are automatically detected and restored to a pre-approved security state. Which of the following operational controls best meets this requirement?

Cevabı ve açıklamayı göster

Cevap: Automated configuration management baseline enforcement

Cevap

Automated configuration management baseline enforcement
Automated configuration management baseline enforcement continuously compares system settings against an established baseline and automatically remediates configuration drift by restoring approved settings.

Adım Adım Çözüm

1
Identify the core requirement in the scenario.
The scenario requires automatic detection and restoration of unauthorized system configuration changes (configuration drift).
Security baselines define approved operational settings, and automated tools enforce compliance against these baselines continuously.
2
Evaluate the technical capabilities of available operational controls.
Automated configuration management tools actively monitor settings and enforce baselines, reverting unauthorized drift automatically without manual intervention.
Other control options act as detective logging mechanisms or network filters rather than internal system configuration enforcement tools.

Anahtar Kavram

Configuration Drift and Automated Baseline Enforcement
Soru 14Soru →

A security administrator is establishing standard operating procedures for system maintenance across enterprise servers. Which of the following actions should be performed prior to deploying software patches to live production servers? (Select TWO)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Test updates in a non-production staging environment to verify system stability and software compatibility; Submit proposed updates for formal review and authorization through the change management process

Cevap

Testing updates in a non-production staging environment and submitting proposed updates through formal change management review.
A sound patch management policy requires testing software updates in a non-production staging environment to confirm system stability and software compatibility prior to live deployment. Additionally, submitting the proposed changes through a formal change management process ensures administrative oversight, scheduled maintenance windows, and verified rollback plans.

Adım Adım Çözüm

1
Analyze the patch management lifecycle requirements prior to production deployment.
Identified the need for technical verification and administrative risk governance.
Pre-deployment validation reduces the risk of operational disruption.
2
Evaluate technical pre-deployment procedures.
Staging environment testing verifies functional compatibility without risking live services.
Staging reflects production conditions while isolating potential patch defects.
3
Evaluate administrative governance controls.
Formal change management authorization provides proper approval, scheduling, and rollback planning.
Change control ensures organizational awareness and structured risk management.

Anahtar Kavram

Patch Management and Change Control Lifecycle
Soru 15Soru →

A security technician is documenting the standard patch deployment workflow for enterprise operating systems. Place the following stages of the patch management lifecycle in the correct order from first to last.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence for the patch management lifecycle is: 1. Identify and assess newly released vendor patches -> 2. Test the patch in a staging environment -> 3. Submit the patch deployment plan to the Change Advisory Board (CAB) -> 4. Deploy the patch to production systems -> 5. Perform post-installation auditing.
The standard patch management process follows a structured lifecycle: identification of updates, non-production testing, change management authorization, controlled production deployment, and post-deployment validation auditing.

Adım Adım Çözüm

1
Identify available patches
Discovers vendor updates requiring evaluation.
Security operations must monitor vendor advisories and assess patch severity before taking operational action.
2
Perform staging and testing
Confirms patch compatibility without affecting live systems.
Testing ensures updates do not cause system crashes or application conflicts.
3
Request change authorization
Obtains formal CAB review and approval.
Change management governance mandates documentation and risk review prior to production modification.
4
Execute production deployment
Installs patches on production assets.
Deployment must occur during scheduled maintenance windows to minimize business impact.
5
Conduct post-patch verification and auditing
Confirms compliance and closure of vulnerability.
Auditing verifies that installation succeeded and configuration baselines remain secure.

Anahtar Kavram

Standard Patch Management Lifecycle Workflow
Soru 16Soru →

A security engineer at a financial institution is establishing a patch and configuration management framework for dual-homed payment processing nodes. The environment requires continuous compliance enforcement against baseline images, strict change validation before production deployment, and protection against unauthorized system modifications. Which of the following strategies should the security engineer implement to maintain secure configuration baselines and control patch deployment risks? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Utilize automated infrastructure-as-code configuration management tools to continuously audit system state and automatically remediate configuration drift back to approved baselines.; Staging patch updates in an isolated test environment and verifying cryptographic signature hashes prior to deploying updates into production.

Cevap

The security engineer should utilize automated infrastructure-as-code tools to continuously audit and remediate configuration drift, and stage patch updates in an isolated environment while verifying cryptographic signature hashes before production deployment.
Automated infrastructure-as-code tools continuously validate system settings against established security baselines and automatically remediate configuration drift. Additionally, staging patches in an isolated environment combined with verifying cryptographic signatures prevents unstable or malicious update packages from compromising production systems.

Adım Adım Çözüm

1
Analyze configuration maintenance requirements
Identified the need for continuous drift detection and enforcement using automated configuration baselines.
Manual baseline auditing is ineffective in dynamic environments, making automated remediation via configuration management essential for eliminating drift.
2
Evaluate patch deployment risk mitigation controls
Selected pre-deployment staging and cryptographic hash verification.
Testing patches in staging prevents unexpected service outages, and verifying signature hashes guarantees patch integrity against tampering.
3
Assess distractor validity
Rejected using firewalls as permanent patch replacements and misclassifying control categories.
Firewalls do not remediate system code flaws, and mislabeling control types invalidates risk governance modeling.

Anahtar Kavram

Continuous baseline configuration enforcement and staged patch verification
Soru 17Soru →

A system administrator updates a cluster of web servers with an emergency software patch. Immediately after the update, users report that web applications hosted on those servers are failing to load. Which of the following actions should the administrator take FIRST to restore system functionality?

Cevabı ve açıklamayı göster

Cevap: Execute the documented rollback plan to revert the servers to their known good baseline configuration.

Cevap

Execute the documented rollback plan to revert the servers to their known good baseline configuration.
When a patch causes unexpected service outage or instability in production, the immediate action within configuration management is to execute a tested rollback plan to restore services to the last known good baseline.

Adım Adım Çözüm

1
Identify the immediate operational impact following the patch deployment.
The newly applied patch caused application instability and service disruption.
When a patch causes system failure, immediate operational recovery is required.
2
Initiate the emergency rollback procedures associated with the patch deployment plan.
The servers revert to the previously verified baseline state.
Rollback plans ensure rapid recovery to a stable configuration minimalizing downtime.

Anahtar Kavram

Rollback Planning and Configuration Baselines
Soru 18Soru →

A security administrator needs to ensure that all newly deployed enterprise servers strictly adhere to a standardized, hardened set of initial operational settings prior to production release. Which of the following should the administrator implement to establish these standardized settings?

Cevabı ve açıklamayı göster

Cevap: A security configuration baseline profile

Cevap

The administrator should implement a security configuration baseline profile, which establishes standardized, pre-approved hardening settings for newly deployed systems.
A configuration baseline profile defines a mandatory minimum standard for operating systems and applications, ensuring consistent hardening across all deployed assets.

Adım Adım Çözüm

1
Identify the goal in the scenario
The requirement is to define standard, hardened security settings across all newly deployed systems.
The system lifecycle requires consistent initial configurations to prevent security weaknesses before systems enter production.
2
Evaluate potential configuration management tools
A security configuration baseline defines the standard minimum security setup (e.g., CIS benchmarks, DISA STIGs) for systems.
Baselines ensure uniformity, simplify drift monitoring, and minimize misconfigurations.

Anahtar Kavram

Security Baselines and Configuration Management
Soru 19Soru →

A security analyst is implementing an out-of-band security patch for a critical database cluster following the discovery of an actively exploited zero-day vulnerability. Arrange the following steps of the emergency patch management process in the correct sequential order from first to last.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence for emergency patch deployment is: 1) Validate patch authenticity and execute sandbox testing in staging, 2) Submit an Emergency Change Request with a rollback plan, 3) Deploy the patch to the production database cluster, 4) Perform post-implementation vulnerability scanning and health checks, and 5) Update the CMDB and system security baseline image.
The standard emergency patch management lifecycle follows a strict sequence to balance urgent vulnerability mitigation with operational risk management. First, validating and testing the patch in an isolated sandbox ensures it does not destabilize the software ecosystem. Second, submitting an Emergency Change Request (ECR) with a rollback strategy maintains change control governance. Third, the patch is deployed to production systems once approved. Fourth, post-implementation vulnerability scans and service health checks confirm the flaw is resolved without side effects. Finally, updating the CMDB records and baseline images preserves configuration integrity and prevents drift during future node provisioning.

Adım Adım Çözüm

1
Perform initial pre-deployment testing and signature verification in a non-production environment.
The patch is verified as genuine and free from breaking application dependencies.
Applying unverified patches directly to production risks outage or malware injection.
2
Obtain formal emergency authorization via Emergency Change Advisory Board (ECAB).
Authorized emergency change ticket with mandatory fallback/rollback procedures established.
Change control governance prevents unauthorized alterations and ensures back-out plans exist.
3
Execute the patch deployment across production nodes.
Production servers receive and install the patch binaries.
Implementation executes the authorized changes on live production systems.
4
Conduct post-deployment validation scans and monitoring.
Confirmation that the target flaw is remediated and no regression issues exist.
Integrity checks confirm successful threat mitigation before closing the incident ticket.
5
Reconcile configuration management records and baseline artifacts.
CMDB and golden image templates reflect the new version compliance standard.
Updating baselines prevents future automated provisioning from reverting systems to an unpatched state.

Anahtar Kavram

Emergency Patch and Configuration Management Lifecycle
Soru 20Soru →

A system administrator is preparing to roll out a critical operating system patch across enterprise workstations. Which of the following tasks should be completed prior to deploying the patch into the broad production environment? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Test the patch in an isolated staging environment to verify system stability and application compatibility.; Establish a rollback plan and back up system configurations to ensure rapid recovery if the update fails.

Cevap

Testing the patch in an isolated staging environment to verify system stability and establishing a rollback plan with backups prior to deployment.
Prior to deploying software updates across production environments, best practices require validating patch stability in a non-production staging environment and creating backups with a documented rollback plan to recover quickly if issues arise.

Adım Adım Çözüm

1
Identify pre-deployment requirements in the patch management lifecycle.
Recognize that changes must be tested in a controlled staging environment before production release.
Testing mitigates the risk of unforeseen software incompatibilities or system crashes.
2
Determine risk mitigation procedures for patch deployment failures.
Establish backups and a clear rollback plan.
System snapshots and backups enable quick restoration if a patch introduces severe operational disruptions.

Anahtar Kavram

Pre-deployment Patch Staging and Rollback Planning
Sayfa 1 / 3Sonraki