CompTIA Security+ SY0-701 Practice Test 55
Question 540
An employee installs a meeting scheduler that asks for OAuth consent to read every folder in the user's work mailbox. The scheduler only needs calendar availability, and its publisher has not passed the company's app review. The consent screen says the request is technically valid. What security issue should the identity team investigate?
- Approve the requested mailbox read scope because the OAuth consent request was issued by the organization's identity provider
- Shorten token lifetime but retain unlimited mailbox read access without checking the application's publisher
- Require a verified publisher badge before granting the same unrestricted mailbox scope
- Excessive delegated mailbox scope for an untrusted app that could access messages unrelated to scheduling
Explanation
Correct Answer
D:An OAuth consent grant may allow a third-party app to access mailbox content on the user's behalf without another password prompt. Reading every folder is unnecessary for a meeting scheduler that only checks calendar availability, expanding the disclosure boundary to unrelated communications. The team should block or revoke the suspicious grant, inspect issued tokens and access logs, review publisher identity and require least-privilege scopes. Consent governance should limit which permissions users may approve without administrator review. This is authorization-scope abuse and third-party trust risk, not proof that the OAuth protocol itself malfunctioned.
Incorrect Answers
A:An identity provider can present or enforce a valid OAuth consent flow without attesting that the requested scopes are appropriate for the application's purpose. The scheduler needs calendar availability, not read access to every mailbox folder. A malicious or poorly governed application can ask for excessive delegated privileges through otherwise functioning authorization infrastructure. The team should verify the publisher, consent policy and least-privilege permission set before allowing the grant, not equate protocol validity with business approval.
B:Shorter token lifetime can limit some persistence windows, but it does not remove the excessive data access available during each valid token session. The app could read a mailbox immediately after consent. Scope reduction and publisher review are needed before granting permissions, not just a shorter expiry. A short-lived but broad token can read confidential messages immediately after approval.
C:Publisher verification can help establish who controls an application registration and improve accountability, but it does not establish that a meeting scheduler genuinely needs access to all mail folders. Even a well-identified vendor can request permissions broader than its feature set requires. The identity team must evaluate the granted scopes, publisher security posture and approved business purpose together. Simply adding a badge without narrowing delegated access leaves unnecessary exposure to unrelated messages.
Question 541
At a financial-services company, a compliance officer opens a sensitive customer analytics portal using a single sign-on session established earlier that morning. She now requests an export containing every account's identifying and transaction fields. The portal must reduce the risk of a stolen but otherwise valid session without forcing a new login for routine dashboard navigation. What access decision best meets this requirement?
- Require fresh, phishing-resistant step-up authentication immediately before authorizing the bulk export
- Accept the existing SSO assertion because the session was established using MFA earlier that morning
- Ask the officer to click an acknowledgement banner without collecting any new authentication evidence
- Request supervisor workflow approval but automatically trust the existing session identity at export time
Explanation
Correct Answer
A:Step-up authentication ties stronger, current identity assurance to the particularly sensitive export rather than to every ordinary page view. A short-lived authorization decision can require a fresh approved factor or phishing-resistant assertion before the bulk data leaves the portal. This addresses session theft or unattended workstation risk even if the earlier SSO login was legitimate. It should complement role-based authorization, export limits and audit recording, because proving identity again does not establish unlimited business need. A design that scopes the extra challenge to high-impact actions improves usability without allowing an old login event to become permanent proof of present possession.
Incorrect Answers
B:An earlier MFA event is useful context but does not prove that the individual requesting today's export still controls the session. Browser-token theft, session replay or an unattended authenticated workstation could circumvent the original login challenge. Session age is therefore insufficient as the sole control for this exceptional action. The requirement is a fresh assurance decision tied to the export.
C:Acknowledging a warning establishes that a browser user clicked a button, not that the authorized compliance officer possesses an authentication factor. An attacker with a stolen session can acknowledge it equally well. The banner may support policy communication and accountability, but it cannot replace step-up verification when the risk specifically involves the integrity of the existing session.
D:A manager can validate business justification and may be part of an approval workflow, but the manager's consent does not prove who currently controls the portal session. A thief using a valid cookie could exploit an approved request. Both transaction authorization and fresh authentication can be required; neither should be treated as a substitute for the other.
Question 542
During an identity-provider outage at a regional utility, engineers activate a preauthorized emergency cloud administrator account to restore core applications. The account is deliberately independent of normal federation. After service returns, the security lead needs assurance that its use can be reconstructed and the emergency secret cannot remain an unnoticed routine credential. Which arrangement is most defensible?
- Allow engineers to retain the emergency account as their normal shared administrative identity after recovery
- Place the emergency password in a general team wiki that anyone with operations access can read
- Maintain restricted emergency custody, independent activity records, post-incident review and immediate credential rotation
- Send all emergency sign-in events exclusively to the unavailable identity provider and rely on delayed retrospective recovery
Explanation
Correct Answer
C:The emergency account must work when ordinary identity infrastructure is unavailable, so its vault or sealed custody process and activity logging cannot depend exclusively on that infrastructure. Use narrowly authorized retrieval, independent audit records and alerting, time-limited emergency use, a documented incident record and post-recovery review. Rotate or resecure the credential after use and test the workflow periodically. This provides accountability without undermining emergency availability. Rotation alone is insufficient if no one can determine what the account did, while perfect logging alone leaves a publicly known emergency credential available for later abuse. Both custody and post-use closure are essential.
Incorrect Answers
A:An emergency identity becomes substantially riskier when it turns into a standing shared administrator account. Continued use blurs which activity was part of the emergency and bypasses the normal federation and privileged-access controls. Emergency access should be limited to an approved exceptional condition, with its use independently recorded and the credential secured or replaced once primary identity services recover.
B:A team wiki is not a suitable custody boundary for a highly privileged break-glass secret, even when its page requires corporate login. Too many people can discover or duplicate the credential, and such access may depend on the same identity systems that failed. Emergency custody needs narrowly authorized access, usable during outages, with proof of who retrieved or activated it.
D:Logging exclusively through an unavailable provider creates a predictable audit gap during the incident when the highest privileges are active. If administrative actions are not captured elsewhere, restoring federation cannot reconstruct the missing data afterward. Independent cloud control-plane and privileged-session records should remain available, with reconciliation into central monitoring when systems return.
Question 543
A software company runs separate production and development image-processing queues. Both services previously used the same embedded API key, which granted access to queues in either environment. The platform now supports signed workload identity tokens with audience restrictions and distinct service principals per deployment. Which design best prevents a compromised development processor from accessing production queue messages?
- Give each environment a separately authorized workload identity with an audience-bound short-lived token limited to its own queue
- Encrypt the shared permanent API key inside both deployment images using a key stored with the images
- Give the development processor a never-expiring service password that can read every queue but cannot delete any
- Issue temporary tokens to both services but assign the same unrestricted tenant-wide messaging role
Explanation
Correct Answer
A:A distinct workload identity for each deployment lets queue authorization distinguish the development service from the production service, while audience-bound tokens restrict where the issued credentials can be accepted. Short expiration reduces the time available to abuse a stolen token, and narrowly scoped queue permissions limit the effect of a compromised development processor. The identity provider and messaging service must validate token issuer, audience, expiry, and applicable workload claims, not merely the existence of a signed token. This differs from the separate short-lived deployment-job question because here the decisive requirement is an enforced cross-environment trust boundary for long-running service-to-service messaging, not replacing a permanent administrator password in a fifteen-minute pipeline.
Incorrect Answers
B:Encrypting a shared key in deployment artifacts may reduce accidental disclosure in source control, but using the same credential across environments leaves their identities inseparable after decryption. Any compromised development processor that obtains its functioning key could still authenticate as the production service. If the decryption material is co-located with the image, extraction risk rises further. Encryption at rest is useful but cannot replace per-environment identity and fine-grained authorization at the queue.
C:A dedicated password could distinguish this service from unrelated application accounts, but a never-expiring credential remains attractive for theft and reuse. The proposed permissions also cover every queue, which allows the development worker to inspect production messages despite the lack of delete access. Preventing cross-environment reads requires scope enforcement, not just restricting one action. Short-lived workload tokens and distinct service principals offer a narrower blast radius.
D:Temporary tokens help limit credential lifetime, but their scope still matters. Giving both environments the same tenant-wide role allows a stolen development token to read production queues during its valid period. An attacker may need only minutes to copy sensitive messages. The explicit requirement is environment isolation at the messaging authorization boundary, so each workload must receive separately validated identity and permission claims tied only to its intended queue.
Question 544
An engineering company audits permissions to a repository containing a prototype used by a discontinued project. A designer's employment and corporate identity are still valid, but the designer transferred to a different team nine months ago. The former repository owner cannot identify a current task requiring access. What is the appropriate access-review disposition?
- Keep the repository entitlement automatically because the employee's corporate account has not been terminated
- Disable the entire employee identity, including unrelated production tools needed in the new role
- Keep the old entitlement as long as the employee must use MFA and a short-lived session
- Remove the dormant repository grant unless an authorized owner documents a renewed business need
Explanation
Correct Answer
D:Periodic access certification checks whether individual entitlements remain appropriate for a person's current responsibilities. With no demonstrated need or owner approval, the stale repository membership should be removed and the decision documented. If a future assignment requires the code, an authorized owner can grant appropriately scoped access again. This is a least-privilege and permission-lifecycle decision, not employee offboarding. Reviewers should verify inherited group access and cached tokens after removal, because revoking one direct assignment may not close all paths. Automated access-review evidence makes recurring exceptions visible rather than allowing dormant rights to persist indefinitely.
Incorrect Answers
A:Employment status establishes a continuing organization relationship, not a continuing need for every historical project privilege. Leaving project grants untouched allows permission accumulation and creates unnecessary exposure when a valid account is compromised. The resource owner's current authorization decision should be based on actual duties and ownership, not solely the person's employment record.
B:Disabling the whole identity is disproportionate when the employee performs legitimate duties elsewhere. It may interrupt unrelated applications and work without addressing the governance reason that the stale repository grant survived. Access review should revoke the specific obsolete entitlement while preserving other privileges justified by current assignments and recording which owner approved the correction.
C:MFA and session lifetime can lower the chance of account misuse but cannot justify a right that is no longer needed. A strongly authenticated employee could still read or export confidential prototype code outside the person's job. Authorization and authentication solve different questions; access reviews must remove unnecessary privileges even when sign-in security is excellent.
Question 545
An employee authenticates successfully to the corporate identity provider. A signed SAML response reaches an expense application before expiration, but the service rejects it because the audience field names a different service provider. Help-desk staff propose changing the employee password. Which finding actually explains the failed federation flow?
- The employee's password was not verified even though the identity provider reports a successful authentication
- The SAML signing certificate must be replaced whenever the audience differs from the intended service provider
- The assertion's time window is too short even though it was accepted before the stated expiration
- The relying party correctly rejected a signed assertion whose audience did not designate that application
Explanation
Correct Answer
D:SAML audience restriction binds the identity assertion to an intended relying party. A properly signed assertion for another application should not be accepted by this expense system, because otherwise a token could be replayed across services that trust the same identity provider. Compare the configured service-provider entity ID, issuer metadata and actual assertion audience, then correct federation configuration at the appropriate side. Do not disable audience validation or replace passwords to hide the mismatch. Signature and expiration are independent checks; passing them does not override the audience requirement. This is a recipient-binding failure, not evidence that primary authentication was unsuccessful.
Incorrect Answers
A:The identity provider already authenticated the user, so changing credentials would not change the assertion recipient field. A login failure at the service provider may involve trust configuration, audience, recipient, time or signature validation, not the person's password. Troubleshooting should follow which component accepted the authentication and which claim failed at the relying party.
B:A signing certificate helps a relying party verify assertion integrity and issuer authenticity; it does not transform an assertion minted for another service into one valid for this application. Replacing keys without finding a signature failure creates needless operational risk and may break working trusts. The audience restriction must agree with the service provider's configured identifier.
C:The response was presented inside its valid time interval, which makes a clock or expiration hypothesis inconsistent with the given evidence. Even a long-lived signed assertion should be rejected if meant for a different relying party. Extending its lifetime would increase replay exposure without correcting the recipient mismatch identified by the application.
Question 546
A university's enrollment application binds to an LDAP directory through a network shared with outsourced maintenance staff. A packet capture reveals the application's bind password in cleartext, although the password itself is strong. The directory offers encrypted connectivity with a validated internal certificate. Which change most directly addresses the exposure?
- Encode the password with Base64 before sending it over ordinary LDAP
- Use LDAP over authenticated TLS, validate the directory server's certificate and then perform the bind
- Disable TLS certificate validation so any interception appliance can complete the directory connection
- Remove login auditing and account lockout so the application can retry failed plaintext binds more easily
Explanation
Correct Answer
B:Protect the LDAP connection using StartTLS or LDAPS as appropriately configured, and verify the directory server's certificate and expected identity before sending bind credentials. TLS protects against passive interception and helps prevent active impersonation on the shared network. Confirm that plaintext fallback is disabled, certificate trust and name validation are correct, and credentials have only the required directory rights. This addresses the specific captured-password exposure without abandoning needed authentication. Operational testing should confirm both encryption and fail-closed behavior, because enabling TLS while silently accepting untrusted endpoints could still reveal the secret to a man-in-the-middle.
Incorrect Answers
A:Base64 changes the representation of credential bytes but supplies no confidentiality against packet observers. Anyone recording traffic can reverse the encoding and read the same password. The application needs a protected transport channel, not another text encoding. Credential strength does not protect secrets that an observer receives directly in plaintext.
C:Encrypted transport without authenticating the remote directory server can let a malicious intermediary present its own certificate and receive sensitive bind credentials. The network is specifically shared with contractors, increasing the importance of endpoint identity verification. Certificate checks are part of the security property, not a diagnostic obstacle to be bypassed for easier connectivity.
D:Disabling auditing or account lockout changes detection and abuse resistance; it does nothing to encrypt a password already visible in packets. It may make guessing attacks less detectable and weaken directory safeguards. The application should first protect the credential in transit, then tune retry and account policies according to operational needs rather than deleting those controls.
Question 547
A finance department uses robotic process automation to approve routine invoices. The robot necessarily operates with a shared workload identity, but five employees can launch a privileged job through an internal portal. After an unauthorized run, the SIEM shows only the shared robot account. Auditors require an attributable initiating person without breaking the automated service. What should be implemented?
- Digitally sign every job using the same shared service certificate, but do not require individual portal authentication
- Retain detailed job IDs and timestamps but let every operator launch tasks through one common portal username
- Authenticate each operator individually and attach their verified identity and job request to immutable execution records
- Record only the robot service principal in audit events because the platform account executed the privileged action
Explanation
Correct Answer
C:The robot may need a nonhuman credential for system integrations, but each privileged launch should originate from an individually authenticated operator and approved workflow. Bind the operator ID, authorization, request parameters, time, run ID and final outcome into protected logs; correlate those with the shared workload account's actions. This creates a credible accountability chain without creating separate robot credentials for every user. Enforce role-specific launch permissions and investigate modifications to queued jobs so the recorded initiator cannot be replaced later. The shared service principal explains how the action executed; the per-person portal identity explains who authorized or requested it.
Incorrect Answers
A:A shared certificate can protect a job artifact or demonstrate the service that signed it, but it does not distinguish which of five employees requested execution. All operators could trigger identical signatures under that identity. Human-to-workload attribution requires evidence at the submission boundary, before the robot begins acting, rather than relying solely on credentials held by the automation engine.
B:Job IDs and timestamps enable correlation but cannot independently identify an employee if every person enters with the same portal account. Analysts might correlate external chat or attendance records, but the resulting attribution would be speculative. The submission system must record unique authenticated operator identities against approved requests and preserve that binding through job execution.
D:Knowing the robot's service account identifies the component making downstream API calls, not the person who launched a particular invoice approval. Treating those as equivalent would misattribute activity during an investigation and fail the audit requirement. Human authorization records must remain distinct from the workload identity and be linked to each job's execution trail.
Question 548
A security team is tuning a SOAR playbook that currently quarantines a laptop whenever a login originates from an unfamiliar country. Traveling executives frequently generate harmless triggers, while several stolen sessions previously showed matching device health and malicious local processes. The team wants a more discriminating automated decision without losing speed. Which design best fits?
- Continue isolating every host on the single geographic indicator with no additional context
- Remove endpoint and identity telemetry so the orchestration system handles fewer possible conditions
- Apply identical containment to every laptop in the user's department whenever one sign-in alert is raised
- Enrich the alert with token, device posture and endpoint activity before making a policy-controlled containment decision
Explanation
Correct Answer
D:Enriching a SOAR decision with independent identity, device and endpoint signals reduces decisions based on an unreliable single feature. Confirm which token was issued, whether the endpoint is managed and compliant, and whether malicious process behavior supports the identity anomaly. Define thresholds for monitoring, step-up authentication, token revocation or host quarantine, with human approval for ambiguous high-impact actions. Preserve the evidence and the rule outcome so analysts can explain why the playbook acted. Correlation does not guarantee perfect attribution, but it enables a more proportional, auditable response than unconditional isolation from a geographic alert alone.
Incorrect Answers
A:Geographic anomalies are useful clues but may reflect VPN egress, travel or legitimate access patterns. Treating one such signal as conclusive will isolate healthy devices and disrupt essential operations. The playbook should correlate risk indicators, maintain clear thresholds and reserve high-impact automatic containment for evidence meeting the defined decision rule.
B:Discarding independent evidence would make the system simpler but less capable of distinguishing benign travel from account compromise. Identity sign-in details, device compliance and EDR process telemetry answer different questions. Automation can collect them quickly; complexity should be managed through reliable integrations and tested decision logic rather than by removing corroboration.
C:Department-wide containment expands the impact far beyond the affected identity or device and lacks a technical relationship to which endpoint is compromised. It may also take critical workstations offline. The workflow should identify the actual session and host, then apply proportionate response controls. Broader action requires separate evidence of widespread compromise.
Question 549
At a logistics company, a firewall rule provisioning script runs after every branch configuration change. Each execution appends a new 'allow management subnet to monitoring host' rule, even if the exact rule already exists. By Friday, dozens of equivalent entries clutter the policy and complicate review. Which automation property is missing?
- Check only whether the firewall has at least one rule, then append the requested rule regardless of its existing contents
- Reconcile the intended policy with the current policy so rerunning the script does not create duplicate entries
- Filter duplicate firewall syslog events after rule installation, leaving the duplicated firewall configuration untouched
- Schedule a weekly cleanup to remove identical rules while permitting every provisioning run to append another duplicate
Explanation
Correct Answer
B:An idempotent operation has the same intended effect when executed repeatedly as when executed once. The script should identify the required rule, inspect current state and create or update it only if necessary, using reliable identifiers and controlled ordering. That prevents repeated policy objects, improves reviewability and makes recovery from interrupted deployments safer. Rerun behavior should be tested with an existing rule, a missing rule and a partially applied change. Idempotency does not mean never changing policy; it means converging on the requested state without unintended accumulation when the same authorized request is processed again.
Incorrect Answers
A:Checking the presence of any rule is not the same as comparing the specified rule's identity, source, destination and action against existing policy. This approach could add duplicates or skip required new access. Proper automation needs a precise desired-state comparison rather than a superficial nonempty-rule test. The next run might therefore change policy unpredictably even when the intended firewall state was already correct.
C:Deduplicating logs reduces repeated monitoring events but does not remove the redundant enforcement objects. The firewall's configuration remains cluttered, with potential differences in precedence and future audit results. The defect is in how desired configuration changes are applied, so logging adjustments cannot substitute for changing the provisioning logic itself. The duplicate rules would still be evaluated by the firewall during live traffic handling.
D:A cleanup job may reduce clutter later, but it allows avoidable duplicates throughout each day and introduces another automation that can accidentally remove legitimate, subtly different rules. Prevent the creation of redundant state in the first place, and use cleanup only as supplementary hygiene with appropriate approval and verification of rule equivalence.
Question 550
A managed security team automates daily account reviews across ten customer cloud tenants. A developer discovers administrator credentials for every tenant stored in the script repository. The team wants scheduled jobs to keep functioning while preventing one tenant's breach from exposing all others. Which credential architecture should replace the current approach?
- Move the ten administrator passwords into one encrypted file that every tenant's service can decrypt
- Deploy one shared cloud service principal for all ten customers, granting it the minimum read rights needed in each tenant
- Leave passwords in the repository but rotate them yearly and rely on repository access controls
- Use a centrally governed secret service and separate narrowly scoped workload identities for each tenant
Explanation
Correct Answer
D:Separate per-tenant workload identities prevent a job for one customer from automatically gaining permissions across the other nine. A protected secret manager can handle exceptional credentials, access policy, rotation, auditing and retrieval only at runtime; ideally cloud federation avoids static passwords altogether. Grant each automation only the account-review actions it needs, with tenant-specific trust relationships and short-lived tokens. This design contains compromise and makes access revocation and investigation tractable. Central management does not imply a single global administrator credential: segmentation of identity and permissions is essential to preventing cross-tenant blast radius.
Incorrect Answers
A:Encryption at rest is valuable but does not solve shared, broad credential retrieval: if all scripts can decrypt the file, a compromise of one workload may expose all ten tenant accounts. The design should also minimize what each job can access and how long a stolen credential stays useful. Central protection without per-tenant isolation is an incomplete improvement.
B:Reducing administrative rights is useful, but using one principal across independent customer tenants creates a common identity and trust dependency. If its credential or token is compromised in one workflow, the attacker may gain access to the other tenants where that principal is trusted. The design needs separate customer-scoped workload identities and centrally governed secret custody, not merely one broadly reusable identity with reduced role names.
C:Source control access restrictions lower casual exposure but cannot safely govern powerful secrets embedded in commits and copied into builds. Historical versions may preserve older credentials, and annual rotation leaves a long exposure period. The organization should remove them from source history where practical, replace them and move to scoped runtime credentials.