General Security Concepts

Review questions

Summary: General Security Concepts

General security is not reducible to the device in view. A server-room badge reader combines physical and technical control; its log detects, while a lock prevents. In payroll, authentication establishes the session, authorization decides whether that identity may access a specific record, and accounting attributes the action. Passing MFA therefore does not permit editing a colleague's bank details. If a policy service fails during an emergency, compare denial with a predesigned narrow, monitored path; do not grant everyone access. For a payment-firewall change, record the required flow and test both allowed and denied paths before deployment. Define a measurable error threshold and rollback authority. After restoring rules, verify a successful payment: command completion is not service recovery. Choose cryptography by objective: TLS with a hostname-validated server certificate for protected transport, a signature for integrity and origin, slow derivation with a unique salt for passwords, and a separate key for backups. A signature does not conceal content, and renewing a server certificate cannot recover a backup whose decryption key is lost. This is a training review for SY0-701 skills, not an official exam form. Compare physical safeguards at testable boundaries: visitor authorization, tailgating denial, and open-door alerting. A bounded decoy detects unusual touches but does not replace real access control. Close a gap with test evidence, owner, and deadline—not a count of purchased devices.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1A badge reader unlocks a server room and logs passage. Which two control categories dominate?
  2. Question 2An attacker changes a payment amount without disclosure or outage. Which goal fails first?
  3. Question 3An employee passes MFA but cannot open a colleague's record. Which function denies it?
  4. Question 4Device posture changes during a session and a sensitive request must be re-evaluated. Who computes the decision?
  5. Question 5A firewall update may interrupt payments. What change-request detail matters before approval?
  6. Question 6A deny rule is added below a broader allow rule. What is likely?
  7. Question 7Payment errors reach 3% for five minutes after change; rollback threshold is 2%. What next?
  8. Question 8A TLS canary works for 99% but a critical payment client fails. What is appropriate?
  9. Question 9An API needs protected traffic and server identity. Which option fits?
  10. Question 10One byte changes in a signed file. What should verification report?
  11. Question 11A file hash is on the same attacker-modified page as the file. What is not proven?
  12. Question 12Passwords use fast unsalted SHA-256. What is the appropriate repair?
  13. Question 13A visitor tailgates into a server room while a camera records. Which repair addresses the cause?
  14. Question 14A noisy door alarm was disconnected. What is the first gap-analysis step?
  15. Question 15Which decoy design avoids creating a new attack path?
  16. Question 16After revising visitor reception, which evidence best closes the gap?