View Full ISC CISSP-ISSAP Exam Dumps and Practice Test Dumps
Question 181.
A security architect is designing an authentication service for several critical applications. Which consideration should be addressed FIRST?
- The visual design of the login page
2. Trust requirements, availability needs, and authentication assurance levels
3. The number of help-desk agents
4. The physical size of the servers
Correct Answer: 2. Trust requirements, availability needs, and authentication assurance levels
Explanation:
Authentication architecture should begin with an understanding of the identities involved, the sensitivity of the protected resources, required assurance, and the business impact of service failure. These requirements influence authentication methods, redundancy, federation, logging, and recovery. Cosmetic design and hardware size are secondary implementation concerns. A strong architecture traces authentication controls back to business risk and availability requirements.
Question 182.
Which security design principle BEST supports checking authorization every time a protected object is accessed?
- Complete mediation
2. Economy of mechanism
3. Open design
4. Data minimization
Correct Answer: 1. Complete mediation
Explanation:
Complete mediation requires each access attempt to a protected resource to be checked against current authorization policy. This reduces the chance that revoked or changed permissions are ignored because of an earlier access decision. The principle is especially important when permissions can change dynamically. Economy of mechanism favors simplicity, while open design and data minimization address different security concerns.
Question 183.
A security architect wants to reduce the blast radius if one microservice is compromised. Which approach is BEST?
- Give every microservice the same privileged identity
2. Permit unrestricted east-west traffic
3. Use separate service identities, segmentation, and least-privilege permissions
4. Disable service-level logging
Correct Answer: 3. Use separate service identities, segmentation, and least-privilege permissions
Explanation:
Separate identities and narrowly scoped permissions limit what a compromised microservice can access. Segmentation and explicit service-to-service policies further restrict lateral movement. This supports defense in depth and reduces the impact of credential or service compromise. Shared privileged identities and unrestricted communication greatly increase the potential blast radius.
Question 184.
A critical application depends on one cloud region. What is the MAIN architectural concern?
- The region may have too many users
2. Cloud resources may be inexpensive
3. The region may contain several availability zones
4. Regional failure could disrupt the entire application**
Correct Answer: 4. Regional failure could disrupt the entire application
Explanation:
An application that relies entirely on one region may remain vulnerable to large-scale regional outages even if it uses multiple zones within that region. If business requirements demand regional resilience, the architecture should consider geographically separate processing, data replication, network independence, and tested failover. Resilience should be designed against the failure domain the business needs to survive.
Question 185.
Why should privileged administrative accounts be separate from normal user accounts?
- To reduce exposure of privileged credentials during routine activity
2. To eliminate the need for logging
3. To guarantee administrators cannot be compromised
4. To remove authorization controls
Correct Answer: 1. To reduce exposure of privileged credentials during routine activity
Explanation:
Using separate privileged accounts limits the situations in which powerful credentials are exposed. Administrators can use normal accounts for routine email, browsing, and productivity tasks while reserving privileged identities for controlled administrative sessions. This supports least privilege, improves accountability, and reduces the risk that compromise of a normal user session immediately provides administrative access.
Question 186.
A company wants to protect API secrets used by serverless functions. Which design is MOST appropriate?
- Hard-code secrets in the function source code
2. Retrieve secrets from an approved secrets-management service using controlled workload identity
3. Publish secrets in deployment documentation
4. Use the same secret for every application permanently
Correct Answer: 2. Retrieve secrets from an approved secrets-management service using controlled workload identity
Explanation:
Secrets should not be embedded in code or documentation. A managed secrets service can provide secure storage, access control, auditing, rotation, and controlled retrieval. Serverless workloads should authenticate using an appropriate workload identity and receive only the secrets they require. This design reduces exposure through source repositories and supports stronger credential lifecycle management.
Question 187.
Which control BEST protects against unauthorized modification of system configuration baselines?
- Disabling change records
2. Allowing unrestricted administrator changes
3. Controlled change management with integrity monitoring and configuration auditing
4. Storing configurations only on user workstations
Correct Answer: 3. Controlled change management with integrity monitoring and configuration auditing
Explanation:
Approved configuration baselines should be protected from unauthorized or unnoticed modification. Change-management controls provide authorization and traceability, while integrity monitoring and configuration auditing help detect drift. Together, these mechanisms support the security architecture by ensuring that systems remain aligned with approved settings. Unrestricted changes weaken both security and accountability.
Question 188.
A security architect is designing a failover site for a critical database. Which requirement should MOST directly determine replication frequency?
- Administrator preference
2. Data-center floor space
3. Recovery time objective only
4. Recovery point objective**
Correct Answer: 4. Recovery point objective
Explanation:
The recovery point objective specifies the maximum amount of data loss the business can tolerate. Replication or backup frequency must be sufficient to meet that target. The recovery time objective influences how quickly the service must be restored but does not directly define how current the recovered data must be. Both metrics should be incorporated into resilience design.
Question 189.
What is the PRIMARY security benefit of placing an API gateway between external clients and internal services?
- It creates a controlled enforcement point for authentication, validation, rate limiting, and logging
2. It eliminates the need for backend authorization
3. It guarantees application availability
4. It allows every internal service to be publicly exposed
Correct Answer: 1. It creates a controlled enforcement point for authentication, validation, rate limiting, and logging
Explanation:
An API gateway can reduce direct exposure of internal services and provide consistent security enforcement at a trust boundary. It may perform authentication, request validation, rate limiting, routing, logging, and other controls. Backend services should still enforce appropriate authorization and security policies. The gateway provides an additional layer rather than replacing service-level protections.
Question 190.
An enterprise uses several external identity providers. What should the security architect establish to reduce inconsistent trust decisions?
- Different access rules for every user without governance
2. Common federation assurance requirements and trust policies
3. Anonymous fallback authentication
4. Shared administrator passwords with each provider
Correct Answer: 2. Common federation assurance requirements and trust policies
Explanation:
Multiple identity providers can create inconsistent authentication assurance unless common trust requirements are defined. The organization should establish acceptable authentication strength, assertion validation, certificate or key management, identity attributes, authorization mapping, and procedures for terminating trust. Standardized federation policies help ensure that access decisions remain aligned with enterprise risk regardless of which provider authenticates the user.
Question 191.
A security architect finds that developers can modify production infrastructure directly without approval. What is the PRIMARY concern?
- Production systems may consume more storage
2. Developers may need additional training
3. Unauthorized or unreviewed changes can bypass security and change controls
4. Source code may contain too many files
Correct Answer: 3. Unauthorized or unreviewed changes can bypass security and change controls
Explanation:
Direct production modification can bypass testing, approval, integrity verification, and separation-of-duties controls. A controlled deployment process should ensure that changes are reviewed, authorized, traceable, and based on approved artifacts. Restricting direct administrative access also reduces insider and credential-compromise risk. Production changes should follow defined governance rather than ad hoc modification.
Question 192.
A highly sensitive system relies on a centralized policy engine. What should the architecture define if the engine becomes unavailable?
- New interface colors
2. Whether employees may bypass policy manually
3. How many administrators are on duty
4. Explicit fail-secure and continuity behavior**
Correct Answer: 4. Explicit fail-secure and continuity behavior
Explanation:
Dependency failures should not result in undefined security behavior. The architecture should specify whether access is denied, whether limited cached policy can be used, how long such policy remains valid, and which operations remain permitted. These decisions must balance confidentiality, integrity, and availability. For highly sensitive systems, fail-secure behavior is often appropriate when authorization cannot be verified.
Question 193.
Which action BEST supports reducing security risk from unnecessary functionality in a new system?
- Disable unneeded services, interfaces, accounts, and ports
2. Enable every feature by default
3. Grant all users administrator permissions
4. Expose management interfaces publicly
Correct Answer: 1. Disable unneeded services, interfaces, accounts, and ports
Explanation:
Unused functionality increases attack surface without delivering business value. Removing or disabling unnecessary services, ports, interfaces, and accounts reduces the number of potential attack paths and simplifies monitoring and hardening. Required functions should remain available but should be configured securely and exposed only to the users or systems that legitimately need them.
Question 194.
A company processes regulated customer data through a third-party platform. What should be defined before production use?
- Only the provider’s support phone number
2. Security responsibilities, data handling, incident notification, retention, and assurance requirements
3. The provider’s advertising budget
4. The color of the provider’s management portal
Correct Answer: 2. Security responsibilities, data handling, incident notification, retention, and assurance requirements
Explanation:
Third-party use of regulated data requires explicit governance. The organization should define responsibility boundaries, permitted processing, access controls, incident reporting, retention, deletion, audit rights, and security assurance expectations. These requirements should be reflected in contracts and operating procedures. Relying on informal assumptions can leave serious gaps in security and compliance.
Question 195.
A security architect is reviewing a legacy application that cannot support modern encryption. Which response is MOST appropriate?
- Ignore the limitation permanently
2. Expose the application directly to untrusted networks
3. Assess the risk and use compensating controls such as secure gateways or encrypted tunnels
4. Disable all monitoring
Correct Answer: 3. Assess the risk and use compensating controls such as secure gateways or encrypted tunnels
Explanation:
Legacy limitations should be addressed through risk analysis and compensating controls. Secure gateways, encrypted tunnels, network isolation, and restricted access paths may provide protection when the application itself cannot support modern cryptography. The organization should also consider long-term modernization or replacement. Simply accepting the weakness without analysis creates unmanaged risk.
Question 196.
A security architect wants to prevent administrators from deleting evidence of their own privileged actions. Which design is BEST?
- Store logs only on the administered system
2. Give administrators full access to audit records
3. Disable logging during maintenance windows
4. Forward audit records to a separately protected logging platform**
Correct Answer: 4. Forward audit records to a separately protected logging platform
Explanation:
A separately protected logging platform provides an independent copy of privileged activity and makes it harder for an administrator or attacker controlling the target system to erase evidence. Logs should be protected from modification, synchronized in time, monitored, and retained according to policy. Local logging remains useful, but independent storage strengthens accountability.
Question 197.
Which architectural principle MOST directly supports reducing unnecessary complexity in security controls?
- Economy of mechanism
2. Complete mediation
3. Separation of privilege
4. Defense in depth
Correct Answer: 1. Economy of mechanism
Explanation:
Economy of mechanism encourages security designs to be as simple as practical. Simpler mechanisms are generally easier to understand, test, validate, and maintain. Unnecessary complexity can introduce hidden dependencies and configuration errors. This principle does not mean eliminating required functionality; rather, every additional component or rule should have a justified purpose.
Question 198.
A company requires that no single employee can both create and approve a high-value payment. Which security concept is being applied?
- Open design
2. Separation of duties
3. Data minimization
4. High availability
Correct Answer: 2. Separation of duties
Explanation:
Separation of duties divides sensitive responsibilities among multiple people so that no one individual can complete the entire high-risk process. Requiring separate initiation and approval reduces the likelihood of fraud, abuse, and undetected mistakes. The design should also maintain individual identities and protected audit logs so each participant’s actions remain traceable.
Question 199.
An enterprise application depends on DNS, identity, and key-management services. Why should these dependencies be included in resilience planning?
- Supporting services are never critical
2. Applications can function without them during outages
3. Failure of a shared dependency can disrupt applications even when their own servers are healthy
4. Shared services should always be eliminated
Correct Answer: 3. Failure of a shared dependency can disrupt applications even when their own servers are healthy
Explanation:
Application availability depends on more than the application servers themselves. DNS, identity, certificates, networks, and key-management systems can all be critical supporting services. Failure of one shared dependency may affect many applications simultaneously. Resilience planning should therefore include these dependencies, their recovery requirements, redundancy, and concentration risk.
Question 200.
Which practice BEST demonstrates mature ISSAP-level security architecture governance?
- Freeze architecture standards permanently
2. Allow undocumented exceptions when projects request them
3. Review designs only after deployment
4. Maintain principles and standards, evaluate designs and exceptions, track risk, and reassess architecture as conditions change**
Correct Answer: 4. Maintain principles and standards, evaluate designs and exceptions, track risk, and reassess architecture as conditions change
Explanation:
Mature security architecture governance is continuous and risk-based. Principles and standards create consistency, design reviews identify weaknesses early, and formal exception processes ensure deviations are justified and documented. Risk decisions should be tracked and revisited as business requirements, technologies, regulations, threats, and dependencies change. Architecture should remain a living discipline rather than a one-time approval exercise.