ECCouncil 312-38 (Certified Network Defender) Practice Test 13

Question 120

To identify a signed-in user to an application built on OAuth 2.0, what should defenders select?

  1. Single sign-on federation
  2. OpenID Connect ID token
  3. Just-in-time access
  4. SAML assertion validation
  5. Privileged access management

Explanation

Correct Answer

B:

OIDC adds an identity layer with verifiable ID tokens; OAuth access tokens alone express delegation; this mechanism directly supports the requirement to identify a signed-in user to an application built on OAuth 2.0.

Incorrect Answers

A:

Federation exchanges signed identity assertions so apps do not each require a separate password; that is useful when the task is to let multiple internal applications trust one authentication session, not the stated requirement to identify a signed-in user to an application built on OAuth 2.0.

C:

Temporary privileged grants reduce standing access while preserving time-limited operational capability; its operational purpose is to activate elevated permissions only for a bounded maintenance interval, not to achieve the specific requirement to identify a signed-in user to an application built on OAuth 2.0.

D:

Signed assertions carry authentication and attribute statements that the service provider must verify; applying it would serve authenticate a browser-based enterprise application using trusted IdP claims without directly satisfying the goal to identify a signed-in user to an application built on OAuth 2.0.

E:

PAM can vault secrets, approve elevation and record privileged activity independently of user login; it addresses the different need to broker and audit sessions to network device administrator accounts, leaving the requested ability to identify a signed-in user to an application built on OAuth 2.0 unresolved.

Question 121

To synchronize user account creation and removal across SaaS applications, what should defenders select?

  1. Privileged access management
  2. Single sign-on federation
  3. OpenID Connect ID token
  4. SCIM provisioning

Explanation

Correct Answer

D:

Standardized identity APIs automate lifecycle changes without making an authentication assertion; it supplies the specific control needed to synchronize user account creation and removal across SaaS applications.

Incorrect Answers

A:

PAM can vault secrets, approve elevation and record privileged activity independently of user login; it could help someone trying to broker and audit sessions to network device administrator accounts, but the problem is instead to synchronize user account creation and removal across SaaS applications.

B:

Federation exchanges signed identity assertions so apps do not each require a separate password; that is useful when the task is to let multiple internal applications trust one authentication session, not the stated requirement to synchronize user account creation and removal across SaaS applications.

C:

OIDC adds an identity layer with verifiable ID tokens; OAuth access tokens alone express delegation; a team would select it to identify a signed-in user to an application built on OAuth 2.0, which does not provide the particular result to synchronize user account creation and removal across SaaS applications.

Question 122

To encrypt bulk backup data efficiently with one protected secret key, which mechanism best fits?

  1. Symmetric encryption
  2. Hash-based integrity verification
  3. Asymmetric key exchange
  4. Digital signatures

Explanation

Correct Answer

A:

Symmetric algorithms use the same shared key family for encryption and decryption of large data volumes; that is why it addresses the operational task to encrypt bulk backup data efficiently with one protected secret key.

Incorrect Answers

B:

Cryptographic hashes reveal changed content when the expected digest itself is received through a trusted channel; it could help someone trying to detect accidental or malicious modification of a downloaded file, but the problem is instead to encrypt bulk backup data efficiently with one protected secret key.

C:

Public-key cryptography supports authenticated or unauthenticated agreement depending on the chosen protocol; that is useful when the task is to establish session secrets without pre-sharing the same encryption key, not the stated requirement to encrypt bulk backup data efficiently with one protected secret key.

D:

A signature uses the private signing key and verification under a trusted public key; a team would select it to let recipients verify a publisher's identity and message integrity, which does not provide the particular result to encrypt bulk backup data efficiently with one protected secret key.

Question 123

To establish session secrets without pre-sharing the same encryption key, which measure best meets the requirement?

  1. Digital signatures
  2. Asymmetric key exchange
  3. Hash-based integrity verification
  4. PKI certificate chain

Explanation

Correct Answer

B:

Public-key cryptography supports authenticated or unauthenticated agreement depending on the chosen protocol; its relevant protective or investigative effect is to establish session secrets without pre-sharing the same encryption key.

Incorrect Answers

A:

A signature uses the private signing key and verification under a trusted public key; the outcome it supports is to let recipients verify a publisher's identity and message integrity, whereas this scenario asks defenders to establish session secrets without pre-sharing the same encryption key.

C:

Cryptographic hashes reveal changed content when the expected digest itself is received through a trusted channel; it could help someone trying to detect accidental or malicious modification of a downloaded file, but the problem is instead to establish session secrets without pre-sharing the same encryption key.

D:

Certificate path and hostname validation tie a presented key to an accepted trust anchor; that is useful when the task is to prove a remote gateway's public key belongs to an expected identity, not the stated requirement to establish session secrets without pre-sharing the same encryption key.

Question 124

To detect accidental or malicious modification of a downloaded file, what control should be selected?

  1. Asymmetric key exchange
  2. Hash-based integrity verification
  3. Certificate revocation checking
  4. Symmetric encryption

Explanation

Correct Answer

B:

Cryptographic hashes reveal changed content when the expected digest itself is received through a trusted channel; the requested outcome is precisely to detect accidental or malicious modification of a downloaded file.

Incorrect Answers

A:

Public-key cryptography supports authenticated or unauthenticated agreement depending on the chosen protocol; its mechanism supports establish session secrets without pre-sharing the same encryption key, while the requested control must be able to detect accidental or malicious modification of a downloaded file.

C:

CRL or OCSP status can inform whether a certificate remains authorized before expiry; although relevant to reject an otherwise valid certificate known to be compromised, it does not by itself achieve the required task to detect accidental or malicious modification of a downloaded file.

D:

Symmetric algorithms use the same shared key family for encryption and decryption of large data volumes; it could help someone trying to encrypt bulk backup data efficiently with one protected secret key, but the problem is instead to detect accidental or malicious modification of a downloaded file.

Question 125

To authenticate a message between two parties that share a secret, which security control is most appropriate?

  1. HMAC authentication
  2. Certificate revocation checking
  3. PKI certificate chain
  4. Forward secrecy
  5. Symmetric encryption

Explanation

Correct Answer

A:

A keyed hash provides integrity and source authenticity to key holders, unlike an unkeyed checksum; this choice fits the scenario because the team must authenticate a message between two parties that share a secret.

Incorrect Answers

B:

CRL or OCSP status can inform whether a certificate remains authorized before expiry; its mechanism supports reject an otherwise valid certificate known to be compromised, while the requested control must be able to authenticate a message between two parties that share a secret.

C:

Certificate path and hostname validation tie a presented key to an accepted trust anchor; the outcome it supports is to prove a remote gateway's public key belongs to an expected identity, whereas this scenario asks defenders to authenticate a message between two parties that share a secret.

D:

Ephemeral key agreement prevents retrospective session decryption from one static-key compromise alone; although relevant to protect recorded encrypted sessions if a server's long-term key later leaks, it does not by itself achieve the required task to authenticate a message between two parties that share a secret.

E:

Symmetric algorithms use the same shared key family for encryption and decryption of large data volumes; it could help someone trying to encrypt bulk backup data efficiently with one protected secret key, but the problem is instead to authenticate a message between two parties that share a secret.

Question 126

To let recipients verify a publisher's identity and message integrity, what would a security architect implement or use?

  1. Authenticated encryption
  2. Certificate revocation checking
  3. Digital signatures
  4. HMAC authentication

Explanation

Correct Answer

C:

A signature uses the private signing key and verification under a trusted public key; this mechanism directly supports the requirement to let recipients verify a publisher's identity and message integrity.

Incorrect Answers

A:

AEAD modes such as AES-GCM combine confidentiality with integrity tags under appropriate nonce handling; it addresses the different need to prevent unnoticed ciphertext tampering as well as disclosure, leaving the requested ability to let recipients verify a publisher's identity and message integrity unresolved.

B:

CRL or OCSP status can inform whether a certificate remains authorized before expiry; the technique works for situations involving reject an otherwise valid certificate known to be compromised, rather than this need to let recipients verify a publisher's identity and message integrity.

D:

A keyed hash provides integrity and source authenticity to key holders, unlike an unkeyed checksum; the outcome it supports is to authenticate a message between two parties that share a secret, whereas this scenario asks defenders to let recipients verify a publisher's identity and message integrity.

Question 127

To prove a remote gateway's public key belongs to an expected identity, which practice addresses that objective?

  1. HMAC authentication
  2. Certificate revocation checking
  3. Symmetric encryption
  4. PKI certificate chain

Explanation

Correct Answer

D:

Certificate path and hostname validation tie a presented key to an accepted trust anchor; it supplies the specific control needed to prove a remote gateway's public key belongs to an expected identity.

Incorrect Answers

A:

A keyed hash provides integrity and source authenticity to key holders, unlike an unkeyed checksum; applying it would serve authenticate a message between two parties that share a secret without directly satisfying the goal to prove a remote gateway's public key belongs to an expected identity.

B:

CRL or OCSP status can inform whether a certificate remains authorized before expiry; it addresses the different need to reject an otherwise valid certificate known to be compromised, leaving the requested ability to prove a remote gateway's public key belongs to an expected identity unresolved.

C:

Symmetric algorithms use the same shared key family for encryption and decryption of large data volumes; the technique works for situations involving encrypt bulk backup data efficiently with one protected secret key, rather than this need to prove a remote gateway's public key belongs to an expected identity.

Question 128

To reject an otherwise valid certificate known to be compromised, which tool, policy, or technique is appropriate?

  1. PKI certificate chain
  2. Certificate revocation checking
  3. Digital signatures
  4. Authenticated encryption

Explanation

Correct Answer

B:

CRL or OCSP status can inform whether a certificate remains authorized before expiry; that is why it addresses the operational task to reject an otherwise valid certificate known to be compromised.

Incorrect Answers

A:

Certificate path and hostname validation tie a presented key to an accepted trust anchor; its operational purpose is to prove a remote gateway's public key belongs to an expected identity, not to achieve the specific requirement to reject an otherwise valid certificate known to be compromised.

C:

A signature uses the private signing key and verification under a trusted public key; it addresses the different need to let recipients verify a publisher's identity and message integrity, leaving the requested ability to reject an otherwise valid certificate known to be compromised unresolved.

D:

AEAD modes such as AES-GCM combine confidentiality with integrity tags under appropriate nonce handling; the technique works for situations involving prevent unnoticed ciphertext tampering as well as disclosure, rather than this need to reject an otherwise valid certificate known to be compromised.

Question 129

To protect recorded encrypted sessions if a server's long-term key later leaks, what safeguard would be most applicable?

  1. Forward secrecy
  2. Authenticated encryption
  3. PKI certificate chain
  4. Key rotation policy

Explanation

Correct Answer

A:

Ephemeral key agreement prevents retrospective session decryption from one static-key compromise alone; its relevant protective or investigative effect is to protect recorded encrypted sessions if a server's long-term key later leaks.

Incorrect Answers

B:

AEAD modes such as AES-GCM combine confidentiality with integrity tags under appropriate nonce handling; its operational purpose is to prevent unnoticed ciphertext tampering as well as disclosure, not to achieve the specific requirement to protect recorded encrypted sessions if a server's long-term key later leaks.

C:

Certificate path and hostname validation tie a presented key to an accepted trust anchor; applying it would serve prove a remote gateway's public key belongs to an expected identity without directly satisfying the goal to protect recorded encrypted sessions if a server's long-term key later leaks.

D:

Scheduled replacement reduces lifetime and facilitates incident response to suspected key compromise; it addresses the different need to limit cryptographic exposure after long-lived keys become widely deployed, leaving the requested ability to protect recorded encrypted sessions if a server's long-term key later leaks unresolved.

Question 130

To prevent unnoticed ciphertext tampering as well as disclosure and to limit cryptographic exposure after long-lived keys become widely deployed, which TWO measures should the defender select? Choose TWO.

  1. Security module key storage
  2. HMAC authentication
  3. Key rotation policy
  4. Forward secrecy
  5. Authenticated encryption

Explanation

Correct Answers

C:

Scheduled replacement reduces lifetime and facilitates incident response to suspected key compromise; its contribution to the combined design is specifically to limit cryptographic exposure after long-lived keys become widely deployed.

E:

AEAD modes such as AES-GCM combine confidentiality with integrity tags under appropriate nonce handling; its contribution to the combined design is specifically to prevent unnoticed ciphertext tampering as well as disclosure.

Incorrect Answers

A:

An HSM performs protected cryptographic operations with restricted key export paths; that is useful when the task is to keep high-value signing keys out of normal server process memory, not the stated requirement to prevent unnoticed ciphertext tampering as well as disclosure and to limit cryptographic exposure after long-lived keys become widely deployed.

B:

A keyed hash provides integrity and source authenticity to key holders, unlike an unkeyed checksum; a team would select it to authenticate a message between two parties that share a secret, which does not provide the particular result to prevent unnoticed ciphertext tampering as well as disclosure and to limit cryptographic exposure after long-lived keys become widely deployed.

D:

Ephemeral key agreement prevents retrospective session decryption from one static-key compromise alone; applying it would serve protect recorded encrypted sessions if a server's long-term key later leaks without directly satisfying the goal to prevent unnoticed ciphertext tampering as well as disclosure and to limit cryptographic exposure after long-lived keys become widely deployed.

Certified Network Defender (312-38) Practice Tests