Question 1A hospital's old imaging appliance downloads a disguised update from an unapproved mirror and begins contacting unfamiliar external addresses. What should the engineer change first to meet these conditions? Pin and verify signed package provenance and isolate the deployment until the dependency is investigated. Activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. ExplanationCorrect Answer D:Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. This action specifically works because a trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. Verify with: Correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. Other Answers A:An LLM supply-chain component can execute code or alter prompts outside the model's ordinary content controls. The required change instead is to isolate the appliance and investigate the trojanized update before restoring it from a trusted image. B:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. A more relevant action is to isolate the appliance and investigate the trojanized update before restoring it from a trusted image. C:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. The corrective action for this requirement is to isolate the appliance and investigate the trojanized update before restoring it from a trusted image.
Question 2A hospital's old imaging appliance downloads a disguised update from an unapproved mirror and begins contacting unfamiliar external addresses. Which cause-and-effect relationship determines the best answer? An LLM supply-chain component can execute code or alter prompts outside the model's ordinary content controls. A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. ExplanationCorrect Answer B:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. The practical corrective action is: Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. Confirm it by: Correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. Other Answers A:An LLM supply-chain component can execute code or alter prompts outside the model's ordinary content controls. In the stated system, a trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. C:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. By contrast, a trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. D:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. By contrast, a trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity.
Question 3A hospital's old imaging appliance downloads a disguised update from an unapproved mirror and begins contacting unfamiliar external addresses. Which observable result shows the correction is effective? Correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. Compare authoritative DNS query rates, NXDOMAIN ratios and service availability before and after mitigation. Verify anomalous API operations cease after key revocation and test the new identity's least privileges. Compare SBOM and artifact digests to approved releases and inspect outbound connection telemetry. ExplanationCorrect Answer A:Correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. The evidence confirms the intended action: Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. It matters because a trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. Other Answers B:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. The relevant acceptance check is to correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. C:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. The failure is checked more directly by a test to correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. D:An LLM supply-chain component can execute code or alter prompts outside the model's ordinary content controls. A more meaningful verification is to correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release.
Question 4A hospital's old imaging appliance downloads a disguised update from an unapproved mirror and begins contacting unfamiliar external addresses. What should be institutionalized before future deployments? Remove long-lived embedded API keys and alert on location and permission anomalies. Require validated update signatures and restricted update destinations for clinical appliances. Document upstream DNS mitigation capacity and exercise volumetric incident response. Enforce signed dependency admission and scan model-serving containers and extensions before deployment. ExplanationCorrect Answer B:Require validated update signatures and restricted update destinations for clinical appliances. This safeguard limits repeat failures because a trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. The direct correction remains: Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. Other Answers A:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. A more direct preventive measure is to require validated update signatures and restricted update destinations for clinical appliances. C:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. Reducing this risk requires a practice to require validated update signatures and restricted update destinations for clinical appliances. D:An LLM supply-chain component can execute code or alter prompts outside the model's ordinary content controls. The stronger recurring control is to require validated update signatures and restricted update destinations for clinical appliances.
Question 5A cloud billing tenant has no malware alerts but its API calls originate from a leaked automation token in an overseas region. What should the engineer change first to meet these conditions? Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. Activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. Move future automation tokens into a protected vault but leave the compromised API credential enabled until the next maintenance window. ExplanationCorrect Answer A:Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. This action specifically works because compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. Verify with: Verify anomalous API operations cease after key revocation and test the new identity's least privileges. Other Answers B:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. A more relevant action is to revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. C:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. The corrective action for this requirement is to revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. D:Move future automation tokens into a protected vault but leave the compromised API credential enabled until the next maintenance window. A vault improves future credential hygiene but cannot stop active abuse of the already-leaked token without immediate revocation. The case-specific answer is: Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity.
Question 6A cloud billing tenant has no malware alerts but its API calls originate from a leaked automation token in an overseas region. Which cause-and-effect relationship determines the best answer? Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. A bearer token grants authority to whoever possesses it, regardless of transport encryption after disclosure. Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. ExplanationCorrect Answer D:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. The practical corrective action is: Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. Confirm it by: Verify anomalous API operations cease after key revocation and test the new identity's least privileges. Other Answers A:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. In the stated system, compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. B:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. By contrast, compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. C:A bearer token grants authority to whoever possesses it, regardless of transport encryption after disclosure. By contrast, compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint.
Question 7A cloud billing tenant has no malware alerts but its API calls originate from a leaked automation token in an overseas region. Which observable result shows the correction is effective? Correlate the update package hash, EDR process tree and DNS flows with a vendor-signed release. Verify anomalous API operations cease after key revocation and test the new identity's least privileges. Compare authoritative DNS query rates, NXDOMAIN ratios and service availability before and after mitigation. Search new logs and verify no token values appear, then test the rotated token's limited scope. ExplanationCorrect Answer B:Verify anomalous API operations cease after key revocation and test the new identity's least privileges. The evidence confirms the intended action: Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. It matters because compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. Other Answers A:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. The relevant acceptance check is to verify anomalous API operations cease after key revocation and test the new identity's least privileges. C:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. The failure is checked more directly by a test to verify anomalous API operations cease after key revocation and test the new identity's least privileges. D:A bearer token grants authority to whoever possesses it, regardless of transport encryption after disclosure. A more meaningful verification is to verify anomalous API operations cease after key revocation and test the new identity's least privileges.
Question 8A cloud billing tenant has no malware alerts but its API calls originate from a leaked automation token in an overseas region. What should be institutionalized before future deployments? Remove long-lived embedded API keys and alert on location and permission anomalies. Require validated update signatures and restricted update destinations for clinical appliances. Document upstream DNS mitigation capacity and exercise volumetric incident response. Use scoped expiring credentials and automated secret-scanning for all orchestration scripts. ExplanationCorrect Answer A:Remove long-lived embedded API keys and alert on location and permission anomalies. This safeguard limits repeat failures because compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. The direct correction remains: Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. Other Answers B:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. The lasting safeguard is to remove long-lived embedded API keys and alert on location and permission anomalies. C:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. The stronger recurring control is to remove long-lived embedded API keys and alert on location and permission anomalies. D:A bearer token grants authority to whoever possesses it, regardless of transport encryption after disclosure. A more direct preventive measure is to remove long-lived embedded API keys and alert on location and permission anomalies.
Question 9An edge DNS service receives high-volume distributed queries for random names while the web application remains healthy. What should the engineer change first to meet these conditions? Isolate the appliance and investigate the trojanized update before restoring it from a trusted image. Activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. Revoke the exposed key, review API audit records and replace it with a scoped short-lived workload identity. Replace string concatenation with parameterized queries and keep database privileges limited to required tables. ExplanationCorrect Answer B:Activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. This action specifically works because distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. Verify with: Compare authoritative DNS query rates, NXDOMAIN ratios and service availability before and after mitigation. Other Answers A:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. The corrective action for this requirement is to activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. C:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. The required change instead is to activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. D:SQL injection occurs when untrusted input changes the syntax of a query rather than remaining a bound value. The corrective action for this requirement is to activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters.
Question 10An edge DNS service receives high-volume distributed queries for random names while the web application remains healthy. Which cause-and-effect relationship determines the best answer? Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. SQL injection occurs when untrusted input changes the syntax of a query rather than remaining a bound value. ExplanationCorrect Answer A:Distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. The practical corrective action is: Activate rate controls and upstream DDoS mitigation at the DNS service rather than tuning application SQL filters. Confirm it by: Compare authoritative DNS query rates, NXDOMAIN ratios and service availability before and after mitigation. Other Answers B:Compromised cloud credentials can directly invoke privileged APIs without malware executing on a managed endpoint. By contrast, distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. C:A trojan uses apparently legitimate software delivery to execute malicious code; network containment limits lateral activity. In the stated system, distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application. D:SQL injection occurs when untrusted input changes the syntax of a query rather than remaining a bound value. In the stated system, distributed DNS query floods exhaust resolver or authoritative capacity before normal web traffic reaches the application.