Question 20
To detect unexpected changes to protected executables and configuration and to reduce exposure of reusable domain credentials on supported Windows endpoints, which TWO measures should the defender select? Choose TWO.
- Browser isolation
- Macro execution restrictions
- Credential Guard
- Security awareness reporting
- File integrity monitoring
Explanation
Correct Answers
C:Virtualization-based isolation protects selected secrets from straightforward extraction from the ordinary OS context; it satisfies the distinct requirement to reduce exposure of reusable domain credentials on supported Windows endpoints within the multi-control task.
E:Recorded hashes or metadata baselines reveal unauthorized modifications, with alerts requiring change-context review; it satisfies the distinct requirement to detect unexpected changes to protected executables and configuration within the multi-control task.
Incorrect Answers
A:Running untrusted pages in an isolated environment limits local impact of malicious browser code; that is useful when the task is to keep active web content from directly reaching sensitive desktop processes, not the stated requirement to detect unexpected changes to protected executables and configuration and to reduce exposure of reusable domain credentials on supported Windows endpoints.
B:Office macro policy blocks a common attachment execution path, while permitting appropriately approved documents; a team would select it to stop untrusted documents from starting scripts automatically, which does not provide the particular result to detect unexpected changes to protected executables and configuration and to reduce exposure of reusable domain credentials on supported Windows endpoints.
D:A short, practiced escalation path improves detection before multiple recipients execute the same malicious content; applying it would serve prompt employees to report suspicious delivery attempts promptly without directly satisfying the goal to detect unexpected changes to protected executables and configuration and to reduce exposure of reusable domain credentials on supported Windows endpoints.
Question 21
An administrator connects by RDP from a domain-joined Windows client to a less-trusted domain-joined server. The session must provide user single sign-on without depositing reusable credentials on the remote host. Kerberos prerequisites are met. Which feature best matches?
- File integrity monitoring
- Windows Defender Credential Guard
- Restricted Admin mode for RDP
- Remote Credential Guard for RDP
Explanation
Correct Answer
D:Remote Credential Guard redirects Kerberos requests to the RDP client so credentials remain on that client while the session can use user SSO. It requires a supported Kerberos-based RDP setup.
Incorrect Answers
A:File integrity monitoring detects unexpected changes to selected files and settings. It cannot change how reusable domain credentials are delegated during an RDP login to a remote server.
B:Windows Defender Credential Guard isolates selected credentials on the local endpoint using virtualization-based security. It is not the RDP-specific method that redirects Kerberos requests to the client.
C:Restricted Admin mode avoids passing credentials to the remote host, but remote resource access uses the remote computer identity rather than providing the requested user SSO experience.
Question 22
To prompt employees to report suspicious delivery attempts promptly, which security control is most appropriate?
- Credential Guard
- Security awareness reporting
- Macro execution restrictions
- USB device control
Explanation
Correct Answer
B:A short, practiced escalation path improves detection before multiple recipients execute the same malicious content; the requested outcome is precisely to prompt employees to report suspicious delivery attempts promptly.
Incorrect Answers
A:Virtualization-based isolation protects selected secrets from straightforward extraction from the ordinary OS context; although relevant to reduce exposure of reusable domain credentials on supported Windows endpoints, it does not by itself achieve the required task to prompt employees to report suspicious delivery attempts promptly.
C:Office macro policy blocks a common attachment execution path, while permitting appropriately approved documents; that is useful when the task is to stop untrusted documents from starting scripts automatically, not the stated requirement to prompt employees to report suspicious delivery attempts promptly.
D:Endpoint policy can restrict device classes or read/write access independently of network firewall rules; a team would select it to reduce untrusted removable-storage executable and data risks, which does not provide the particular result to prompt employees to report suspicious delivery attempts promptly.
Question 23
To prevent input from changing the structure of a database query, what would a network defender implement or use?
- CSRF tokens
- Prepared SQL statements
- Contextual output encoding
- SPF records
Explanation
Correct Answer
B:Parameter binding separates query structure from user data and mitigates SQL injection without relying on escaping alone; this choice fits the scenario because the team must prevent input from changing the structure of a database query.
Incorrect Answers
A:An unpredictable server-validated request token distinguishes authorized form submissions from cross-origin requests; the outcome it supports is to block state-changing requests forged from another website, whereas this scenario asks defenders to prevent input from changing the structure of a database query.
C:Encoding for the destination HTML or JavaScript context prevents untrusted bytes being interpreted as markup or code; it could help someone trying to stop stored user content becoming executable script in a browser, but the problem is instead to prevent input from changing the structure of a database query.
D: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 prevent input from changing the structure of a database query.
Question 24
To stop stored user content becoming executable script in a browser, which practice addresses that objective?
- Content Security Policy
- SPF records
- Contextual output encoding
- CSRF tokens
Explanation
Correct Answer
C:Encoding for the destination HTML or JavaScript context prevents untrusted bytes being interpreted as markup or code; this mechanism directly supports the requirement to stop stored user content becoming executable script in a browser.
Incorrect Answers
A:A restrictive browser-enforced policy narrows permitted code sources but does not replace input handling; its mechanism supports limit browser script origins if a page contains an injection weakness, while the requested control must be able to stop stored user content becoming executable script in a browser.
B:Receiver-side SPF checking tests the sending IP against published domain policy, not message-body integrity; the outcome it supports is to declare which sending hosts are authorized to use a domain in SMTP envelope identities, whereas this scenario asks defenders to stop stored user content becoming executable script in a browser.
D:An unpredictable server-validated request token distinguishes authorized form submissions from cross-origin requests; it could help someone trying to block state-changing requests forged from another website, but the problem is instead to stop stored user content becoming executable script in a browser.
Question 25
To block state-changing requests forged from another website, which tool, policy, or technique is appropriate?
- Prepared SQL statements
- CSRF tokens
- Content Security Policy
- Contextual output encoding
- SPF records
Explanation
Correct Answer
B:An unpredictable server-validated request token distinguishes authorized form submissions from cross-origin requests; it supplies the specific control needed to block state-changing requests forged from another website.
Incorrect Answers
A:Parameter binding separates query structure from user data and mitigates SQL injection without relying on escaping alone; the technique works for situations involving prevent input from changing the structure of a database query, rather than this need to block state-changing requests forged from another website.
C:A restrictive browser-enforced policy narrows permitted code sources but does not replace input handling; the outcome it supports is to limit browser script origins if a page contains an injection weakness, whereas this scenario asks defenders to block state-changing requests forged from another website.
D:Encoding for the destination HTML or JavaScript context prevents untrusted bytes being interpreted as markup or code; although relevant to stop stored user content becoming executable script in a browser, it does not by itself achieve the required task to block state-changing requests forged from another website.
E:Receiver-side SPF checking tests the sending IP against published domain policy, not message-body integrity; it could help someone trying to declare which sending hosts are authorized to use a domain in SMTP envelope identities, but the problem is instead to block state-changing requests forged from another website.
Question 26
To limit browser script origins if a page contains an injection weakness, what safeguard would be most applicable?
- Content Security Policy
- Contextual output encoding
- Attachment sandboxing
- Prepared SQL statements
Explanation
Correct Answer
A:A restrictive browser-enforced policy narrows permitted code sources but does not replace input handling; that is why it addresses the operational task to limit browser script origins if a page contains an injection weakness.
Incorrect Answers
B:Encoding for the destination HTML or JavaScript context prevents untrusted bytes being interpreted as markup or code; the technique works for situations involving stop stored user content becoming executable script in a browser, rather than this need to limit browser script origins if a page contains an injection weakness.
C:Detonation in an isolated environment reveals behavioral indicators while separating analysis from user endpoints; its mechanism supports inspect suspicious office attachments without executing them on staff workstations, while the requested control must be able to limit browser script origins if a page contains an injection weakness.
D:Parameter binding separates query structure from user data and mitigates SQL injection without relying on escaping alone; the outcome it supports is to prevent input from changing the structure of a database query, whereas this scenario asks defenders to limit browser script origins if a page contains an injection weakness.
Question 27
To declare which sending hosts are authorized to use a domain in SMTP envelope identities, what is the relevant defensive action?
- Attachment sandboxing
- SPF records
- DMARC enforcement
- Prepared SQL statements
Explanation
Correct Answer
B:Receiver-side SPF checking tests the sending IP against published domain policy, not message-body integrity; its relevant protective or investigative effect is to declare which sending hosts are authorized to use a domain in SMTP envelope identities.
Incorrect Answers
A:Detonation in an isolated environment reveals behavioral indicators while separating analysis from user endpoints; applying it would serve inspect suspicious office attachments without executing them on staff workstations without directly satisfying the goal to declare which sending hosts are authorized to use a domain in SMTP envelope identities.
C:DMARC combines aligned SPF or DKIM results with domain policy to guide quarantine or rejection decisions; the technique works for situations involving specify alignment and disposition for spoofed messages using an organizational domain, rather than this need to declare which sending hosts are authorized to use a domain in SMTP envelope identities.
D:Parameter binding separates query structure from user data and mitigates SQL injection without relying on escaping alone; its mechanism supports prevent input from changing the structure of a database query, while the requested control must be able to declare which sending hosts are authorized to use a domain in SMTP envelope identities.
Question 28
To detect message header or body alteration after authorized signing, which option most directly provides the capability?
- SPF records
- DMARC enforcement
- DKIM signatures
- Contextual output encoding
Explanation
Correct Answer
C:Cryptographic signatures bind selected headers and the body to a signing domain and survive permitted mail routing; the requested outcome is precisely to detect message header or body alteration after authorized signing.
Incorrect Answers
A:Receiver-side SPF checking tests the sending IP against published domain policy, not message-body integrity; its operational purpose is to declare which sending hosts are authorized to use a domain in SMTP envelope identities, not to achieve the specific requirement to detect message header or body alteration after authorized signing.
B:DMARC combines aligned SPF or DKIM results with domain policy to guide quarantine or rejection decisions; applying it would serve specify alignment and disposition for spoofed messages using an organizational domain without directly satisfying the goal to detect message header or body alteration after authorized signing.
D:Encoding for the destination HTML or JavaScript context prevents untrusted bytes being interpreted as markup or code; the technique works for situations involving stop stored user content becoming executable script in a browser, rather than this need to detect message header or body alteration after authorized signing.
Question 29
To specify alignment and disposition for spoofed messages using an organizational domain, which control achieves the target outcome?
- OAuth consent governance
- SPF records
- CSRF tokens
- DMARC enforcement
Explanation
Correct Answer
D:DMARC combines aligned SPF or DKIM results with domain policy to guide quarantine or rejection decisions; this choice fits the scenario because the team must specify alignment and disposition for spoofed messages using an organizational domain.
Incorrect Answers
A:Restricting risky app grants prevents token-based access that might bypass ordinary password-reset recovery; a team would select it to stop malicious applications from gaining persistent mailbox access through consent, which does not provide the particular result to specify alignment and disposition for spoofed messages using an organizational domain.
B:Receiver-side SPF checking tests the sending IP against published domain policy, not message-body integrity; its operational purpose is to declare which sending hosts are authorized to use a domain in SMTP envelope identities, not to achieve the specific requirement to specify alignment and disposition for spoofed messages using an organizational domain.
C:An unpredictable server-validated request token distinguishes authorized form submissions from cross-origin requests; applying it would serve block state-changing requests forged from another website without directly satisfying the goal to specify alignment and disposition for spoofed messages using an organizational domain.
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.