You save $69.98
The organization implemented the response to this scenario: A plant's programmable controller cannot be restarted safely during production, but IT schedules an automatic firmware update. The approved response was: Use safety-engineered maintenance planning and segmented compensating controls with approved vendor procedures. Which statement MOST accurately identifies a remaining risk or constraint?
OT availability and human safety constraints change acceptable patch methods and timing. A dry-run change plan demonstrates safe state, rollback and approved maintenance window.
Even segregated OT systems need monitoring, controlled access and tested safe shutdown.
Patching priorities must account for industrial hazard and safe maintenance constraints.
Safety-engineered procedures need rehearsed failure handling and vendor compatibility checks.
Management implemented a response after this event: A plant's programmable controller cannot be restarted safely during production, but IT schedules an automatic firmware update. The response was: Use safety-engineered maintenance planning and segmented compensating controls with approved vendor procedures. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
A dry-run change plan demonstrates safe state, rollback and approved maintenance window. OT availability and human safety constraints change acceptable patch methods and timing.
Administrative success is not a safe operational outcome.
A version number alone cannot substantiate process-safe patching.
Segmentation cannot prove plant safety during a critical failure.
An IaaS tenant assumes the cloud provider automatically patches its custom guest OS and application packages. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Shared responsibility differs by service model; IaaS tenants retain control of hosted software. The provider's assurance report does not prove customer workload hardening or IAM configuration.
Infrastructure service agreements do not automatically include customer OS and application maintenance.
Provider controls do not attest the configuration of tenant-installed workload software.
Host patching cannot remove customer guest software vulnerabilities.
The organization implemented the response to this scenario: An IaaS tenant assumes the cloud provider automatically patches its custom guest OS and application packages. The approved response was: Assign guest OS and workload patching to the tenant while verifying provider infrastructure responsibility. Which statement MOST accurately identifies a remaining risk or constraint?
Shared responsibility differs by service model; IaaS tenants retain control of hosted software. A signed responsibility matrix and patch audit show guest vulnerabilities are owned and remediated.
Customer IAM and guest operating systems remain distinct responsibility boundaries.
Virtualization does not automatically turn customer-managed IaaS guests into managed SaaS software.
Availability of the underlying service is not an assurance of workload hardening.
Management implemented a response after this event: An IaaS tenant assumes the cloud provider automatically patches its custom guest OS and application packages. The response was: Assign guest OS and workload patching to the tenant while verifying provider infrastructure responsibility. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
A signed responsibility matrix and patch audit show guest vulnerabilities are owned and remediated. Shared responsibility differs by service model; IaaS tenants retain control of hosted software.
Provider availability does not demonstrate customer maintenance.
Supplier evidence does not substitute for tenant-side assurance.
Host patch levels cannot verify remediation inside the customer environment.
Field devices accept arbitrary firmware downloaded over HTTPS because transport encryption is mistaken for publisher trust. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Transport security protects delivery but does not prove firmware image publisher authenticity. Compromised signing keys can authorize malicious updates, so revocation and recovery matter.
TLS protects the delivery connection but does not bind the firmware bytes to an authorized signing authority.
A same-source unsigned checksum can be replaced alongside a malicious firmware image.
Signature authenticity alone does not prevent replay of outdated unsafe releases.
The organization implemented the response to this scenario: Field devices accept arbitrary firmware downloaded over HTTPS because transport encryption is mistaken for publisher trust. The approved response was: Require authenticated signed firmware, anti-rollback policy and verified update authorization. Which statement MOST accurately identifies a remaining risk or constraint?
Transport security protects delivery but does not prove firmware image publisher authenticity. Tampered or downgraded firmware is rejected while current approved images install.
Compromised authorized keys require revocation, replacement and recovery processes.
Network encryption cannot enforce monotonic version or anti-rollback policy.
Server authentication is distinct from authenticated software release provenance.
Management implemented a response after this event: Field devices accept arbitrary firmware downloaded over HTTPS because transport encryption is mistaken for publisher trust. The response was: Require authenticated signed firmware, anti-rollback policy and verified update authorization. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
Tampered or downgraded firmware is rejected while current approved images install. Transport security protects delivery but does not prove firmware image publisher authenticity.
Transport encryption is not publisher-authenticated firmware verification.
A successful happy-path update does not demonstrate anti-rollback enforcement.
Confidential delivery alone does not verify trusted release identity.
A storage team proposes RSA encryption of every byte of multi-terabyte backups for performance and key management. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Symmetric cryptography efficiently handles large data; asymmetric operations are suited to limited-size key exchange/signatures. Nonce reuse or exposed data keys can defeat otherwise strong encryption algorithms.
Asymmetric encryption is unsuitable for efficient authenticated bulk-data processing.
A checksum lacks confidentiality and an attacker can replace both data and unprotected checksum.
Nonce reuse can destroy confidentiality or integrity guarantees of common AEAD designs.
The organization implemented the response to this scenario: A storage team proposes RSA encryption of every byte of multi-terabyte backups for performance and key management. The approved response was: Use suitable symmetric authenticated bulk encryption and protect small data keys with an authorized key-management mechanism. Which statement MOST accurately identifies a remaining risk or constraint?
Symmetric cryptography efficiently handles large data; asymmetric operations are suited to limited-size key exchange/signatures. Large backups encrypt and decrypt efficiently and altered ciphertext is detected.
Encryption does not survive loss of secrecy for effective decrypt keys.
Some AEAD schemes have critical security failures under nonce reuse.
Key lifecycle and access control determine who can decrypt the bulk ciphertext.
Management implemented a response after this event: A storage team proposes RSA encryption of every byte of multi-terabyte backups for performance and key management. The response was: Use suitable symmetric authenticated bulk encryption and protect small data keys with an authorized key-management mechanism. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
Large backups encrypt and decrypt efficiently and altered ciphertext is detected. Symmetric cryptography efficiently handles large data; asymmetric operations are suited to limited-size key exchange/signatures.
Performance alone is not authenticated confidentiality and alteration detection.
Encrypted backup bytes do not demonstrate protected key custody.
Compression statistics cannot establish correct cryptographic operation or recoverability.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (484 Questions, Last Updated on Oct 31, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
