Question 30
To inspect suspicious office attachments without executing them on staff workstations, which solution should be adopted?
- SPF records
- Phishing-resistant MFA
- OAuth consent governance
- Attachment sandboxing
- DMARC enforcement
Explanation
Correct Answer
D:Detonation in an isolated environment reveals behavioral indicators while separating analysis from user endpoints; this mechanism directly supports the requirement to inspect suspicious office attachments without executing them on staff workstations.
Incorrect Answers
A:Receiver-side SPF checking tests the sending IP against published domain policy, not message-body integrity; that is useful when the task is to declare which sending hosts are authorized to use a domain in SMTP envelope identities, not the stated requirement to inspect suspicious office attachments without executing them on staff workstations.
B:Origin-bound authenticators resist adversary-in-the-middle credential replay better than SMS or manually entered OTPs; a team would select it to reduce authentication via stolen passwords and relayable one-time codes, which does not provide the particular result to inspect suspicious office attachments without executing them on staff workstations.
C:Restricting risky app grants prevents token-based access that might bypass ordinary password-reset recovery; its operational purpose is to stop malicious applications from gaining persistent mailbox access through consent, not to achieve the specific requirement to inspect suspicious office attachments without executing them on staff workstations.
E:DMARC combines aligned SPF or DKIM results with domain policy to guide quarantine or rejection decisions; it addresses the different need to specify alignment and disposition for spoofed messages using an organizational domain, leaving the requested ability to inspect suspicious office attachments without executing them on staff workstations unresolved.
Question 31
To reduce authentication via stolen passwords and relayable one-time codes, which of the available controls is suitable?
- Attachment sandboxing
- Mailbox forwarding audit
- Phishing-resistant MFA
- DMARC enforcement
Explanation
Correct Answer
C:Origin-bound authenticators resist adversary-in-the-middle credential replay better than SMS or manually entered OTPs; it supplies the specific control needed to reduce authentication via stolen passwords and relayable one-time codes.
Incorrect Answers
A:Detonation in an isolated environment reveals behavioral indicators while separating analysis from user endpoints; it could help someone trying to inspect suspicious office attachments without executing them on staff workstations, but the problem is instead to reduce authentication via stolen passwords and relayable one-time codes.
B:Review of mailbox rules reveals automatic exfiltration that can continue after the login session ends; that is useful when the task is to find attacker-created external forwarding rules after an account compromise, not the stated requirement to reduce authentication via stolen passwords and relayable one-time codes.
D:DMARC combines aligned SPF or DKIM results with domain policy to guide quarantine or rejection decisions; its operational purpose is to specify alignment and disposition for spoofed messages using an organizational domain, not to achieve the specific requirement to reduce authentication via stolen passwords and relayable one-time codes.
Question 32
To find attacker-created external forwarding rules after an account compromise and to stop malicious applications from gaining persistent mailbox access through consent, which TWO measures should the defender select? Choose TWO.
- DKIM signatures
- OAuth consent governance
- Mailbox forwarding audit
- Phishing-resistant MFA
- DMARC enforcement
Explanation
Correct Answers
B:Restricting risky app grants prevents token-based access that might bypass ordinary password-reset recovery; it satisfies the distinct requirement to stop malicious applications from gaining persistent mailbox access through consent within the multi-control task.
C:Review of mailbox rules reveals automatic exfiltration that can continue after the login session ends; it satisfies the distinct requirement to find attacker-created external forwarding rules after an account compromise within the multi-control task.
Incorrect Answers
A:Cryptographic signatures bind selected headers and the body to a signing domain and survive permitted mail routing; although relevant to detect message header or body alteration after authorized signing, it does not by itself achieve the required task to find attacker-created external forwarding rules after an account compromise and to stop malicious applications from gaining persistent mailbox access through consent.
D:Origin-bound authenticators resist adversary-in-the-middle credential replay better than SMS or manually entered OTPs; a team would select it to reduce authentication via stolen passwords and relayable one-time codes, which does not provide the particular result to find attacker-created external forwarding rules after an account compromise and to stop malicious applications from gaining persistent mailbox access through consent.
E:DMARC combines aligned SPF or DKIM results with domain policy to guide quarantine or rejection decisions; its operational purpose is to specify alignment and disposition for spoofed messages using an organizational domain, not to achieve the specific requirement to find attacker-created external forwarding rules after an account compromise and to stop malicious applications from gaining persistent mailbox access through consent.
Question 33
To stop malicious applications from gaining persistent mailbox access through consent, which option is the direct technical match?
- Attachment sandboxing
- OAuth consent governance
- Mailbox forwarding audit
- Phishing-resistant MFA
Explanation
Correct Answer
B:Restricting risky app grants prevents token-based access that might bypass ordinary password-reset recovery; its relevant protective or investigative effect is to stop malicious applications from gaining persistent mailbox access through consent.
Incorrect Answers
A:Detonation in an isolated environment reveals behavioral indicators while separating analysis from user endpoints; the outcome it supports is to inspect suspicious office attachments without executing them on staff workstations, whereas this scenario asks defenders to stop malicious applications from gaining persistent mailbox access through consent.
C:Review of mailbox rules reveals automatic exfiltration that can continue after the login session ends; it could help someone trying to find attacker-created external forwarding rules after an account compromise, but the problem is instead to stop malicious applications from gaining persistent mailbox access through consent.
D:Origin-bound authenticators resist adversary-in-the-middle credential replay better than SMS or manually entered OTPs; that is useful when the task is to reduce authentication via stolen passwords and relayable one-time codes, not the stated requirement to stop malicious applications from gaining persistent mailbox access through consent.
Question 34
To identify an access point falsely advertising many remembered client network names, which approach should a network defender choose?
- Cloud metadata isolation
- Karma rogue-AP detection
- Evil-twin certificate checking
- CI/CD protected branches
Explanation
Correct Answer
B:Wireless monitoring correlates suspicious probe responses and spoofed SSIDs to expose opportunistic hotspot impersonation; the requested outcome is precisely to identify an access point falsely advertising many remembered client network names.
Incorrect Answers
A:Restricting metadata paths and using hardened token flows reduces credential theft from vulnerable workloads; its mechanism supports limit server-side request forgery from reaching instance identity tokens, while the requested control must be able to identify an access point falsely advertising many remembered client network names.
C:Validating the EAP server certificate and expected name blocks credential leakage to counterfeit infrastructure; although relevant to keep users from authenticating to a lookalike enterprise WLAN, it does not by itself achieve the required task to identify an access point falsely advertising many remembered client network names.
D:Mandatory review and protected refs constrain pipeline modifications that could insert malicious build steps; it could help someone trying to prevent unreviewed changes to production build definitions, but the problem is instead to identify an access point falsely advertising many remembered client network names.
Question 35
To find an unauthorized radio impersonating an office SSID, which method is designed for the task?
- Rogue access-point discovery
- Evil-twin certificate checking
- Cloud metadata isolation
- CI/CD protected branches
- Cloud access key rotation
Explanation
Correct Answer
A:Wireless scanning compares broadcast identifiers and authorized infrastructure to expose unexpected nearby transmitters; this choice fits the scenario because the team must find an unauthorized radio impersonating an office SSID.
Incorrect Answers
B:Validating the EAP server certificate and expected name blocks credential leakage to counterfeit infrastructure; its mechanism supports keep users from authenticating to a lookalike enterprise WLAN, while the requested control must be able to find an unauthorized radio impersonating an office SSID.
C:Restricting metadata paths and using hardened token flows reduces credential theft from vulnerable workloads; the outcome it supports is to limit server-side request forgery from reaching instance identity tokens, whereas this scenario asks defenders to find an unauthorized radio impersonating an office SSID.
D:Mandatory review and protected refs constrain pipeline modifications that could insert malicious build steps; although relevant to prevent unreviewed changes to production build definitions, it does not by itself achieve the required task to find an unauthorized radio impersonating an office SSID.
E:Revocation and replacement cut off further use of the exposed secret; removal of the public copy alone is insufficient; it could help someone trying to replace a credential discovered in a public repository, but the problem is instead to find an unauthorized radio impersonating an office SSID.
Question 36
Employees previously joined public Wi-Fi networks while travelling. Company laptops should no longer associate automatically with a lookalike hotspot broadcasting a remembered public SSID. Which client-side action directly addresses that risk?
- Validate the corporate EAP server certificate
- Disable auto-join for untrusted wireless profiles
- Perform an inventory of authorized office APs
- Disable Wi-Fi Protected Setup on office APs
Explanation
Correct Answer
B:Disabling auto-join for untrusted or public profiles prevents automatic client association with a lookalike SSID. Users can choose a connection deliberately under policy.
Incorrect Answers
A:Validating the EAP server certificate is important for properly configured enterprise 802.1X. It does not stop automatic association with a remembered public wireless network profile.
C:An AP inventory identifies unauthorized access points within monitored coverage. It does not change whether a roaming laptop automatically connects to a previously saved public SSID.
D:Disabling WPS prevents one weak onboarding path on applicable access points. It does not change laptop behavior when a familiar public hotspot name appears.
Question 37
A repository reviewer finds that cloud credentials can be committed to source control. The team wants to detect and block probable access-key secrets during pull-request checks, before they reach the main branch. Which safeguard fits?
- Pre-merge secret scanning with blocking policy
- Cloud access-key rotation after exposure
- Container image vulnerability scanning
- Software bill-of-materials generation
Explanation
Correct Answer
A:Repository and CI secret checks can detect likely tokens or keys in proposed commits and block merge while a reviewer resolves the finding. Scan patterns must be tuned to manage false positives.
Incorrect Answers
B:Rotating a disclosed key is essential after exposure, but it does not prevent a new credential from being merged into a source repository in the first place.
C:Container image scanning finds vulnerabilities or known risks in built images. It does not reliably detect a token embedded in a proposed source-code change before merge.
D:An SBOM records software components and dependencies for supply-chain visibility. It is not a repository policy that searches for embedded cloud access credentials.
Question 38
A web service fetches URLs supplied by users. Attackers might submit alternate hostnames or redirects to reach internal administrative HTTP endpoints. Which application-side safeguard most directly blocks those unintended fetch targets?
- Validate only that each URL uses HTTPS
- Rotate the cloud instance access key
- Enforce a destination allowlist after DNS resolution and redirects
- Send a Content-Security-Policy header to browsers
Explanation
Correct Answer
C:A destination allowlist that checks resolved addresses and revalidates redirects constrains the server-side fetch to approved endpoints, limiting hostname tricks and internal reachability.
Incorrect Answers
A:Checking only the URL scheme still permits requests to private address ranges and internal hosts. HTTPS does not imply that a server-initiated destination is authorized.
B:Rotating an instance credential reduces the life of a leaked secret, but does not stop a vulnerable URL fetcher from reaching forbidden internal HTTP services.
D:Content-Security-Policy is mainly a browser-side document security control. It does not authorize or filter outbound HTTP requests performed by the back-end fetch service.
Question 39
To prevent unreviewed changes to production build definitions, what should defenders select?
- CI/CD protected branches
- Cloud access key rotation
- Signed build provenance
- Dependency pinning
Explanation
Correct Answer
A:Mandatory review and protected refs constrain pipeline modifications that could insert malicious build steps; its relevant protective or investigative effect is to prevent unreviewed changes to production build definitions.
Incorrect Answers
B:Revocation and replacement cut off further use of the exposed secret; removal of the public copy alone is insufficient; its operational purpose is to replace a credential discovered in a public repository, not to achieve the specific requirement to prevent unreviewed changes to production build definitions.
C:Cryptographically verifiable attestations link outputs to a known builder and input revision; applying it would serve verify that deployable artifacts originated from an approved build workflow without directly satisfying the goal to prevent unreviewed changes to production build definitions.
D:Version and integrity locks keep resolution stable until maintainers deliberately approve an update; it addresses the different need to prevent an unexpected upstream package version entering a reproducible build, leaving the requested ability to prevent unreviewed changes to production build definitions unresolved.
Question 40
To verify that deployable artifacts originated from an approved build workflow, which mechanism best fits?
- Cloud access key rotation
- Software bill of materials
- Cloud metadata isolation
- Dependency pinning
- Signed build provenance
Explanation
Correct Answer
E:Cryptographically verifiable attestations link outputs to a known builder and input revision; the requested outcome is precisely to verify that deployable artifacts originated from an approved build workflow.
Incorrect Answers
A:Revocation and replacement cut off further use of the exposed secret; removal of the public copy alone is insufficient; that is useful when the task is to replace a credential discovered in a public repository, not the stated requirement to verify that deployable artifacts originated from an approved build workflow.
B:A component inventory enables targeted exposure analysis instead of guessing where a library was bundled; a team would select it to identify which deployed applications contain a vulnerable dependency, which does not provide the particular result to verify that deployable artifacts originated from an approved build workflow.
C:Restricting metadata paths and using hardened token flows reduces credential theft from vulnerable workloads; its operational purpose is to limit server-side request forgery from reaching instance identity tokens, not to achieve the specific requirement to verify that deployable artifacts originated from an approved build workflow.
D:Version and integrity locks keep resolution stable until maintainers deliberately approve an update; applying it would serve prevent an unexpected upstream package version entering a reproducible build without directly satisfying the goal to verify that deployable artifacts originated from an approved build workflow.