McAfee-Secured Website

Exam Bundle

Exam Code: SC-900

Exam Name Microsoft Security, Compliance, and Identity Fundamentals

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Security, Compliance, and Identity Fundamentals

Microsoft SC-900 Bundle $44.99

100% Microsoft SC-900 Guaranteed Success With Testking Training Materials

Get Real SC-900 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    SC-900 Questions & Answers

    259 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual SC-900 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • SC-900 Video Course

    SC-900 Video Course

    147 Video Lectures

    SC-900 Video Course is developed by Microsoft Professionals to help you pass the SC-900 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Security, Compliance, and Identity Fundamentals exam.
  • Study Guide

    SC-900 Study Guide

    413 PDF Pages

    Developed by industry experts, this 413-page guide spells out in painstaking detail all of the information you need to ace SC-900 exam.

Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    259 Questions

    $124.99
  • SC-900 Video Course

    Video Course

    147 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    413 PDF Pages

    $29.99

Microsoft SC-900 Practice Test 61

Question 600

For Brightstone Legal, the security review of matter files and sensitive case records highlights this gap: A company stores its application TLS certificates in an untracked shared drive and misses planned expiration dates. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An authorized signing request succeeds without exposing private key material to the application caller.
  2. A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails.
  3. The approved certificate is available to the application and expiration monitoring identifies the next renewal boundary.
  4. A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Explanation

Correct Answer

C:

The approved certificate is available to the application and expiration monitoring identifies the next renewal boundary. This is the relevant proof because it tests whether the selected corrective action (Manage supported certificate lifecycle and monitoring through Azure Key Vault where appropriate) addressed the initiating problem (A company stores its application TLS certificates in an untracked shared drive and misses planned expiration dates) in Brightstone Legal's matter files and sensitive case records environment, not merely whether a task was marked complete.

Incorrect Answers

A:

An authorized signing request succeeds without exposing private key material to the application caller. This is useful evidence for a different situation (A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text) and action (Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access). For the reported issue at Brightstone Legal, it does not establish the required outcome: The approved certificate is available to the application and expiration monitoring identifies the next renewal boundary.

B:

A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails. This is useful evidence for a different situation (An application reads sensitive Key Vault secrets over public network paths although policy requires private network access) and action (Configure an appropriate Azure Private Endpoint and network access restrictions for the vault). For the reported issue at Brightstone Legal, it does not establish the required outcome: The approved certificate is available to the application and expiration monitoring identifies the next renewal boundary.

D:

A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents. This is useful evidence for a different situation (A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions) and action (Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model). For the reported issue at Brightstone Legal, it does not establish the required outcome: The approved certificate is available to the application and expiration monitoring identifies the next renewal boundary.

Question 601

For Stonehaven Logistics, the security review of warehouse scheduling and shipping records highlights this gap: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. Which action BEST addresses the described security, identity, or compliance gap?

  1. Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment.
  2. Configure an appropriate Azure Private Endpoint and network access restrictions for the vault.
  3. Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites.
  4. Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access.

Explanation

Correct Answer

D:

Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access. This directly addresses the observed weakness: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. For Stonehaven Logistics and its warehouse scheduling and shipping records, a meaningful acceptance check would be: An authorized signing request succeeds without exposing private key material to the application caller.

Incorrect Answers

A:

Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment. This addresses a different security or governance gap: A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs. For Stonehaven Logistics and its warehouse scheduling and shipping records, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

B:

Configure an appropriate Azure Private Endpoint and network access restrictions for the vault. This addresses a different security or governance gap: An application reads sensitive Key Vault secrets over public network paths although policy requires private network access. For Stonehaven Logistics and its warehouse scheduling and shipping records, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

C:

Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites. This addresses a different security or governance gap: An operations team needs SSH access to a private Linux VM but incorrectly assumes Azure Bastion is only for Windows desktop sessions. For Stonehaven Logistics and its warehouse scheduling and shipping records, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

Question 602

For Stonehaven Logistics, the security review of warehouse scheduling and shipping records highlights this gap: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An authorized signing request succeeds without exposing private key material to the application caller.
  2. A permitted administrator starts a secure SSH session without exposing an inbound public SSH endpoint.
  3. An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented.
  4. A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails.

Explanation

Correct Answer

A:

An authorized signing request succeeds without exposing private key material to the application caller. This is the relevant proof because it tests whether the selected corrective action (Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access) addressed the initiating problem (A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text) in Stonehaven Logistics's warehouse scheduling and shipping records environment, not merely whether a task was marked complete.

Incorrect Answers

B:

A permitted administrator starts a secure SSH session without exposing an inbound public SSH endpoint. This is useful evidence for a different situation (An operations team needs SSH access to a private Linux VM but incorrectly assumes Azure Bastion is only for Windows desktop sessions) and action (Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites). For the reported issue at Stonehaven Logistics, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

C:

An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented. This is useful evidence for a different situation (A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs) and action (Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment). For the reported issue at Stonehaven Logistics, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

D:

A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails. This is useful evidence for a different situation (An application reads sensitive Key Vault secrets over public network paths although policy requires private network access) and action (Configure an appropriate Azure Private Endpoint and network access restrictions for the vault). For the reported issue at Stonehaven Logistics, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

Question 603

An engineer reviewing Seabright Municipal Works and its public-sector records and operations services documents: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. Which action BEST addresses the described security, identity, or compliance gap?

  1. Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites.
  2. Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment.
  3. Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access.
  4. Configure an appropriate Azure Private Endpoint and network access restrictions for the vault.

Explanation

Correct Answer

C:

Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access. This directly addresses the observed weakness: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. For Seabright Municipal Works and its public-sector records and operations, a meaningful acceptance check would be: An authorized signing request succeeds without exposing private key material to the application caller.

Incorrect Answers

A:

Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites. This addresses a different security or governance gap: An operations team needs SSH access to a private Linux VM but incorrectly assumes Azure Bastion is only for Windows desktop sessions. For Seabright Municipal Works and its public-sector records and operations, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

B:

Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment. This addresses a different security or governance gap: A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs. For Seabright Municipal Works and its public-sector records and operations, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

D:

Configure an appropriate Azure Private Endpoint and network access restrictions for the vault. This addresses a different security or governance gap: An application reads sensitive Key Vault secrets over public network paths although policy requires private network access. For Seabright Municipal Works and its public-sector records and operations, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

Question 604

An engineer reviewing Seabright Municipal Works and its public-sector records and operations services documents: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. A permitted administrator starts a secure SSH session without exposing an inbound public SSH endpoint.
  2. A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails.
  3. An authorized signing request succeeds without exposing private key material to the application caller.
  4. An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented.

Explanation

Correct Answer

C:

An authorized signing request succeeds without exposing private key material to the application caller. This is the relevant proof because it tests whether the selected corrective action (Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access) addressed the initiating problem (A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text) in Seabright Municipal Works's public-sector records and operations environment, not merely whether a task was marked complete.

Incorrect Answers

A:

A permitted administrator starts a secure SSH session without exposing an inbound public SSH endpoint. This is useful evidence for a different situation (An operations team needs SSH access to a private Linux VM but incorrectly assumes Azure Bastion is only for Windows desktop sessions) and action (Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites). For the reported issue at Seabright Municipal Works, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

B:

A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails. This is useful evidence for a different situation (An application reads sensitive Key Vault secrets over public network paths although policy requires private network access) and action (Configure an appropriate Azure Private Endpoint and network access restrictions for the vault). For the reported issue at Seabright Municipal Works, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

D:

An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented. This is useful evidence for a different situation (A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs) and action (Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment). For the reported issue at Seabright Municipal Works, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

Question 605

Oceanview Payments operates regulated card workflows and employee access with a managed device fleet. Its review records the following concern: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. Which action BEST addresses the described security, identity, or compliance gap?

  1. Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment.
  2. Configure an appropriate Azure Private Endpoint and network access restrictions for the vault.
  3. Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access.
  4. Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites.

Explanation

Correct Answer

C:

Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access. This directly addresses the observed weakness: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. For Oceanview Payments and its regulated card workflows and employee access, a meaningful acceptance check would be: An authorized signing request succeeds without exposing private key material to the application caller.

Incorrect Answers

A:

Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment. This addresses a different security or governance gap: A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

B:

Configure an appropriate Azure Private Endpoint and network access restrictions for the vault. This addresses a different security or governance gap: An application reads sensitive Key Vault secrets over public network paths although policy requires private network access. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

D:

Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites. This addresses a different security or governance gap: An operations team needs SSH access to a private Linux VM but incorrectly assumes Azure Bastion is only for Windows desktop sessions. For Oceanview Payments and its regulated card workflows and employee access, the issue is instead: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. This alternative alone would not demonstrate the needed result: An authorized signing request succeeds without exposing private key material to the application caller.

Question 606

Oceanview Payments operates regulated card workflows and employee access with a managed device fleet. Its review records the following concern: A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented.
  2. A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails.
  3. A permitted administrator starts a secure SSH session without exposing an inbound public SSH endpoint.
  4. An authorized signing request succeeds without exposing private key material to the application caller.

Explanation

Correct Answer

D:

An authorized signing request succeeds without exposing private key material to the application caller. This is the relevant proof because it tests whether the selected corrective action (Use Azure Key Vault key capabilities for controlled cryptographic operations and restricted key access) addressed the initiating problem (A signing service requires controlled cryptographic key operations but the application team proposes distributing the private key as plain text) in Oceanview Payments's regulated card workflows and employee access environment, not merely whether a task was marked complete.

Incorrect Answers

A:

An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented. This is useful evidence for a different situation (A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs) and action (Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment). For the reported issue at Oceanview Payments, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

B:

A private client resolves and reaches the vault through the intended endpoint while a disallowed public access attempt fails. This is useful evidence for a different situation (An application reads sensitive Key Vault secrets over public network paths although policy requires private network access) and action (Configure an appropriate Azure Private Endpoint and network access restrictions for the vault). For the reported issue at Oceanview Payments, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

C:

A permitted administrator starts a secure SSH session without exposing an inbound public SSH endpoint. This is useful evidence for a different situation (An operations team needs SSH access to a private Linux VM but incorrectly assumes Azure Bastion is only for Windows desktop sessions) and action (Use Azure Bastion's supported SSH connectivity workflow with authorized identities and network prerequisites). For the reported issue at Oceanview Payments, it does not establish the required outcome: An authorized signing request succeeds without exposing private key material to the application caller.

Question 607

Sapphire Data Systems operates customer tenants and managed cloud services with separation-of-duties controls. Its review records the following concern: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. Which action BEST addresses the described security, identity, or compliance gap?

  1. Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment.
  2. Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model.
  3. Store application secrets in Azure Key Vault and grant only approved identities access to retrieve them.
  4. Apply least-privilege NSG rules to permit only required application traffic and restrict administration access.

Explanation

Correct Answer

B:

Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model. This directly addresses the observed weakness: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. For Sapphire Data Systems and its customer tenants and managed cloud services, a meaningful acceptance check would be: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Incorrect Answers

A:

Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment. This addresses a different security or governance gap: A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs. For Sapphire Data Systems and its customer tenants and managed cloud services, the issue is instead: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. This alternative alone would not demonstrate the needed result: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

C:

Store application secrets in Azure Key Vault and grant only approved identities access to retrieve them. This addresses a different security or governance gap: A web application embeds database passwords in configuration files and sends them through every developer deployment. For Sapphire Data Systems and its customer tenants and managed cloud services, the issue is instead: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. This alternative alone would not demonstrate the needed result: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

D:

Apply least-privilege NSG rules to permit only required application traffic and restrict administration access. This addresses a different security or governance gap: A subnet exposes RDP from the public internet because no network security group rules restrict management sources. For Sapphire Data Systems and its customer tenants and managed cloud services, the issue is instead: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. This alternative alone would not demonstrate the needed result: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Question 608

Sapphire Data Systems operates customer tenants and managed cloud services with separation-of-duties controls. Its review records the following concern: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented.
  2. An unapproved source cannot connect to the management port while legitimate workload traffic succeeds.
  3. The application reads the secret using its assigned identity while a developer without permission receives an access denial.
  4. A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Explanation

Correct Answer

D:

A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents. This is the relevant proof because it tests whether the selected corrective action (Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model) addressed the initiating problem (A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions) in Sapphire Data Systems's customer tenants and managed cloud services environment, not merely whether a task was marked complete.

Incorrect Answers

A:

An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented. This is useful evidence for a different situation (A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs) and action (Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment). For the reported issue at Sapphire Data Systems, it does not establish the required outcome: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

B:

An unapproved source cannot connect to the management port while legitimate workload traffic succeeds. This is useful evidence for a different situation (A subnet exposes RDP from the public internet because no network security group rules restrict management sources) and action (Apply least-privilege NSG rules to permit only required application traffic and restrict administration access). For the reported issue at Sapphire Data Systems, it does not establish the required outcome: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

C:

The application reads the secret using its assigned identity while a developer without permission receives an access denial. This is useful evidence for a different situation (A web application embeds database passwords in configuration files and sends them through every developer deployment) and action (Store application secrets in Azure Key Vault and grant only approved identities access to retrieve them). For the reported issue at Sapphire Data Systems, it does not establish the required outcome: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Question 609

For Linden Manufacturing, the security review of plant operations and product design information highlights this gap: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. Which action BEST addresses the described security, identity, or compliance gap?

  1. Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment.
  2. Store application secrets in Azure Key Vault and grant only approved identities access to retrieve them.
  3. Apply least-privilege NSG rules to permit only required application traffic and restrict administration access.
  4. Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model.

Explanation

Correct Answer

D:

Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model. This directly addresses the observed weakness: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. For Linden Manufacturing and its plant operations and product design information, a meaningful acceptance check would be: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Incorrect Answers

A:

Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment. This addresses a different security or governance gap: A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs. For Linden Manufacturing and its plant operations and product design information, the issue is instead: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. This alternative alone would not demonstrate the needed result: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

B:

Store application secrets in Azure Key Vault and grant only approved identities access to retrieve them. This addresses a different security or governance gap: A web application embeds database passwords in configuration files and sends them through every developer deployment. For Linden Manufacturing and its plant operations and product design information, the issue is instead: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. This alternative alone would not demonstrate the needed result: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

C:

Apply least-privilege NSG rules to permit only required application traffic and restrict administration access. This addresses a different security or governance gap: A subnet exposes RDP from the public internet because no network security group rules restrict management sources. For Linden Manufacturing and its plant operations and product design information, the issue is instead: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. This alternative alone would not demonstrate the needed result: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Question 610

For Linden Manufacturing, the security review of plant operations and product design information highlights this gap: A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?

  1. The application reads the secret using its assigned identity while a developer without permission receives an access denial.
  2. An unapproved source cannot connect to the management port while legitimate workload traffic succeeds.
  3. An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented.
  4. A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

Explanation

Correct Answer

D:

A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents. This is the relevant proof because it tests whether the selected corrective action (Apply least-privilege Key Vault data access with an appropriate Azure RBAC or supported access policy model) addressed the initiating problem (A Key Vault deployment assigns broad access to all subscriptions because the team confuses resource management with data-plane secret permissions) in Linden Manufacturing's plant operations and product design information environment, not merely whether a task was marked complete.

Incorrect Answers

A:

The application reads the secret using its assigned identity while a developer without permission receives an access denial. This is useful evidence for a different situation (A web application embeds database passwords in configuration files and sends them through every developer deployment) and action (Store application secrets in Azure Key Vault and grant only approved identities access to retrieve them). For the reported issue at Linden Manufacturing, it does not establish the required outcome: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

B:

An unapproved source cannot connect to the management port while legitimate workload traffic succeeds. This is useful evidence for a different situation (A subnet exposes RDP from the public internet because no network security group rules restrict management sources) and action (Apply least-privilege NSG rules to permit only required application traffic and restrict administration access). For the reported issue at Linden Manufacturing, it does not establish the required outcome: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.

C:

An accidental deletion can be recovered within the configured window and unauthorized early permanent purge is prevented. This is useful evidence for a different situation (A staff member accidentally deletes a secret and the vault has no recovery process aligned with regulatory retention needs) and action (Enable and govern supported soft-delete and purge-protection capabilities for the Key Vault deployment). For the reported issue at Linden Manufacturing, it does not establish the required outcome: A permitted identity retrieves only its allowed secret and an unrelated identity cannot read the vault contents.