{"id":19089,"date":"2026-09-22T11:34:05","date_gmt":"2026-09-22T11:34:05","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=19089"},"modified":"2026-09-22T11:34:05","modified_gmt":"2026-09-22T11:34:05","slug":"isc-cissp-issap-practice-test-questions-and-exam-dumps-part17-q321-340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/isc-cissp-issap-practice-test-questions-and-exam-dumps-part17-q321-340\/","title":{"rendered":"ISC CISSP-ISSAP Practice Test Questions and Exam Dumps Part17 Q321-340"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/cissp-issap-exam-dumps\"><b>ISC CISSP-ISSAP Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<p><b>Question 321.<\/b><\/p>\n<p><b>A security architect is reviewing a design that allows administrators to approve their own high-risk production changes. What is the BEST corrective action?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Increase administrator privileges<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Introduce independent approval through separation of duties<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disable change logging<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Allow emergency changes without review<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Introduce independent approval through separation of duties<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Separation of duties reduces the risk that one individual can initiate and approve a sensitive action without oversight. High-risk production changes should normally involve independent review or approval, especially when they affect critical security controls. This approach helps reduce fraud, mistakes, and misuse of privilege. Logging should remain enabled so the organization can verify who requested, approved, and implemented each change.<\/span><\/p>\n<p><b>Question 322.<\/b><\/p>\n<p><b>A security architect is assessing a new internet-facing application. Which activity should occur FIRST?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Identify assets, trust boundaries, threats, and security requirements<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Purchase the firewall appliance<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Configure production user accounts<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Perform post-deployment penetration testing<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. Identify assets, trust boundaries, threats, and security requirements<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Architecture should begin with understanding what needs protection and why. Identifying assets, data flows, trust boundaries, threats, business requirements, and risk helps determine the necessary security controls. Selecting technology before defining these requirements may result in gaps or unnecessary complexity. Penetration testing is valuable later, but it does not replace design-time security analysis.<\/span><\/p>\n<p><b>Question 323.<\/b><\/p>\n<p><b>A critical application relies on one centralized secrets-management platform. What should the architect evaluate MOST carefully?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> The appearance of the secrets-management console<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> The number of application developers<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Resilience, administrative protection, and recovery of the secrets platform<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> The length of secret names<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Resilience, administrative protection, and recovery of the secrets platform<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A centralized secrets platform may become a critical dependency for many applications. An outage can prevent workloads from accessing credentials, while compromise may expose sensitive secrets across the enterprise. The architecture should therefore address redundancy, access control, auditing, backup, recovery, and privileged administration. Critical shared services require strong protection against both availability failures and security compromise.<\/span><\/p>\n<p><b>Question 324.<\/b><\/p>\n<p><b>A service must deny unauthorized access even when its policy database is unavailable. Which design principle is MOST applicable?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Default allow<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Shared authentication<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Open access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Fail-secure behavior**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Fail-secure behavior<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Fail-secure design ensures that a security-control failure does not automatically grant access. If the policy database cannot be reached, the system should move toward a protected state, especially for sensitive operations. Some low-risk functions may use carefully controlled cached policy if explicitly designed, but the default should not become unrestricted access. This approach reflects fail-safe security principles.<\/span><\/p>\n<p><b>Question 325.<\/b><\/p>\n<p><b>What is the MAIN security benefit of separating application tiers into different network zones?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> It limits unnecessary communication and reduces lateral movement<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> It eliminates authentication requirements<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> It guarantees confidentiality automatically<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> It removes the need for host security controls<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. It limits unnecessary communication and reduces lateral movement<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Segmentation allows the architect to enforce which systems may communicate and through which protocols. If one tier is compromised, properly configured boundaries can limit the attacker\u2019s ability to move to application, database, or administrative systems. Segmentation should be combined with identity, authorization, endpoint security, and monitoring. It is an important defense-in-depth control rather than a complete security solution by itself.<\/span><\/p>\n<p><b>Question 326.<\/b><\/p>\n<p><b>A company wants to use certificates for service-to-service authentication. Which capability is MOST important for long-term reliability?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Manually tracking certificates in spreadsheets<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Automated certificate issuance, renewal, revocation, and inventory management<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Using certificates with no expiration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Sharing private keys between services<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Automated certificate issuance, renewal, revocation, and inventory management<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Large-scale certificate use requires effective lifecycle management. Automated issuance and renewal reduce outage risk, while inventory and revocation capabilities help respond to compromise and retirement. Private keys should remain protected and should not be shared unnecessarily. Certificates with unlimited validity would increase exposure and make lifecycle governance more difficult.<\/span><\/p>\n<p><b>Question 327.<\/b><\/p>\n<p><b>A security architect wants to ensure that a compromised build server cannot immediately deploy malicious software to production. Which design is BEST?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Give the build server unrestricted production administrator access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Store deployment credentials in build scripts<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Separate build, signing, approval, and deployment privileges<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Disable deployment logs<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Separate build, signing, approval, and deployment privileges<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Separating responsibilities creates multiple control points in the software-delivery process. Compromise of the build server should not automatically provide signing authority or production deployment capability. Independent approvals, protected signing keys, artifact integrity verification, and controlled deployment reduce supply-chain risk. This is an application of defense in depth and separation of duties.<\/span><\/p>\n<p><b>Question 328.<\/b><\/p>\n<p><b>An enterprise has redundant data centers, but both depend on the same power utility substation. What architectural issue exists?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Too many backup systems<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Excessive encryption<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Too much network segmentation<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> A common-mode failure risk**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. A common-mode failure risk<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Redundancy is effective only when supposedly independent components do not share critical failure points. Two data centers that rely on the same power infrastructure may fail simultaneously during a utility disruption. Architects should identify shared power, network, DNS, identity, storage, and provider dependencies when evaluating resilience. Hidden common dependencies can undermine otherwise strong recovery designs.<\/span><\/p>\n<p><b>Question 329.<\/b><\/p>\n<p><b>Why should privileged service accounts be reviewed periodically?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> To confirm that permissions still reflect current business and technical requirements<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> To ensure privileges always increase over time<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> To eliminate logging<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> To make credentials permanent<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. To confirm that permissions still reflect current business and technical requirements<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Service accounts can accumulate unnecessary permissions as applications evolve. Periodic review helps ensure that access remains aligned with current requirements and that obsolete privileges are removed. This supports least privilege and reduces the potential impact of credential compromise. The review should also consider account ownership, credential rotation, usage, and whether the account is still required.<\/span><\/p>\n<p><b>Question 330.<\/b><\/p>\n<p><b>A security architect is designing an external partner portal. What should be MOST important when defining federation access?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Allowing every partner the same permissions<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Mapping trusted identity claims to narrowly scoped authorization<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disabling assertion validation<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Trusting all requests from partner networks<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Mapping trusted identity claims to narrowly scoped authorization<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Federation proves or communicates identity attributes, but authorization still determines what the partner may access. Trusted claims should be validated and mapped to the minimum permissions required for the partner&#8217;s role. Network origin alone should not imply trust. The architecture should also define assurance levels, key or certificate management, logging, and procedures for terminating the federation relationship.<\/span><\/p>\n<p><b>Question 331.<\/b><\/p>\n<p><b>An application receives signed software updates from a vendor. What should the application verify before installation?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Only the file name<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Only the download size<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Signature validity, trusted signer, and package integrity<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> The vendor&#8217;s marketing website<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Signature validity, trusted signer, and package integrity<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Signed updates are useful only if the system verifies the signature against a trusted signer and confirms package integrity. This helps detect tampering and unauthorized packages. The architecture should also address trusted-key distribution, certificate or key revocation, and secure update transport. File names and sizes do not provide meaningful assurance that software is legitimate.<\/span><\/p>\n<p><b>Question 332.<\/b><\/p>\n<p><b>A system must restore service within 45 minutes after a disaster. Which metric defines this requirement?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Recovery point objective<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Mean time between failures<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Data-retention period<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Recovery time objective**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Recovery time objective<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">RTO defines how quickly a service must be restored after disruption. A 45-minute target therefore represents the recovery time objective. RPO addresses the amount of data loss the business can tolerate. Architects use both metrics to determine suitable standby capacity, replication, backup, automation, and recovery procedures.<\/span><\/p>\n<p><b>Question 333.<\/b><\/p>\n<p><b>What is the MAIN security reason for restricting direct database access by end users?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> It allows application-layer controls to mediate and limit data operations<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> It guarantees database availability<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> It eliminates encryption requirements<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> It prevents all application vulnerabilities<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. It allows application-layer controls to mediate and limit data operations<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Applications can enforce business logic, validation, authorization, and logging before requests reach sensitive databases. Broad direct access may bypass those controls and expose data or administrative functions unnecessarily. Database permissions should also be scoped according to least privilege. Restricting direct access reduces attack surface and helps preserve separation between user interaction and backend data management.<\/span><\/p>\n<p><b>Question 334.<\/b><\/p>\n<p><b>A third-party provider processes sensitive customer information. Which contractual requirement is MOST important for incident response?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> The provider&#8217;s branding guidelines<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Defined security-incident notification obligations and timelines<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> The number of provider employees<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> The location of the provider&#8217;s sales team<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Defined security-incident notification obligations and timelines<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The organization needs timely information when a provider experiences a security incident that may affect its data or services. Contracts should define what constitutes a reportable incident, how quickly notification must occur, required information, cooperation expectations, and responsibilities during investigation and recovery. Without explicit terms, delays or ambiguity can impair the organization&#8217;s own response obligations.<\/span><\/p>\n<p><b>Question 335.<\/b><\/p>\n<p><b>A security architect discovers that a legacy system stores passwords using obsolete cryptographic protection. What should be done FIRST?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Ignore the issue because the system is legacy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Disable all monitoring<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Assess the exposure and define remediation or compensating controls<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Publish the passwords for easier recovery<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Assess the exposure and define remediation or compensating controls<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Legacy weaknesses should be addressed through documented risk analysis. The architect should understand the sensitivity of the accounts, exposure of the credential store, available upgrade options, and compensating controls such as stronger upstream authentication, network isolation, or restricted access. A modernization or replacement plan may be required if residual risk remains unacceptable.<\/span><\/p>\n<p><b>Question 336.<\/b><\/p>\n<p><b>A security architect is designing local authorization caching for a distributed application. What is the MOST important security concern?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Cache files may use disk space<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> The application may start more quickly<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Users may prefer cached access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Cached permissions may remain valid after access has been revoked**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Cached permissions may remain valid after access has been revoked<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Authorization caching improves resilience and performance, but stale policy can create security risk. If a user&#8217;s access is revoked centrally, a distributed service may continue honoring an old cached decision. The architecture should define cache lifetime, invalidation behavior, high-risk operations that require current authorization, and fail-secure behavior when the central service is unavailable.<\/span><\/p>\n<p><b>Question 337.<\/b><\/p>\n<p><b>Why is it important to identify dependencies on DNS, identity, and certificate services during architecture design?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Failure of shared services can disrupt otherwise healthy applications<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Shared services should never be used<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> These services eliminate the need for recovery planning<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Applications cannot operate with centralized services<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. Failure of shared services can disrupt otherwise healthy applications<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Applications often depend on shared infrastructure that is not obvious from the primary application diagram. DNS, identity, certificate validation, key management, and networking can all become critical points of failure. Identifying these dependencies helps architects evaluate concentration risk, redundancy, recovery requirements, and cascading impact. Resilience planning should encompass supporting services as well as application servers.<\/span><\/p>\n<p><b>Question 338.<\/b><\/p>\n<p><b>A company wants to prevent unmanaged endpoints from accessing a sensitive application even when the user&#8217;s password is correct. Which approach is BEST?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Trust all internal IP addresses<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Combine user authentication with device posture or device identity requirements<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disable endpoint security checks<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Allow access from any browser<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Combine user authentication with device posture or device identity requirements<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">User identity alone may not provide enough assurance for highly sensitive applications. Device posture or device identity can confirm that the endpoint is managed, patched, encrypted, or otherwise compliant. Combining these signals supports contextual access control and Zero Trust principles. Network location should not be treated as sufficient proof that an endpoint is trustworthy.<\/span><\/p>\n<p><b>Question 339.<\/b><\/p>\n<p><b>A security architecture exception has remained open for several years without reassessment. What is the MAIN governance concern?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> The documentation may be too detailed<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> The exception may generate too many reports<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> The original risk assumptions and compensating controls may no longer be valid<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> The system may have too many owners<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. The original risk assumptions and compensating controls may no longer be valid<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Exceptions should be temporary or periodically reassessed. Business use, threats, technology, and available remediation options change over time. A risk that was once acceptable may no longer be tolerable, and compensating controls may have degraded. Effective governance assigns ownership and review dates so exceptions do not silently become permanent architectural weaknesses.<\/span><\/p>\n<p><b>Question 340.<\/b><\/p>\n<p><b>Which practice BEST demonstrates mature enterprise security architecture management?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Treat architecture as a one-time project deliverable<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Allow each business unit to ignore enterprise standards<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Maintain undocumented exceptions indefinitely<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Continuously govern architecture decisions, risks, dependencies, standards, and exceptions**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Continuously govern architecture decisions, risks, dependencies, standards, and exceptions<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Mature security architecture is an ongoing enterprise discipline. Architecture decisions should be documented, standards maintained, exceptions governed, dependencies understood, and risks periodically reassessed. Business requirements, threats, technologies, and regulations change, so static architecture can become obsolete. Continuous governance keeps security controls aligned with current organizational needs and risk tolerance.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ISC CISSP-ISSAP Exam Dumps and Practice Test Dumps &nbsp; Question 321. A security architect is reviewing a design that allows administrators to approve their own high-risk production changes. What is the BEST corrective action? Increase administrator privileges 2. Introduce independent approval through separation of duties 3. Disable change logging 4. Allow emergency changes [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19089"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=19089"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19089\/revisions"}],"predecessor-version":[{"id":19090,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19089\/revisions\/19090"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=19089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=19089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=19089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}