{"id":19083,"date":"2026-09-22T11:33:16","date_gmt":"2026-09-22T11:33:16","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=19083"},"modified":"2026-09-22T11:33:16","modified_gmt":"2026-09-22T11:33:16","slug":"isc-cissp-issap-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/isc-cissp-issap-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"ISC CISSP-ISSAP Practice Test Questions and Exam Dumps Part14 Q261-280"},"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 261.<\/b><\/p>\n<p><b>A security architect is designing a privileged-access model for cloud administrators. Which control provides the STRONGEST reduction in standing privilege?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Permanent administrator roles assigned to all cloud engineers<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Just-in-time privileged access with approval and expiration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Shared administrator accounts<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Passwords stored in team documentation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Just-in-time privileged access with approval and expiration<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Just-in-time access reduces standing privilege by granting elevated permissions only when they are required and removing them automatically after a defined period. Approval, strong authentication, and session logging can further strengthen the process. Permanent privileged roles increase exposure because powerful permissions remain available even when they are not needed. Shared accounts also weaken accountability and make it harder to attribute administrative activity to a specific individual.<\/span><\/p>\n<p><b>Question 262.<\/b><\/p>\n<p><b>Which architectural principle BEST supports evaluating every request based on current identity and policy rather than trusting a prior network location?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Continuous verification<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Open design<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Data minimization<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Maximum availability<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. Continuous verification<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Continuous verification is a key concept in modern Zero Trust architectures. It assumes that network location alone should not establish ongoing trust. Access decisions should consider current identity assurance, device posture, session context, resource sensitivity, and other relevant factors. This reduces the risk that an attacker who gains access to an internal network automatically inherits broad trust. The approach complements least privilege and explicit authorization.<\/span><\/p>\n<p><b>Question 263.<\/b><\/p>\n<p><b>A security architect is reviewing an application that stores encryption keys in the same database as encrypted records. What is the MAIN concern?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> The database may require more storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> The keys may expire too quickly<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Compromise of the database may expose both ciphertext and the keys needed to decrypt it<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Encryption may slow application performance<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Compromise of the database may expose both ciphertext and the keys needed to decrypt it<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Encryption provides limited protection if the encrypted data and its decryption keys are protected by the same trust boundary and access controls. An attacker who compromises that database may obtain both. Keys should normally be separated and protected through a dedicated key-management mechanism or hardware-backed service. Access, rotation, revocation, backup, and recovery should also be addressed throughout the key lifecycle.<\/span><\/p>\n<p><b>Question 264.<\/b><\/p>\n<p><b>An enterprise application requires communication with a third-party service over the internet. Which design BEST protects the connection?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Send sensitive data in plaintext because the provider is trusted<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Rely only on IP address filtering<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disable server authentication to improve availability<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Use authenticated encrypted transport and validate the remote service identity**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Use authenticated encrypted transport and validate the remote service identity<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Traffic crossing an untrusted network should be protected against interception, modification, and impersonation. Authenticated encryption can provide confidentiality and integrity, while certificate or equivalent identity validation helps ensure the application is communicating with the intended third party. Network filtering can be an additional control, but it does not replace cryptographic protection or strong endpoint authentication.<\/span><\/p>\n<p><b>Question 265.<\/b><\/p>\n<p><b>What is the PRIMARY purpose of an architecture security review before implementation?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Identify design-level risks while they are still easier and less costly to correct<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Replace all later security testing<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Guarantee the system will have no vulnerabilities<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Approve every requested exception automatically<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. Identify design-level risks while they are still easier and less costly to correct<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Architecture reviews provide an opportunity to identify trust issues, missing controls, resilience weaknesses, data-protection gaps, and risky dependencies before implementation decisions become difficult to change. They complement, rather than replace, later activities such as code review, vulnerability assessment, and penetration testing. Early identification can reduce remediation cost and improve alignment between business requirements and security controls.<\/span><\/p>\n<p><b>Question 266.<\/b><\/p>\n<p><b>An organization is designing a service that must tolerate the loss of one encryption-key-management node. Which approach is MOST appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Store all keys in plaintext as a backup<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Use secure redundant key-management components with protected replication and tested failover<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disable encryption during outages<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Keep only one key server and increase its CPU capacity<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Use secure redundant key-management components with protected replication and tested failover<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Key-management infrastructure can become a critical dependency for encryption, signing, and authentication services. Redundancy can improve availability, but replication and failover must preserve the confidentiality and integrity of key material. Plaintext backup or disabling encryption would introduce unacceptable security risk. The architecture should combine strong protection of keys with tested resilience mechanisms.<\/span><\/p>\n<p><b>Question 267.<\/b><\/p>\n<p><b>A security architect discovers that different business units independently manage privileged accounts with inconsistent controls. What is the BEST architectural response?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Allow each team to continue without common standards<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Disable auditing to reduce complexity<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Establish enterprise privileged-access standards and centralized governance where practical<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Require all administrators to share one account<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Establish enterprise privileged-access standards and centralized governance where practical<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Inconsistent privileged-access practices can create uneven security and make enterprise risk difficult to manage. Common standards for authentication, approval, session control, credential storage, logging, and account lifecycle improve consistency. Centralized governance does not necessarily require one technical platform, but it should establish clear expectations and accountability across business units. Shared accounts would reduce traceability and should generally be avoided.<\/span><\/p>\n<p><b>Question 268.<\/b><\/p>\n<p><b>A security architect is designing an application that must continue processing low-risk requests when the central identity service is unavailable. What should be defined?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> A blanket rule allowing every request<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> A permanent bypass of authentication<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> An anonymous administrator account<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Explicit degraded-mode behavior with clearly limited permissions and duration**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Explicit degraded-mode behavior with clearly limited permissions and duration<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">If business requirements justify continued operation during an identity-service outage, degraded-mode behavior should be explicitly designed rather than improvised. The architect should define which low-risk operations remain available, what cached identity or authorization data may be used, how long it remains valid, and which sensitive functions must stop. This balances availability with security and prevents an outage from turning into broad unauthorized access.<\/span><\/p>\n<p><b>Question 269.<\/b><\/p>\n<p><b>Which design BEST limits the impact of compromise of a software build server?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Separate build, signing, and production deployment privileges and protect the pipeline with strong controls<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Allow the build server unrestricted production administrator access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Store all signing keys on the build server in plaintext<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Disable pipeline logging<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. Separate build, signing, and production deployment privileges and protect the pipeline with strong controls<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A build server is a high-value software-supply-chain target. Separating responsibilities reduces the chance that compromise of one component automatically enables malicious code to be signed and deployed. Signing keys should be strongly protected, production deployment should require controlled authorization, and pipeline activity should be logged. Defense in depth within the delivery process helps limit the impact of any single compromise.<\/span><\/p>\n<p><b>Question 270.<\/b><\/p>\n<p><b>An application stores sensitive session tokens in browser-accessible storage even though client-side scripts do not require them. What security principle suggests a safer design?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Maximum privilege<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Minimize exposure of sensitive data and credentials<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Default allow<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> High availability only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Minimize exposure of sensitive data and credentials<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Sensitive credentials and tokens should be exposed only to the components that legitimately require them. If client-side scripts do not need access, the architecture should use mechanisms that reduce script exposure and lower the risk from client-side compromise. This reflects data minimization and least-exposure principles. The exact implementation depends on the application model and threat environment.<\/span><\/p>\n<p><b>Question 271.<\/b><\/p>\n<p><b>A security architect is reviewing a proposed active-active architecture across two sites. What should be verified MOST carefully?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Both sites use identical server colors<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Every administrator prefers the same interface<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> The sites do not share hidden dependencies that could fail simultaneously<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Both sites have the same number of user accounts<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. The sites do not share hidden dependencies that could fail simultaneously<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Two sites may appear independent yet depend on the same carrier, DNS service, identity provider, storage platform, certificate infrastructure, or cloud control plane. These common dependencies can defeat an active-active design during a major failure. Architects should map shared dependencies and test failover scenarios to confirm that redundancy actually provides the resilience required by the business.<\/span><\/p>\n<p><b>Question 272.<\/b><\/p>\n<p><b>A business wants to verify that a partner&#8217;s security posture remains acceptable after onboarding. Which governance approach is BEST?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Perform due diligence only before the contract begins<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Assume contractual language guarantees continuous compliance<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Stop monitoring after the first successful audit<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Use ongoing assurance, reporting, and periodic reassessment throughout the relationship**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Use ongoing assurance, reporting, and periodic reassessment throughout the relationship<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Third-party risk changes over time as providers alter technology, personnel, subcontractors, and operational practices. Initial due diligence is important but insufficient for long-term assurance. Contracts should support ongoing reporting and assessment rights, while the organization periodically reviews whether controls continue to meet requirements. Significant incidents or changes should also trigger reassessment.<\/span><\/p>\n<p><b>Question 273.<\/b><\/p>\n<p><b>A security architect wants to reduce the chance that a compromised user account can initiate unusually high-risk transactions. Which design is MOST appropriate?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Require additional verification or approval for high-risk actions<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Give all users permanent high-value transaction rights<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disable transaction monitoring<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Use only a username for authentication<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. Require additional verification or approval for high-risk actions<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Step-up authentication, transaction signing, approval workflows, or other risk-based controls can provide additional assurance for sensitive actions. A user who is sufficiently authenticated for ordinary activity may still require stronger verification before performing a high-value transaction. This limits the damage from compromised sessions or credentials and aligns security controls with transaction risk.<\/span><\/p>\n<p><b>Question 274.<\/b><\/p>\n<p><b>Which metric should MOST directly drive the maximum acceptable frequency of data replication to a disaster-recovery site?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Recovery time objective<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Recovery point objective<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Mean time to repair<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Maximum number of administrators<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Recovery point objective<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">RPO defines how much data loss the business can tolerate after an outage. A smaller RPO requires more frequent replication or backup so recovered data is sufficiently current. RTO addresses how quickly the service must be restored rather than how much data may be lost. Both metrics influence resilience design, but replication frequency is most directly tied to the RPO.<\/span><\/p>\n<p><b>Question 275.<\/b><\/p>\n<p><b>A security architect discovers that an application accepts authorization claims from an external identity provider without verifying their signature. What is the PRIMARY risk?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Authentication may take longer<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> More logs may be generated<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Attackers could forge or modify claims and obtain unauthorized access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Certificates may expire less often<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. Attackers could forge or modify claims and obtain unauthorized access<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Federated identity assertions must be validated before they are trusted. Signature verification helps confirm that the assertion came from the expected identity provider and was not altered in transit. The relying application should also validate issuer, audience, timing, and other relevant conditions. Accepting unsigned or unverified claims can allow attackers to fabricate identities or privileges.<\/span><\/p>\n<p><b>Question 276.<\/b><\/p>\n<p><b>An organization wants to retire an old application that has several service accounts and API credentials. What should the decommissioning process include?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Leave credentials active in case the application returns<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Keep all integrations unchanged<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Remove the application from monitoring only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Revoke credentials, remove access, address retained data, and update dependent systems**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Revoke credentials, remove access, address retained data, and update dependent systems<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Secure decommissioning includes more than shutting down servers. Service accounts, API keys, certificates, trust relationships, firewall rules, data stores, backups, monitoring, and downstream integrations should be reviewed. Unused credentials and network paths can become hidden attack opportunities. Data should be retained or securely destroyed according to policy and legal requirements, and asset inventories should reflect retirement.<\/span><\/p>\n<p><b>Question 277.<\/b><\/p>\n<p><b>What is the MAIN reason to maintain architecture decision records for major security choices?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> They preserve the rationale, assumptions, alternatives, and risk decisions behind the architecture<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> They eliminate the need for future reviews<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> They guarantee the original decision remains correct forever<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> They replace technical documentation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1. They preserve the rationale, assumptions, alternatives, and risk decisions behind the architecture<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Architecture decision records provide context that diagrams alone may not capture. They help future teams understand why a particular control or pattern was chosen, which alternatives were considered, and which assumptions supported the decision. When conditions change, this information makes reassessment easier. Decision records complement technical documentation and governance rather than replacing them.<\/span><\/p>\n<p><b>Question 278.<\/b><\/p>\n<p><b>A security architect wants to prevent sensitive workloads from running on unapproved infrastructure. Which approach is BEST?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Allow workloads to run anywhere as long as they start successfully<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Enforce workload placement and platform-attestation policies before execution<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Disable infrastructure inventory<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Trust network location alone<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2. Enforce workload placement and platform-attestation policies before execution<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Sensitive workloads may require approved hardware, managed environments, trusted images, or specific security controls. Placement policy and attestation can help verify that workloads run only on infrastructure meeting defined trust requirements. This provides stronger assurance than network location alone. The exact mechanisms vary by platform, but the architectural objective is to bind workload execution to approved conditions.<\/span><\/p>\n<p><b>Question 279.<\/b><\/p>\n<p><b>A business application relies on several external SaaS services. What should the security architect include in continuity planning?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Only internal server backups<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Only application source-code recovery<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> External service dependencies, provider outages, alternative processes, and contractual recovery commitments<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> The SaaS provider&#8217;s marketing roadmap only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3. External service dependencies, provider outages, alternative processes, and contractual recovery commitments<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Business continuity can be disrupted by external providers even when internal systems are healthy. Architects should understand which SaaS services are critical, what outages would mean for the business, what provider recovery commitments exist, and whether alternative providers or manual procedures are available. External dependencies must be included in resilience design and business-impact analysis.<\/span><\/p>\n<p><b>Question 280.<\/b><\/p>\n<p><b>Which approach BEST characterizes mature security architecture governance?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Security decisions are made independently by each project with no enterprise oversight<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Exceptions never expire and require no owner<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Architecture is reviewed only after major failures<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Principles, standards, decisions, dependencies, exceptions, and risks are continuously governed and reassessed**<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4. Principles, standards, decisions, dependencies, exceptions, and risks are continuously governed and reassessed<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Mature governance treats architecture as a living enterprise discipline. Principles and standards establish direction, decision records preserve rationale, exceptions are documented and reviewed, and dependencies and risks are monitored over time. Business requirements, threats, technology, and regulation evolve, so architecture must be reassessed accordingly. Continuous governance helps prevent security design from becoming outdated or inconsistent.<\/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 261. A security architect is designing a privileged-access model for cloud administrators. Which control provides the STRONGEST reduction in standing privilege? Permanent administrator roles assigned to all cloud engineers 2. Just-in-time privileged access with approval and expiration 3. Shared administrator accounts 4. Passwords [&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\/19083"}],"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=19083"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19083\/revisions"}],"predecessor-version":[{"id":19084,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19083\/revisions\/19084"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=19083"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=19083"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=19083"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}