You save $69.98
Management implemented a response after this event: A project owner is permitted to share low-risk documents but an administrator mandates central labels for all copies. The response was: Use controlled discretionary permission delegation only within higher-priority mandatory constraints. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
Owners can share eligible files but cannot override prohibited high-classification access. DAC lets owners grant access, but it cannot override centrally enforced classification rules.
A total ban does not implement the intended permitted discretionary access workflow.
Discretionary sharing has defeated the required central restriction.
The mechanism does not demonstrate bounded and auditable delegated permissions.
A microservice caches authorization at the gateway, then permits direct internal calls without rechecking entitlements. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Centralized policy decision logic is ineffective when downstream bypass routes evade enforcement. Decision caching must be bounded to limit stale grants after revocation.
Direct internal routing can bypass the decision unless downstream protected resources enforce access.
Client-side presentation does not guarantee server-side authorization.
Unbounded stale decisions extend access beyond current permitted conditions.
The organization implemented the response to this scenario: A microservice caches authorization at the gateway, then permits direct internal calls without rechecking entitlements. The approved response was: Enforce each resource request at a policy enforcement point using current decisions from a trusted policy service. Which statement MOST accurately identifies a remaining risk or constraint?
Centralized policy decision logic is ineffective when downstream bypass routes evade enforcement. A direct internal call without required entitlement is denied just like a gateway call.
Policy decisions matter only when every protected request is mediated.
Stale cache entries can preserve forbidden access after entitlements change.
Detection at one point cannot substitute for complete enforcement coverage.
Management implemented a response after this event: A microservice caches authorization at the gateway, then permits direct internal calls without rechecking entitlements. The response was: Enforce each resource request at a policy enforcement point using current decisions from a trusted policy service. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
A direct internal call without required entitlement is denied just like a gateway call. Centralized policy decision logic is ineffective when downstream bypass routes evade enforcement.
Bypass of the enforcement point defeats consistent authorization.
Decision freshness has not been propagated to actual resource enforcement.
Client UI behavior is not evidence of server-side protected object checks.
In a procurement application, one clerk can create a vendor, approve that vendor and release payments to it. What is the BEST preventive security architecture?
A single principal should not control all stages of a high-risk financial transaction. Distinct authorities reduce undetected fraud and error.
Detective review can help, but it does not prevent an individual from initiating and approving the fraudulent transaction.
Training and attestation do not enforce conflicting permissions in the application.
Client UI changes can be bypassed; conflict constraints must be enforced server-side.
Procurement duties are split among vendor creation, approval and payment roles. What residual fraud risk still needs detective control?
SoD reduces single-person control but does not eliminate coordinated fraud or the risk of a shared credential bridging roles.
Role separation is a control, not a guarantee that multiple people cannot cooperate maliciously.
Shared identities can bypass role accountability and conflict constraints even with periodic rotation.
Independent reconciliation and audit trails remain needed to identify failures and coordinated abuse.
The procurement system claims one employee can no longer create a vendor, approve it and authorize payment. Which test BEST proves the role separation?
A real negative enforcement check plus an authorized business process shows the separation is functional, not just a diagram of different teams.
Nominal role naming does not enforce conflicting-action constraints.
That shows a bypass of the separation intended to reduce single-person fraud.
Awareness is useful but does not prove transaction authorization enforcement.
A departed employee still appears as owner of a privileged service account in three systems. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Unowned and stale accounts evade ordinary access reviews and incident response. Automatically deleting every shared service identity can break necessary operations.
Stale ownership obscures accountability and may leave inappropriate effective access.
Indiscriminate deletion can break critical applications rather than safely resolve orphan accounts.
A cosmetic rename cannot correct abandoned entitlement and owner records.
The organization implemented the response to this scenario: A departed employee still appears as owner of a privileged service account in three systems. The approved response was: Reconcile identity lifecycle events and remove or reassign orphaned access with accountable ownership. Which statement MOST accurately identifies a remaining risk or constraint?
Unowned and stale accounts evade ordinary access reviews and incident response. A sampled departed identity has no active permissions and surviving services have named owners.
Service identities may remain independently active after the human leaves.
Nonhuman principals can retain powerful machine-to-machine permissions.
Lifecycle correction should safely reassign necessary functions and revoke obsolete access.
Management implemented a response after this event: A departed employee still appears as owner of a privileged service account in three systems. The response was: Reconcile identity lifecycle events and remove or reassign orphaned access with accountable ownership. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
A sampled departed identity has no active permissions and surviving services have named owners. Unowned and stale accounts evade ordinary access reviews and incident response.
HR status alone does not prove asset and access reconciliation.
Destructive removal without continuity is not sound lifecycle management.
A review missing nonhuman principals cannot demonstrate absence of orphan access.
Quarterly access reviews approve all entitlements without managers seeing actual privileges or use history. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Rubber-stamp reviews do not demonstrate that permissions remain appropriate. Historical usage alone can omit rare emergency tasks and must be contextualized.
A rubber-stamp workflow cannot substantiate business necessity and least privilege.
Some legitimate emergency permissions require contextual assessment rather than blind usage rules.
Role labels do not reveal accumulated privileges or toxic combinations.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (484 Questions, Last Updated on Oct 31, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
