CompTIA Security+ SY0-701 Practice Test 30
Question 290
A military research network requires that classified files be accessible only to users with centrally assigned clearances and matching need-to-know labels. Individual file creators must not override the classification policy by sharing documents with friends. Which authorization approach most closely matches?
- Discretionary access control because resource creators decide recipients
- Mandatory access control enforced through central security labels and clearance rules
- Use ordinary application RBAC roles but allow each file creator to override centrally required classifications with a discretionary share grant
- A basic single sign-on session without resource classification checks
Explanation
Correct Answer
B:Mandatory access control constrains access using centrally governed security labels and subject clearances rather than allowing each resource owner to override the policy. For classified research data, the system must evaluate the file's classification, user clearance and applicable need-to-know or compartment attributes before permitting actions. Labels, trusted administration and policy enforcement must be maintained consistently as information is created and moved. A clearance may be necessary but not sufficient; permitted operations also depend on the organization’s classification model. This approach ensures that a document creator cannot unilaterally grant a friend access contrary to centrally defined restrictions.
Incorrect Answers
A:Discretionary control permits an authorized resource owner to influence who receives access, which conflicts with the scenario's explicit prohibition on individual sharing overrides. An owner may possess a file but still lack authority to downgrade its label. The classification policy must be enforced independently of ordinary file-owner preferences. DAC may support collaboration in other settings, but does not satisfy this centrally controlled secrecy requirement by itself.
C:RBAC can restrict application functions, and many document platforms implement it effectively for ordinary enterprise collaboration. Here the crucial requirement is that file owners cannot grant access contrary to mandatory labels and clearance rules. A role system that still permits discretionary sharing overrides does not satisfy the centrally enforced classification boundary. Mandatory access control must apply trusted security labels and subject clearances even when a creator wants an exception.
D:Single sign-on helps establish an authenticated session across services; it does not automatically make access decisions on classified documents. A successfully logged-in user might still lack clearance or need-to-know for a particular file. The content platform needs central label and clearance rules in addition to login authentication. SSO and MAC can coexist, but the requested feature is control over classified resource release, not a reduced number of password prompts.
Question 291
A service requires a user to enter an account password and a separate six-digit PIN stored as another secret. Security management describes the arrangement as 'two-factor authentication' because users enter two values. Which assessment is correct?
- The password is knowledge and the PIN is possession, so two independent factors are present
- Both password and PIN are knowledge factors, so the combination does not establish multifactor authentication
- Treat the PIN as a second factor because it is issued by a separate onboarding team, even though the user memorizes it
- Two knowledge secrets are stronger than any phishing-resistant hardware key by definition
Explanation
Correct Answer
B:Passwords are something the user knows, and a memorized PIN is also something the user knows. Distinct secrets can add a hurdle in some implementations, but using two knowledge inputs does not satisfy the independence of factor categories required for MFA. To add a second type, the service could use a verified possession authenticator or biometric factor with appropriate security properties. The provider should also assess phishing resistance, because adding another secret prompt does not prevent a convincing attacker from collecting both values. Factor counting must reflect the actual authentication mechanism, not merely the number of fields in a form.
Incorrect Answers
A:Possession requires demonstrating control of an item or cryptographic authenticator, not entering a memorized number. A PIN may unlock a device or security key locally, but here it is a separate secret verified by the service. That makes it knowledge, just like the password. Classifying a static PIN as possession would falsely inflate authentication assurance and mislead control assessments.
C:Independent enrollment and a separately assigned PIN may make the secret harder to guess than a reused password. The authentication factor category, however, depends on what a claimant demonstrates during login. If the user enters two remembered secrets, both are knowledge factors, no matter which department issued them. A possession authenticator or biometric-based mechanism would need an independently verified property rather than another typed memorized value.
D:The number of knowledge secrets cannot establish superiority over phishing-resistant cryptographic authentication. Both password and PIN can be exposed through the same phishing page or social-engineering attack. A properly implemented origin-bound hardware authenticator can resist credential replay against a fake site. The appropriate comparison considers factor independence, phishing resistance and session protections, not an absolute claim that two memorized values always outperform a hardware key.
Question 292
An organization has suffered repeated adversary-in-the-middle phishing attacks that capture password and SMS codes. It wants an authenticator for employees that checks the legitimate service origin and uses challenge-response cryptography rather than transferable one-time codes. Which option is best?
- Send a six-digit SMS code after each password entry
- Ask users to answer two security questions in addition to their password
- Add a time-based authenticator-app code that the employee types into the same browser login form
- Deploy FIDO2/WebAuthn security keys or suitable passkeys bound to the approved service origin
Explanation
Correct Answer
D:FIDO2/WebAuthn authenticators use public-key challenge-response with relying-party and origin binding, so a credential registered to the legitimate domain is not normally usable to sign an attacker-controlled look-alike origin. Security keys or appropriately managed passkeys therefore address credential relay differently from SMS OTPs. Deploy supported policies for device registration, lost-key recovery, attestation where needed and session lifetime; phishing-resistant sign-in does not eliminate all risks from compromised endpoints or stolen authenticated sessions. The key distinction is that the authenticator's response is bound to the expected service identity rather than being a transferable code a user can type into a fraudulent prompt.
Incorrect Answers
A:SMS codes add a possession-related check in some threat models, but they can be relayed to a phishing proxy that immediately uses them at the real site. The case explicitly involves adversary-in-the-middle phishing, so a transferable code does not meet the desired origin-bound challenge-response property. SMS also depends on phone-number recovery and delivery security. Stronger options should resist replay at a look-alike domain.
B:Security questions generally ask for knowledge that can be discovered, guessed or phished along with a password. Adding more questions does not create the requested public-key operation bound to a verified site origin. The organization needs an authenticator designed to reject fake relying parties, not additional reusable answers. Recovery procedures should also avoid weakening the stronger login method with low-assurance shared secrets.
C:Time-based one-time codes are often preferable to SMS for delivery security and can provide a second possession-related factor. They are nevertheless transferable strings that an adversary-in-the-middle proxy can collect and relay during a live phishing attack. They are not bound to the legitimate relying-party origin in the way WebAuthn challenge responses are. The scenario specifically requires phishing resistance against real-time code relay.
Question 293
A quarterly entitlement review reveals that several former project members still have write access to a sensitive data warehouse. Management wants accountable business owners to confirm continuing need and promptly remove unjustified grants. Which procedure best achieves this?
- Treat an application owner’s failure to respond by the quarterly deadline as approval to retain all existing grants.
- Remove access only when an employee account is terminated, leaving active employees’ previous project roles unchanged.
- Let the IAM administrator renew roles from the historical approval ticket without asking the current data owner to attest.
- Run an access recertification in which designated owners attest or reject individual privileges and enforce removals
Explanation
Correct Answer
D:Periodic access recertification presents current user-to-resource permissions to designated data or application owners for explicit attestation. Each owner confirms business need or rejects stale privileges, and the identity team must execute removals and verify they took effect. Track completion, overdue reviewers, exceptions and high-risk entitlements such as write and administrator rights. Reconcile results with joiner, mover and leaver records so departing project members are not automatically retained. Attestation is not merely collecting signatures: it must drive enforceable changes and preserve evidence showing what access was reviewed and when. Exception approval must be explicit and time-limited when an owner cannot yet determine necessity.
Incorrect Answers
A:Automatically retaining privileges after a missed review is administratively easy, but silence is not reliable evidence that a former project member still needs write access. An entitlement campaign should establish an escalation path for missing attestations and a controlled removal or suspension decision under policy. The organization needs affirmative accountability, not indefinite permission inheritance from a previous assignment that no longer reflects the user’s role.
B:Terminated-account cleanup is essential identity hygiene and can prevent post-employment access. It does not address this finding because the people have left a project but might still work for the company. Their identities legitimately remain active while obsolete warehouse-write grants accumulate. Recertification must evaluate each entitlement against the current business need and remove inappropriate access without disabling unrelated legitimate work.
C:Earlier approvals help explain why a privilege existed, but they do not prove continuing need after staffing and project changes. An IAM administrator can implement removals and supply access history, yet the business owner is better placed to validate the current purpose of warehouse writes. Relying only on an old ticket converts a periodic recertification into a paperwork renewal and leaves stale grants intact.
Question 294
A company hires staff in several countries each day. HR approves employment and department information in its system, but IT manually creates directory and application accounts, causing delays and occasional excess permissions. What automation design best improves this process without bypassing authorization?
- Provision unrestricted accounts automatically as soon as anyone enters a name into a public form
- Let new employees choose their own privileged application roles during first login
- Automatically provision standard accounts from manager-submitted spreadsheets but skip confirmation against approved HR employment and role records
- Trigger identity provisioning from approved HR lifecycle events, use governed role mappings and record approvals and outcomes
Explanation
Correct Answer
D:An authoritative HR status change can trigger a workflow that creates a directory identity, assigns standard department and job-role groups, requests additional approvals where needed and logs every outcome. Map HR attributes only to maintained entitlement definitions, enforce uniqueness and protect against duplicate or premature activation. Handle failed downstream provisioning with retries and clear exception queues, and coordinate later mover and leaver events through the same lifecycle framework. This reduces manual delay and inconsistent grants while keeping business approval and auditability. Automated execution is appropriate once the eligibility and permission decisions have been made under governance.
Incorrect Answers
A:A public form with no verified employment workflow cannot establish that a person should receive corporate access. Creating unrestricted identities from that input would enable unauthorized entry and privilege misuse. An automated process must have a trusted event source and enforce role selection according to approved employment data. Speed does not justify bypassing eligibility checks or granting greater permissions than a new role requires.
B:Employees may know their job duties, but letting them self-assign powerful access without approval defeats separation of duties and least privilege. Self-service requests can be useful when routed to accountable managers or resource owners. The final entitlement must still be authorized and bounded by policy. The organization wants fewer mistakes from manual provisioning, not an uncontrolled entitlement marketplace that copies users' desired privileges into production.
C:Automated spreadsheets could reduce repetitive typing, and managers may know their teams’ immediate onboarding needs. A manager-entered list is not necessarily authoritative proof that employment is active or that a particular entitlement was approved. Unchecked imports can create accounts prematurely or assign outdated groups. The scenario provides validated HR lifecycle data; provisioning should use those events and governed job-role mappings with exception handling and a recorded outcome.
Question 295
A regulated service creates cloud storage buckets from approved infrastructure templates. Pull-request policy checks normally reject public-read access, but release engineers can bypass that CI step with a privileged emergency flag and invoke the cloud provisioning API directly. The security architect wants a forbidden public-read setting rejected even if the pipeline check is skipped. Which added guardrail closes this enforcement gap?
- Enforce a cloud account or organization-level deny policy against public bucket access, backed by IaC checks and tightly governed exceptions
- Keep the optional CI warning and require the engineer to acknowledge it before using the direct cloud API
- Enable immediate cloud posture alerts on newly public buckets, then request remediation after the service is already provisioned
- Require encryption at rest on the bucket but leave anonymous object reads permitted under the bucket policy
Explanation
Correct Answer
A:A cloud account or organization-level public-access denial can reject an unsafe storage permission when any authorized caller tries to create or modify it, including one that bypasses a CI-only lint step. Keep the source-template checks for fast developer feedback, but enforce the non-bypassable policy at the cloud control plane with suitably constrained exception authority. Test both pipeline and direct-API attempts, and record necessary exceptions under named approval. This differs from merely combining pre-deployment scans and later drift monitoring: the decisive failure in this scenario is a privileged path that skips pipeline validation. The preventive policy must still apply along that bypass route.
Incorrect Answers
B:Acknowledging a warning improves traceability and may make engineers consider the risks of an emergency deployment. It does not change the underlying fact that the cloud API will accept the prohibited public-read configuration once the CI step is bypassed. The business asks for an enforceable denial, not a soft reminder. Account-level restrictions should apply regardless of which pipeline or command-line caller submits the request, with exceptions controlled separately.
C:Rapid posture alerts can shorten the time that a mistakenly public bucket remains exposed, and the organization should monitor for later changes. A detective signal arrives only after the provider has created or altered a policy that may grant anonymous read access. The scenario requires rejection at provisioning time even when pipeline lint is skipped. Cloud-side authorization restrictions can block that unsafe request before the bucket becomes publicly reachable.
D:Encryption at rest protects stored bits against some storage-level threats, but it does not necessarily keep an anonymous caller from reading objects through an API that is expressly authorized by a public bucket policy. The provider can decrypt data for an allowed reader, so the public-read misconfiguration remains a disclosure path. The security architect must constrain who can create such an access policy at the cloud control plane, not rely on encryption alone.
Question 296
A development automation account creates firewall security groups for ephemeral test environments. A bug recently produced a rule allowing administrative access from every Internet address. Security wants automatic group creation to continue, but invalid rules must not reach the cloud control plane. Which action best accomplishes this?
- Give the automation account unrestricted security-group privileges and rely on a daily report
- Validate proposed rules against approved source ranges and port policies before creation, and enforce restrictions using guardrails
- Disable every development environment because automation might create unsafe rules
- Only rename the security groups to include the word 'secure' in their labels
Explanation
Correct Answer
B:A validation layer can check that administrative ports are allowed only from approved management networks, deny catch-all sources, enforce environment-specific restrictions and reject rule requests outside the policy. Implement the checks in the deployment pipeline and, where available, cloud-level policy or permission boundaries so a caller cannot bypass validation with a direct API request. Test valid developer needs and denied examples, and record exceptions under named approval. This retains the efficiency of short-lived test environments while preventing the exact public-admin access failure. Log attempted violations so teams can fix faulty templates rather than silently discarding evidence.
Incorrect Answers
A:Unrestricted security-group permissions increase the impact of an automation bug and allow broad firewall rules to appear immediately. A daily report is detective and can leave a dangerous exposure in place until someone reads it. The security objective is to reject unacceptable configurations at or before creation. Least privilege for the automation identity and preventive controls are more appropriate than granting it unlimited cloud network authority.
C:Shutting down all test environments would halt legitimate development without creating a usable preventive policy for future automation. The firm has a specific faulty security-group pattern that can be constrained while allowing approved configurations. Targeted guardrails and scoped permissions address the blast radius. Emergency suspension might be justified during a live uncontrolled exposure, but it is not the sustainable design change asked for.
D:A name or label has no inherent effect on a firewall rule's source, destination, protocol or port. A resource called 'secure-group' can still permit administrative access from the entire Internet. Inventory tagging can help classification and governance, but enforcement must inspect the actual rule attributes. Cosmetic naming would not stop a faulty automation request from creating an insecure security group.
Question 297
An enterprise scanner discovers a newly disclosed critical vulnerability on an exposed customer portal. The security team wants affected asset owners notified rapidly, with remediation responsibility and verification evidence tracked, while analysts retain the full finding context. What automation is most appropriate?
- Create a workflow that opens an owner-assigned remediation ticket containing asset, advisory, severity, evidence and a validation task
- Send the full scanner report only to a shared SOC mailbox for manual triage before informing asset owners
- Automatically patch every discovered Internet-facing asset without requiring owner validation, change planning or rollback criteria
- Collect the scanner evidence in the SIEM and route owner notification through the next scheduled vulnerability-review meeting.
Explanation
Correct Answer
A:A scanner-to-ticket integration can create a structured record with the affected host, vulnerability identifier, observed version, exposure context and owner, then route it to the right team under a defined service-level policy. Include the technical evidence and a task for post-remediation verification so a completed patch request is not mistaken for closure. Deduplicate repeated detections and track ticket status without overwriting original observations. High-risk findings may also require immediate analyst review and containment decisions. This speeds coordination while preserving the information needed to assess and remediate the exposure responsibly. Escalation criteria should reflect actively exploited conditions and critical service impact.
Incorrect Answers
B:A SOC can use a shared mailbox for triage and to filter noisy scanner output, but the requested process explicitly needs rapid accountable assignment to the affected system owner. Holding every confirmed critical public finding in an unowned central queue can delay remediation and obscure deadlines. A structured owner-specific ticket with asset identity, advisory, evidence and retest requirement provides traceability; analysts may still receive a copy and conduct validation.
C:Automated patching can be appropriate for well-tested standard environments, and it can shorten exposure substantially. But applying it blindly to every scanned asset can interrupt critical applications, especially when detection or asset mapping is imperfect. The question asks for an owner-assigned remediation workflow that preserves finding evidence and verification tasks, not unconditional deployment. A well-governed automation should route evidence and approvals to the correct owner before disruptive changes when warranted.
D:Centralized evidence collection helps analysts correlate repeated findings and avoid losing advisory context. A scheduled meeting may also be appropriate for lower-risk vulnerability planning. The case, however, involves a newly disclosed critical issue on an Internet-exposed customer portal and explicitly requests rapid notification with an accountable owner and verification task. Leaving the finding in a central queue until a routine meeting does not provide immediate assignment or a traceable remediation workflow.
Question 298
A security orchestration platform can instantly disable employee accounts when an unusual login is detected. The same system also controls safety-related operator access at a factory, where an unexpected lockout could stop production. What change makes the automated response safer?
- Disable every account that generates more than one authentication event
- Use an approval record that is reviewed only after the SOAR playbook has already disabled safety-critical operator accounts
- Let the orchestration tool run under a global administrator account for convenience
- Require risk-based approval or a human gate for high-impact account disabling while permitting safe low-impact automation
Explanation
Correct Answer
D:A tiered playbook can automatically collect evidence, open cases, notify responders and apply low-disruption controls while requiring explicit approval before disabling a safety-critical operator identity. The approval should identify a qualified decision-maker, the corroborated risk and a tested restoration path. For ordinary accounts with strong evidence of compromise, policy might permit faster automatic revocation. Test timeouts and escalation behavior so an unavailable approver does not silently create another operational hazard. This balances response speed with the potential safety impact, rather than treating every anomalous login as an identical containment scenario.
Incorrect Answers
A:A single unusual login can occur because of travel, mobile-network changes or identity-provider retry behavior. Blanket disablement based on one signal risks business interruption and may lock out legitimate operators. A more reliable procedure combines corroborating indicators, criticality and account role, with different actions for low-risk and high-impact cases. The team must not confuse speed with correctness when the affected identity supports safety-critical operations.
B:Retrospective approval and review can improve accountability and help tune a response playbook after an action. It cannot prevent the production interruption that may occur when an automation has already locked out a factory operator. The high-impact action needs a pre-execution human decision or a verified safety-preserving exception path. Lower-impact evidence collection and notification can remain automated without exposing the same operational hazard.
C:A global administrator identity gives the orchestration tool more authority than many response actions require, increasing the consequences of a compromised integration or faulty rule. Use narrowly scoped API permissions and protected service credentials. Human gating for consequential operations is separate from privilege minimization; both reduce blast radius. Operational convenience does not justify granting every possible power to an automated workflow.
Question 299
A continuous integration system builds signed release packages from source code. The organization wants to catch embedded credentials, vulnerable third-party dependencies and common source-level defects before any package is approved for production deployment. Which pipeline practice best addresses these risks?
- Run only functional user-interface tests after the release has already been deployed
- Place automated secret scanning, software composition analysis and static checks in the build and promotion gates
- Require the production operator to manually inspect every compiled binary with no supporting tools
- Assume an artifact's code signature proves it has no vulnerabilities or exposed secrets
Explanation
Correct Answer
B:Automated checks can detect accidentally committed credentials, match software dependencies against current advisories and analyze source or build artifacts for risky patterns. Configure actionable failure thresholds and route findings to developers with file, package and version context. A promotion gate can prevent unresolved high-impact issues from reaching production, while documented exceptions manage valid compensating conditions. Signed artifacts should be produced from approved, reproducible inputs and remain traceable to build records. These checks are not guarantees against all vulnerabilities, so dynamic testing and later monitoring can complement them, but they directly target the risks stated before deployment.
Incorrect Answers
A:Functional tests evaluate whether expected features work, not whether secret values are exposed in code or dependencies carry known vulnerabilities. Executing them only after deployment also misses the preventive point where a release could have been withheld. The pipeline should combine correctness checks with security-focused inspection before promotion. User-interface testing remains valuable but cannot substitute for secret and dependency analysis.
C:Manual review alone is difficult to scale and can overlook nested dependencies or secrets embedded in non-obvious files. Human judgment is essential for interpreting findings, yet automated scanners can provide consistent coverage of repeatable patterns across every build. The team should reserve review effort for consequential exceptions and complex weaknesses, not make unsupported manual inspection the only control. Code and dependency provenance should still be recorded.
D:A signature establishes a cryptographic relationship to the signing key and integrity of the signed artifact, subject to validation. It does not inspect whether the underlying source includes a credential or a vulnerable library. Legitimately signed software may still contain exploitable defects. The correct design combines supply-chain integrity with security analysis before signing and releasing. Confusing provenance with code safety would let preventable weaknesses pass through the pipeline.
Question 300
A security orchestration service uses a cloud API to quarantine suspicious virtual machines and an IT service API to open incident tickets. Engineers want the integration to resist credential theft and handle provider outages without losing incident records. What should they prioritize?
- Give both integration keys full organization-wide administrative permissions so API calls never fail
- Hard-code permanent API tokens in every workflow definition so operators can see them
- Disable retry and error handling to prevent duplicate quarantine operations
- Use narrowly scoped workload credentials, secure secret storage, idempotent actions and failure-aware retry or escalation paths
Explanation
Correct Answer
D:Secure orchestration separates each service's authorization, uses scoped short-lived credentials or protected secrets and logs every attempted action. For quarantine, validate the target identity and design calls so repeating the request does not broaden impact; for tickets, use a stable incident identifier to avoid duplicate cases. Detect API timeouts and rate limits, retry safely where appropriate and alert analysts when automation cannot finish. A manual escalation route is essential for urgent containment during provider outages. These controls address both credential blast radius and operational reliability while preserving evidence of what the playbook actually completed.
Incorrect Answers
A:Full organization-wide rights greatly increase the impact of a stolen token or a workflow bug. The quarantine service normally needs limited permissions on identified compute resources, while the ticket system requires separate case-management scopes. Broad rights cannot prevent network outages or invalid requests. Grant only necessary API actions, identify which environment each service may affect and log privileged executions.
B:Hard-coding permanent tokens in playbooks creates copies in source history, export files and operational dashboards. A compromised workflow repository could expose both cloud and ticket-system authority. Retrieve secrets or short-lived workload credentials from a protected integration store, rotate them and restrict who can change workflows. Readability for operators should come from configuration documentation, not visible long-lived credentials embedded in automation definitions.
C:Provider outages, timeouts and transient failures are expected integration conditions, not reasons to discard reliability handling. An API call may succeed even if the response is lost, so blind retries can create duplicate actions. The workflow should track action identifiers and use idempotent operations or deduplication where supported. Disabling all retries can leave hosts unquarantined and tickets missing, while refusing error escalation hides critical failures from responders.