View Full ISC CISSP-ISSAP Exam Dumps and Practice Test Dumps
Question 201.
A security architect is designing a new enterprise application that will process confidential data across several business units. What should be established FIRST?
- Security requirements derived from business objectives, data sensitivity, and risk
2. The preferred firewall vendor
3. The final penetration-testing schedule
4. The production server naming convention
Correct Answer: 1. Security requirements derived from business objectives, data sensitivity, and risk
Explanation:
Architecture should begin with requirements rather than specific technologies. The architect needs to understand business objectives, information classification, regulatory obligations, trust boundaries, availability expectations, and risk tolerance. These factors determine what security capabilities are necessary. Selecting products before defining requirements can produce controls that are expensive yet poorly aligned with actual risk. Testing schedules and naming conventions are implementation considerations that follow the architecture.
Question 202.
A critical application uses a centralized authorization service. Which design BEST improves resilience without abandoning centralized policy governance?
- Permit all access whenever the authorization service is unavailable
2. Provide redundant authorization services with clearly defined fail-secure behavior
3. Disable authorization for internal users
4. Store administrator passwords in the application configuration
Correct Answer: 2. Provide redundant authorization services with clearly defined fail-secure behavior
Explanation:
A centralized authorization service can become a critical dependency. Redundant service instances reduce availability risk while preserving consistent policy enforcement. The application should also have explicitly defined behavior if authorization cannot be verified, particularly for sensitive operations. Automatically allowing access during an outage creates a security bypass. Resilience should therefore be designed together with secure failure behavior rather than sacrificing authorization for availability.
Question 203.
An organization wants to reduce the risk created by administrators using powerful credentials for email and web browsing. Which architecture is MOST appropriate?
- Give every administrator one permanent global account
2. Disable endpoint protection
3. Use separate privileged identities and dedicated administrative workstations or sessions
4. Permit privileged login from any unmanaged device
Correct Answer: 3. Use separate privileged identities and dedicated administrative workstations or sessions
Explanation:
Separating privileged administration from routine user activity reduces exposure of powerful credentials to phishing, malicious websites, email attachments, and ordinary endpoint threats. Dedicated administrative workstations, jump hosts, strong authentication, and separate privileged identities can significantly reduce this risk. Privileged access should also be logged and restricted through controlled network paths. A single broadly used administrator account increases the consequences of compromise.
Question 204.
A security architect discovers that all production systems depend on a single time-synchronization source. What is the PRIMARY concern?
- Time synchronization may increase bandwidth use
2. Users may see different time zones
3. Logs may contain timestamps
4. The time source represents a shared dependency and potential single point of failure**
Correct Answer: 4. The time source represents a shared dependency and potential single point of failure
Explanation:
Time synchronization is important for authentication, certificate validation, distributed transactions, monitoring, and forensic analysis. If every production system depends on one source, failure or compromise of that source could affect many services simultaneously. The architect should consider resilient and trustworthy time sources, appropriate hierarchy, monitoring, and protection against unauthorized changes. Shared infrastructure dependencies should be included in resilience planning.
Question 205.
Which architectural practice BEST reduces the exposure of sensitive databases to compromised web servers?
- Place database systems in a separate security zone and permit only required application flows
2. Allow unrestricted traffic between all tiers
3. Disable database authentication
4. Place databases directly on the internet
Correct Answer: 1. Place database systems in a separate security zone and permit only required application flows
Explanation:
Separating database systems from internet-facing components limits direct attack paths and lateral movement. Only explicitly required traffic from approved application components should be permitted. This approach supports segmentation, least privilege, and defense in depth. Database authentication and authorization should remain enabled as additional controls. A flat network greatly increases the blast radius if a public-facing system is compromised.
Question 206.
An application must authenticate machine identities at very large scale. Which factor is MOST important when designing certificate-based authentication?
- The visual format of certificates
2. Automated issuance, renewal, revocation, and private-key protection
3. The number of application logos
4. User password length
Correct Answer: 2. Automated issuance, renewal, revocation, and private-key protection
Explanation:
Large-scale certificate authentication depends on reliable lifecycle automation. Certificates must be issued securely, renewed before expiration, revoked when compromised or retired, and associated private keys must be protected. Without lifecycle automation, expired certificates and unmanaged keys can cause outages or security failures. Cryptographic strength alone is insufficient if certificate operations and key custody are poorly designed.
Question 207.
A security architect wants to ensure that software dependencies from external repositories are trustworthy before they enter the build pipeline. Which control BEST supports this goal?
- Disable build logging
2. Permit developers to download arbitrary packages directly into production
3. Use approved repositories, dependency verification, and software-supply-chain controls
4. Share signing keys with all developers
Correct Answer: 3. Use approved repositories, dependency verification, and software-supply-chain controls
Explanation:
Third-party dependencies can introduce malicious code, vulnerable libraries, or tampered packages. Approved repositories, integrity verification, dependency inventories, vulnerability checks, and controlled build processes help reduce software-supply-chain risk. Signing and provenance mechanisms can provide additional assurance. Allowing unrestricted package downloads or exposing signing keys would weaken rather than strengthen the integrity of the development process.
Question 208.
A business requires an application to remain available after failure of an entire primary site. Which architecture provides the BEST protection?
- Two servers in the same rack
2. A larger uninterruptible power supply at the primary site
3. Additional local disk capacity
4. A geographically separate recovery or active service capability with tested failover**
Correct Answer: 4. A geographically separate recovery or active service capability with tested failover
Explanation:
Site-level failures can affect power, network connectivity, cooling, physical infrastructure, and all systems within the location. Geographic separation reduces common-mode failure risk. The secondary capability should include the processing, data, networking, and security services needed to meet business RTO and RPO targets. Failover must be tested because untested redundancy may not function correctly during a real disaster.
Question 209.
Why should encryption keys for highly sensitive applications be separated from the encrypted application data?
- Separation reduces the likelihood that compromise of the data store also exposes the decryption keys
2. It removes the need for authentication
3. It guarantees that cryptography cannot fail
4. It eliminates key rotation requirements
Correct Answer: 1. Separation reduces the likelihood that compromise of the data store also exposes the decryption keys
Explanation:
Encryption provides limited protection if keys are stored beside the encrypted data with equivalent access controls. Separating key storage through a dedicated key-management system or hardware security mechanism can reduce the chance that one compromise exposes both data and keys. Key lifecycle management, access restrictions, auditing, rotation, and recovery are still necessary. Separation is one element of a broader cryptographic architecture.
Question 210.
A company wants to grant access based on user role, device health, network context, and transaction risk. Which approach is MOST suitable?
- Shared-account authentication
2. Attribute-based or contextual access control
3. Anonymous access
4. Static network trust only
Correct Answer: 2. Attribute-based or contextual access control
Explanation:
Attribute-based and contextual access control can evaluate multiple characteristics such as user identity, role, device compliance, location, resource sensitivity, time, and transaction risk. This allows more granular and adaptive decisions than a simple static role or network location. Policies should remain manageable and auditable, and access should still follow least-privilege principles.
Question 211.
An architect discovers that a critical application can modify its own audit logs. What is the PRIMARY security concern?
- Log files may consume too much storage
2. The application may use too much processor capacity
3. Evidence of malicious or unauthorized actions could be altered or destroyed
4. Users may receive too many alerts
Correct Answer: 3. Evidence of malicious or unauthorized actions could be altered or destroyed
Explanation:
Audit records support accountability, incident response, and forensic investigation. If the application or an attacker controlling it can freely alter the only audit evidence, malicious activity may be concealed. Critical logs should therefore be forwarded to or protected by an independent logging mechanism with restricted modification rights. Integrity protection and appropriate retention further strengthen trust in audit records.
Question 212.
A system is required to process highly confidential information but must also remain accessible during an authorization-service outage. What should the architect do?
- Always fail open
2. Disable authorization permanently
3. Allow unrestricted access to maintain availability
4. Define an explicit risk-based continuity design that preserves fail-secure behavior for sensitive operations**
Correct Answer: 4. Define an explicit risk-based continuity design that preserves fail-secure behavior for sensitive operations
Explanation:
Security and availability requirements can conflict during dependency failures. The architecture should define which operations may use cached decisions, how long those decisions remain valid, and which sensitive operations must stop if authorization cannot be verified. A blanket fail-open approach is inappropriate for highly confidential data. The decision should be based on business impact, risk tolerance, and the sensitivity of each function.
Question 213.
Which activity MOST directly helps identify whether a proposed architecture contains unnecessary trust relationships?
- Threat modeling and trust-boundary analysis
2. Increasing server memory
3. Reviewing user-interface colors
4. Counting application source files
Correct Answer: 1. Threat modeling and trust-boundary analysis
Explanation:
Threat modeling and trust-boundary analysis help architects understand how users, systems, services, and external parties interact and where trust is assumed. This can reveal relationships that are broader than necessary, such as unrestricted internal access or implicit trust between application components. Unnecessary trust should be reduced through authentication, segmentation, authorization, and explicit policy enforcement.
Question 214.
A security architect is designing backup protection for a ransomware-resilient environment. Which approach is BEST?
- Allow production administrators unrestricted deletion of all backups
2. Maintain isolated or immutable recovery copies with separately controlled access
3. Keep one writable backup attached to every production server
4. Disable backup verification
Correct Answer: 2. Maintain isolated or immutable recovery copies with separately controlled access
Explanation:
Ransomware can target both production data and accessible backups. Isolated, offline, or immutable recovery copies reduce the chance that a compromised production account can encrypt or delete all recovery data. Access to backups should be separately controlled and monitored, and restoration procedures should be tested. Backup security should account for malicious administrative compromise, not only hardware failure or accidental deletion.
Question 215.
An application processes sensitive data but retains it indefinitely even after the business purpose has ended. Which principle is being violated MOST directly?
- Complete mediation
2. Defense in depth
3. Data minimization and appropriate retention
4. High availability
Correct Answer: 3. Data minimization and appropriate retention
Explanation:
Sensitive information should not be retained longer than necessary for legitimate business, legal, or regulatory purposes. Excessive retention increases privacy exposure, storage risk, and breach impact. An appropriate architecture should include retention schedules, secure deletion, and lifecycle controls. Data minimization applies not only to collection but also to continued storage of information after its original purpose has ended.
Question 216.
A business wants to use one identity provider across hundreds of applications. What should the architect address MOST carefully?
- The provider’s interface design
2. The number of application icons
3. Employee office assignments
4. Concentration risk, resilience, strong administration, and recovery of the identity service**
Correct Answer: 4. Concentration risk, resilience, strong administration, and recovery of the identity service
Explanation:
A centralized identity provider can simplify authentication and policy enforcement, but it also becomes a highly critical dependency. An outage or compromise could affect hundreds of applications simultaneously. The architecture should therefore address redundancy, secure administration, privileged-access controls, monitoring, disaster recovery, key protection, and tested failover. Shared security services require especially strong resilience and governance.
Question 217.
A security architect wants to reduce the likelihood that unauthorized software reaches production. What should be implemented?
- A controlled build and deployment process with approvals, integrity checks, and traceable artifacts
2. Direct developer modification of production systems
3. Shared production administrator credentials
4. Disabled deployment logs
Correct Answer: 1. A controlled build and deployment process with approvals, integrity checks, and traceable artifacts
Explanation:
A secure build and deployment process provides consistent controls over what reaches production. Code review, testing, artifact integrity verification, approvals, and traceability help prevent unreviewed or tampered software from being deployed. Direct production changes should be minimized. The pipeline itself is sensitive infrastructure and should be protected with strong access controls and monitoring.
Question 218.
Which control BEST supports nonrepudiation for digitally signed high-value transactions?
- Shared signing keys
2. Strong signer identity, protected private keys, trusted timestamps, and verifiable signatures
3. Anonymous transaction submission
4. Disabled transaction logging
Correct Answer: 2. Strong signer identity, protected private keys, trusted timestamps, and verifiable signatures
Explanation:
Nonrepudiation depends on reliable evidence linking an action to a specific party. Strong identity assurance, controlled private-key custody, digital signatures, timestamps, and protected audit evidence strengthen that linkage. Shared keys undermine attribution because several users could perform the same signing action. The architecture must protect both the cryptographic keys and the evidence used to verify transactions.
Question 219.
A legacy system cannot support the organization’s required authentication standard. What should the security architect do FIRST?
- Disable all security controls
2. Grant unrestricted access because the system is legacy
3. Assess the resulting risk and identify compensating controls or a remediation path
4. Hide the system from architecture documentation
Correct Answer: 3. Assess the resulting risk and identify compensating controls or a remediation path
Explanation:
Legacy constraints should be handled through formal risk management. The architect should determine how much risk the authentication limitation creates and whether controls such as network isolation, access gateways, stronger upstream authentication, monitoring, or restricted privileges can compensate. A long-term modernization or replacement plan may also be necessary. Ignoring the limitation creates unmanaged technical and security debt.
Question 220.
Which approach BEST supports long-term effectiveness of an ISSAP-level enterprise security architecture?
- Review architecture only after major breaches
2. Allow permanent undocumented exceptions
3. Freeze all security standards indefinitely
4. Continuously reassess requirements, risks, dependencies, exceptions, and control effectiveness**
Correct Answer: 4. Continuously reassess requirements, risks, dependencies, exceptions, and control effectiveness
Explanation:
Enterprise security architecture must adapt as business priorities, threats, technologies, regulations, and external dependencies change. Mature practice includes ongoing architecture reviews, documented exceptions, risk tracking, control validation, and reassessment of assumptions. A design that was appropriate several years ago may no longer address current risk. Continuous governance keeps architecture aligned with the organization’s evolving environment.