Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

Microsoft SC-900 Practice Test 56

Question 550

A security and compliance reviewer considers: A developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. Which response and evidence should be linked?

  1. Action: Use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines. Validation: Connect to a private lab virtual machine through Bastion and confirm no internet-exposed public SSH or RDP listener is assigned to that VM.
  2. Action: Keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. Validation: Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.
  3. Action: Apply Azure Firewall rules and appropriate network routing to control approved outbound and cross-network traffic through a centralized service. Validation: Send synthetic authorized and denied connection attempts through the configured route and verify firewall rule-match logs and expected outcomes.
  4. Action: Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Validation: Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Explanation

Correct Answer

B:

The situation is that a developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. Keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. Validation: Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging. The action and test belong together because key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

Incorrect Answers

A:

“use Azure bastion for remote administration without public VM ports” evaluates a different intervention. The appropriate action is to keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. To confirm, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

C:

The situation is that a developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. That action-and-evidence pair concerns “use Azure firewall as central managed network filtering”, not this decision. The appropriate action is to keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. To confirm, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

D:

The proposed pair focuses on “use Azure key vault key operations” instead. The appropriate action is to keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. To confirm, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

Question 551

An organization wants centrally controlled key signing for an application and must distinguish key objects from ordinary stored secret strings. Which action best addresses this requirement?

  1. Place a supported Azure Web Application Firewall in the appropriate application delivery path and configure managed or custom rules for web threats.
  2. Use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines.
  3. Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation.
  4. Design separate Azure virtual network or subnet boundaries for workload tiers and apply intentional connectivity and access-control policies.

Explanation

Correct Answer

C:

Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values. To verify, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Incorrect Answers

A:

This alternative focuses on “use Azure web application firewall for HTTP request threats” instead of the required outcome. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

B:

That choice concerns “use Azure bastion for remote administration without public VM ports”, not the immediate requirement. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

D:

“segment Azure resources through virtual networks and subnets” is related to another task, not the failure shown here. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Question 552

A cloud security learner considers: An organization wants centrally controlled key signing for an application and must distinguish key objects from ordinary stored secret strings. Which underlying principle applies?

  1. A private endpoint gives a service a private IP connection path, but DNS and authorized private routing are necessary for clients to use it.
  2. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.
  3. Large packet floods, bot requests and injection attempts target different layers, so choosing one security product does not cover every web threat.
  4. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Explanation

Correct Answer

D:

Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values. This supports the decision to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation.

Incorrect Answers

A:

“use private endpoints where service data access must avoid public exposure” explains a different mechanism. Here, key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

B:

That statement concerns “store application secrets in Azure key vault with scoped access” rather than the cause in this case. Here, key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

C:

The principle behind “choose layered network ddos and application waf controls” is not the one being tested. Here, key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Question 553

An organization wants centrally controlled key signing for an application and must distinguish key objects from ordinary stored secret strings. What should the team examine before accepting the result?

  1. Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.
  2. Send a harmless test request matching a managed web attack pattern and inspect its WAF log and blocked response without disrupting real users.
  3. Connect to a private lab virtual machine through Bastion and confirm no internet-exposed public SSH or RDP listener is assigned to that VM.
  4. Route synthetic supported application traffic through a pilot inspection policy and verify expected alerts while confirming trusted TLS behavior.

Explanation

Correct Answer

A:

Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle. It is the relevant test because key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Incorrect Answers

B:

This evidence addresses “use Azure web application firewall for HTTP request threats” instead of confirming the repair. To check this result, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

C:

“use Azure bastion for remote administration without public VM ports” would verify a different part of the system. To check this result, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

D:

That test concerns “understand Azure firewall premium inspection scope and tradeoffs”, not the requested outcome. To check this result, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Question 554

An organization wants centrally controlled key signing for an application and must distinguish key objects from ordinary stored secret strings. The proposed shortcut is: "Copy the same private encryption key into every application configuration file to make key rotation easier during deployments." Which failure is most likely?

  1. Attackers may continuously target exposed remote administration ports that could have remained inaccessible from the public internet.
  2. A single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.
  3. A compromised public-facing server can reach sensitive backend services when the design has no meaningful network boundary.
  4. Application-layer exploits can pass a port-level allow rule because packet filtering does not interpret the web request content.

Explanation

Correct Answer

B:

A single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce. The shortcut is unsafe because key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Incorrect Answers

A:

The alternative risk relates to “Attackers may continuously target exposed remote administration ports that could have remained inaccessible from the public…”, not the stated mistake. Here, a single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.

C:

That consequence concerns “A compromised public-facing server can reach sensitive backend services when the design has no meaningful network…”, which is a different failure. Here, a single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.

D:

“Application-layer exploits can pass a port-level allow rule because packet filtering does not interpret the web…” does not describe the result of this shortcut. Here, a single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.

Question 555

For this case—An organization wants centrally controlled key signing for an application and must distinguish key objects from ordinary stored secret strings.—which implementation and acceptance check are correctly paired?

  1. Action: Place a supported Azure Web Application Firewall in the appropriate application delivery path and configure managed or custom rules for web threats. Validation: Send a harmless test request matching a managed web attack pattern and inspect its WAF log and blocked response without disrupting real users.
  2. Action: Group relevant Azure VM interfaces with application security groups and manage subnet routing through supported route tables for documented traffic paths. Validation: Create a synthetic app-server group, apply a scoped NSG rule, then inspect effective next hops and a permitted service-to-service connection.
  3. Action: Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Validation: Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.
  4. Action: Design separate Azure virtual network or subnet boundaries for workload tiers and apply intentional connectivity and access-control policies. Validation: Place synthetic web and database workloads into intended network segments and verify only documented application ports can traverse the boundary.

Explanation

Correct Answer

C:

Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Validation: Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle. The action and test belong together because key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Incorrect Answers

A:

The linked action and check for “use Azure web application firewall for HTTP request threats” would not resolve this case. The appropriate action is to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. To confirm, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

B:

That action-and-evidence pair concerns “use application security groups and route tables for controlled network policy”, not this decision. The appropriate action is to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. To confirm, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

D:

“segment Azure resources through virtual networks and subnets” evaluates a different intervention. The appropriate action is to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. To confirm, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Question 556

A platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Which implementation or design choice most directly mitigates the stated issue?

  1. Use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines.
  2. Evaluate Azure Firewall Premium features such as intrusion detection and supported TLS inspection when justified by policy and application compatibility.
  3. Place a supported Azure Web Application Firewall in the appropriate application delivery path and configure managed or custom rules for web threats.
  4. Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation.

Explanation

Correct Answer

D:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values. To verify, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Incorrect Answers

A:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. That choice concerns “use Azure bastion for remote administration without public VM ports”, not the immediate requirement. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

B:

The proposed action addresses “understand Azure firewall premium inspection scope and tradeoffs” rather than the problem described. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

C:

“use Azure web application firewall for HTTP request threats” is related to another task, not the failure shown here. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Question 557

A platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Which technical explanation most directly supports the right approach?

  1. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.
  2. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.
  3. Azure Bastion provides an administrative connection path without requiring each managed virtual machine to expose its own public RDP or SSH endpoint.
  4. Application security groups simplify NSG rule targeting while user-defined routes determine forwarding paths; neither automatically grants application authorization.

Explanation

Correct Answer

A:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values. This supports the decision to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation.

Incorrect Answers

B:

The principle behind “store application secrets in Azure key vault with scoped access” is not the one being tested. Here, key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

C:

“use Azure bastion for remote administration without public VM ports” describes another technical distinction. Here, key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

D:

“use application security groups and route tables for controlled network policy” explains a different mechanism. Here, key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Question 558

For this situation—A platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required.—which check provides the strongest verification?

  1. Create a synthetic app-server group, apply a scoped NSG rule, then inspect effective next hops and a permitted service-to-service connection.
  2. Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.
  3. Route synthetic supported application traffic through a pilot inspection policy and verify expected alerts while confirming trusted TLS behavior.
  4. Resolve the service's test hostname to its expected private address and verify one permitted client can connect while disallowed public access stays blocked.

Explanation

Correct Answer

B:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle. It is the relevant test because key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Incorrect Answers

A:

This evidence addresses “use application security groups and route tables for controlled network policy” instead of confirming the repair. To check this result, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

C:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. That test concerns “understand Azure firewall premium inspection scope and tradeoffs”, not the requested outcome. To check this result, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

D:

The proposed check is relevant to “use private endpoints where service data access must avoid public exposure”, but not sufficient here. To check this result, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Question 559

A platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. If the team does the following—"Copy the same private encryption key into every application configuration file to make key rotation easier during deployments."—what could go wrong?

  1. A compromised public-facing server can reach sensitive backend services when the design has no meaningful network boundary.
  2. Security controls may be bypassed if route selection and NSG rule targeting are treated as the same network function.
  3. A single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.
  4. Unapproved traffic can evade centralized inspection because packets never traverse the intended filtering service.

Explanation

Correct Answer

C:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. A single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce. The shortcut is unsafe because key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Incorrect Answers

A:

“A compromised public-facing server can reach sensitive backend services when the design has no meaningful network…” can arise elsewhere, but it is not the most direct risk here. Here, a single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.

B:

That consequence concerns “Security controls may be bypassed if route selection and NSG rule targeting are treated as the…”, which is a different failure. Here, a single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.

D:

The alternative risk relates to “Unapproved traffic can evade centralized inspection because packets never traverse the intended filtering service”, not the stated mistake. Here, a single leaked configuration can compromise multiple workloads and coordinated key rotation becomes difficult to enforce.

Question 560

A platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Which action and validation evidence belong together?

  1. Action: Choose Azure Private Link private endpoints for supported PaaS resources and configure private DNS and network reachability correctly. Validation: Resolve the service's test hostname to its expected private address and verify one permitted client can connect while disallowed public access stays blocked.
  2. Action: Keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. Validation: Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.
  3. Action: Evaluate Azure DDoS Protection for eligible public IP resources and network flood threats while pairing it with application and identity controls. Validation: Review simulated traffic alerts and mitigation telemetry on a protected test public endpoint while confirming application WAF rules remain separately configured.
  4. Action: Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Validation: Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

Explanation

Correct Answer

D:

The situation is that a platform team stores a reusable private key in each microservice image and cannot identify every deployed copy when rotation is required. Use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. Validation: Execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle. The action and test belong together because key Vault keys are managed cryptographic objects used through authorization-controlled APIs, whereas Key Vault secrets store arbitrary sensitive values.

Incorrect Answers

A:

That action-and-evidence pair concerns “use private endpoints where service data access must avoid public exposure”, not this decision. The appropriate action is to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. To confirm, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

B:

The proposed pair focuses on “store application secrets in Azure key vault with scoped access” instead. The appropriate action is to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. To confirm, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

C:

“use Azure ddos protection for network flood resilience” evaluates a different intervention. The appropriate action is to use supported Key Vault or Managed HSM key capabilities when applications need controlled cryptographic key operations and defined key rotation. To confirm, execute a test sign or unwrap operation with an approved identity, deny an unauthorized key operation and inspect key-version lifecycle.

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