Question 560An insider converts confidential files to long encoded strings and sends them through repeated DNS TXT lookups to an external domain. Why does that solution fit the observed security condition? Attackers can abuse push approval habituation when they possess a user's primary credential. DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. ExplanationCorrect Answer B:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. The practical corrective action is: Detect abnormal DNS request patterns and restrict unapproved DNS resolution paths with policy enforcement. Confirm it by: Correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. Other Answers A:Attackers can abuse push approval habituation when they possess a user's primary credential. In the stated system, DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. C:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. In the stated system, DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. D:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. By contrast, DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel.
Question 561An insider converts confidential files to long encoded strings and sends them through repeated DNS TXT lookups to an external domain. What should the team check before closing this issue? Replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. Correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. Correlate test SCP traffic with destination allowlists and endpoint file access records. Generate a controlled MFA-spam test and verify the configured protective challenge and incident signal. ExplanationCorrect Answer B:Correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. The evidence confirms the intended action: Detect abnormal DNS request patterns and restrict unapproved DNS resolution paths with policy enforcement. It matters because dNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. Other Answers A:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. The relevant acceptance check is to correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. C:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. The failure is checked more directly by a test to correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. D:Attackers can abuse push approval habituation when they possess a user's primary credential. The relevant acceptance check is to correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records.
Question 562An insider converts confidential files to long encoded strings and sends them through repeated DNS TXT lookups to an external domain. Which preventive practice best follows from this incident? Define outbound management-protocol egress policy and alert on unusual remote file copy volumes. Maintain sanctioned cloud storage inventory and data exfiltration response playbooks. Require approved resolver paths and monitor DNS anomaly and data-loss signals. Restrict risky MFA factors and educate users to reject unsolicited approval prompts. ExplanationCorrect Answer C:Require approved resolver paths and monitor DNS anomaly and data-loss signals. This safeguard limits repeat failures because dNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. The direct correction remains: Detect abnormal DNS request patterns and restrict unapproved DNS resolution paths with policy enforcement. Other Answers A:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. A more direct preventive measure is to require approved resolver paths and monitor DNS anomaly and data-loss signals. B:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. Reducing this risk requires a practice to require approved resolver paths and monitor DNS anomaly and data-loss signals. D:Attackers can abuse push approval habituation when they possess a user's primary credential. Reducing this risk requires a practice to require approved resolver paths and monitor DNS anomaly and data-loss signals.
Question 563A compromised engineering host transfers large encrypted archives to a public cloud storage account over normal HTTPS. Which security change most directly addresses the specific failure? Apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. Detect abnormal DNS request patterns and restrict unapproved DNS resolution paths with policy enforcement. Restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. Correlate endpoint sessions and apply CoA to every active network access session authorized for that identity. ExplanationCorrect Answer A:Apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. This action specifically works because tLS encryption protects transit but does not prove that the destination or uploaded data is authorized. Verify with: Replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. Other Answers B:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. A more relevant action is to apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. C:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. The corrective action for this requirement is to apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. D:An endpoint may hold multiple network sessions; changing one NAD's session does not necessarily remove others. The required change instead is to apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns.
Question 564A compromised engineering host transfers large encrypted archives to a public cloud storage account over normal HTTPS. Why does that solution fit the observed security condition? DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. An endpoint may hold multiple network sessions; changing one NAD's session does not necessarily remove others. TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. ExplanationCorrect Answer C:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. The practical corrective action is: Apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. Confirm it by: Replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. Other Answers A:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. By contrast, TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. B:An endpoint may hold multiple network sessions; changing one NAD's session does not necessarily remove others. In the stated system, TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. D:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. By contrast, TLS encryption protects transit but does not prove that the destination or uploaded data is authorized.
Question 565A compromised engineering host transfers large encrypted archives to a public cloud storage account over normal HTTPS. What should the team check before closing this issue? Replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. Enumerate ISE live sessions and verify all mapped sessions receive the intended restricted state. Correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. Correlate test SCP traffic with destination allowlists and endpoint file access records. ExplanationCorrect Answer A:Replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. The evidence confirms the intended action: Apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. It matters because tLS encryption protects transit but does not prove that the destination or uploaded data is authorized. Other Answers B:An endpoint may hold multiple network sessions; changing one NAD's session does not necessarily remove others. Proving this correction calls for a check to replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. C:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. A more meaningful verification is to replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. D:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. The relevant acceptance check is to replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts.
Question 566A compromised engineering host transfers large encrypted archives to a public cloud storage account over normal HTTPS. Which preventive practice best follows from this incident? Require approved resolver paths and monitor DNS anomaly and data-loss signals. Maintain sanctioned cloud storage inventory and data exfiltration response playbooks. Design global session inventory and response orchestration for compromised users/devices. Define outbound management-protocol egress policy and alert on unusual remote file copy volumes. ExplanationCorrect Answer B:Maintain sanctioned cloud storage inventory and data exfiltration response playbooks. This safeguard limits repeat failures because tLS encryption protects transit but does not prove that the destination or uploaded data is authorized. The direct correction remains: Apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. Other Answers A:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. The stronger recurring control is to maintain sanctioned cloud storage inventory and data exfiltration response playbooks. C:An endpoint may hold multiple network sessions; changing one NAD's session does not necessarily remove others. The lasting safeguard is to maintain sanctioned cloud storage inventory and data exfiltration response playbooks. D:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. Reducing this risk requires a practice to maintain sanctioned cloud storage inventory and data exfiltration response playbooks.
Question 567A legacy process sends configuration secrets through an outbound SCP transfer to an unknown server while port 22 is permitted for administration. Which security change most directly addresses the specific failure? Place guests in a restricted guest authorization policy with separate identity and permitted destination scope. Detect abnormal DNS request patterns and restrict unapproved DNS resolution paths with policy enforcement. Apply approved cloud destination and DLP controls and correlate endpoint identity with upload patterns. Restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. ExplanationCorrect Answer D:Restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. This action specifically works because a permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. Verify with: Correlate test SCP traffic with destination allowlists and endpoint file access records. Other Answers A:Guest authentication establishes visitor identity but does not justify unrestricted internal network privileges. The required change instead is to restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. B:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. The required change instead is to restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. C:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. The required change instead is to restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence.
Question 568A legacy process sends configuration secrets through an outbound SCP transfer to an unknown server while port 22 is permitted for administration. Why does that solution fit the observed security condition? DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. Guest authentication establishes visitor identity but does not justify unrestricted internal network privileges. TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. ExplanationCorrect Answer B:A permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. The practical corrective action is: Restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. Confirm it by: Correlate test SCP traffic with destination allowlists and endpoint file access records. Other Answers A:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. In the stated system, a permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. C:Guest authentication establishes visitor identity but does not justify unrestricted internal network privileges. In the stated system, a permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. D:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. In the stated system, a permitted management protocol can also carry unauthorized file transfers when destination scope is too broad.
Question 569A legacy process sends configuration secrets through an outbound SCP transfer to an unknown server while port 22 is permitted for administration. What should the team check before closing this issue? Replay a synthetic sensitive-data upload and confirm user, destination and data classification appear in alerts. Test guest credentials against internet access and protected engineering servers and inspect authorization logs. Correlate test SCP traffic with destination allowlists and endpoint file access records. Correlate unusual high-entropy DNS labels and query volume with endpoint process and egress records. ExplanationCorrect Answer C:Correlate test SCP traffic with destination allowlists and endpoint file access records. The evidence confirms the intended action: Restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. It matters because a permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. Other Answers A:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. The failure is checked more directly by a test to correlate test SCP traffic with destination allowlists and endpoint file access records. B:Guest authentication establishes visitor identity but does not justify unrestricted internal network privileges. The failure is checked more directly by a test to correlate test SCP traffic with destination allowlists and endpoint file access records. D:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. The failure is checked more directly by a test to correlate test SCP traffic with destination allowlists and endpoint file access records.
Question 570A legacy process sends configuration secrets through an outbound SCP transfer to an unknown server while port 22 is permitted for administration. Which preventive practice best follows from this incident? Define outbound management-protocol egress policy and alert on unusual remote file copy volumes. Require approved resolver paths and monitor DNS anomaly and data-loss signals. Review guest account expiry, sponsor approval and isolation policy for every onboarding process. Maintain sanctioned cloud storage inventory and data exfiltration response playbooks. ExplanationCorrect Answer A:Define outbound management-protocol egress policy and alert on unusual remote file copy volumes. This safeguard limits repeat failures because a permitted management protocol can also carry unauthorized file transfers when destination scope is too broad. The direct correction remains: Restrict SSH/SCP egress to approved management destinations and inspect relevant host transfer evidence. Other Answers B:DNS tunneling uses normally allowed name resolution as a low-bandwidth data exfiltration channel. The lasting safeguard is to define outbound management-protocol egress policy and alert on unusual remote file copy volumes. C:Guest authentication establishes visitor identity but does not justify unrestricted internal network privileges. The lasting safeguard is to define outbound management-protocol egress policy and alert on unusual remote file copy volumes. D:TLS encryption protects transit but does not prove that the destination or uploaded data is authorized. The lasting safeguard is to define outbound management-protocol egress policy and alert on unusual remote file copy volumes.