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 55

Question 540

For this case—A systems team assigns public SSH ports to all production Linux VMs even though its Azure network supports Bastion-based access.—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: 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.
  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 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.

Explanation

Correct Answer

D:

The situation is that a systems team assigns public SSH ports to all production Linux VMs even though its Azure network supports Bastion-based access. 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. The action and test belong together because Azure Bastion provides an administrative connection path without requiring each managed virtual machine to expose its own public RDP or SSH endpoint.

Incorrect Answers

A:

That action-and-evidence pair concerns “use Azure web application firewall for HTTP request threats”, not this decision. The appropriate action is to use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines. To confirm, connect to a private lab virtual machine through Bastion and confirm no internet-exposed public SSH or RDP listener is assigned to that VM.

B:

The proposed pair focuses on “use Azure key vault key operations” instead. The appropriate action is to use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines. To confirm, connect to a private lab virtual machine through Bastion and confirm no internet-exposed public SSH or RDP listener is assigned to that VM.

C:

“use Azure ddos protection for network flood resilience” evaluates a different intervention. The appropriate action is to use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines. To confirm, connect to a private lab virtual machine through Bastion and confirm no internet-exposed public SSH or RDP listener is assigned to that VM.

Question 541

An Azure Function must retrieve its payment API secret without storing the secret value in a published deployment package. Which implementation or design choice most directly mitigates the stated issue?

  1. Keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations.
  2. Evaluate Azure Firewall Premium features such as intrusion detection and supported TLS inspection when justified by policy and application compatibility.
  3. Apply Azure Firewall rules and appropriate network routing to control approved outbound and cross-network traffic through a centralized service.
  4. Use Azure Bastion with supported network design to establish managed browser or native-client RDP and SSH access to private virtual machines.

Explanation

Correct Answer

A:

Keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity. To verify, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

Incorrect Answers

B:

“understand Azure firewall premium inspection scope and tradeoffs” is related to another task, not the failure shown here. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

C:

This alternative focuses on “use Azure firewall as central managed network filtering” instead of the required outcome. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

D:

That choice concerns “use Azure bastion for remote administration without public VM ports”, not the immediate requirement. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

Question 542

An Azure Function must retrieve its payment API secret without storing the secret value in a published deployment package. Which technical explanation most directly supports the right approach?

  1. Azure Bastion provides an administrative connection path without requiring each managed virtual machine to expose its own public RDP or SSH endpoint.
  2. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.
  3. A private endpoint gives a service a private IP connection path, but DNS and authorized private routing are necessary for clients to use it.
  4. Premium inspection features can analyze additional traffic content but depend on routing, certificate trust and policy coverage, and are not automatically applied to every session.

Explanation

Correct Answer

B:

Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity. This supports the decision to keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations.

Incorrect Answers

A:

The principle behind “use Azure bastion for remote administration without public VM ports” is not the one being tested. Here, key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

C:

“use private endpoints where service data access must avoid public exposure” explains a different mechanism. Here, key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

D:

That statement concerns “understand Azure firewall premium inspection scope and tradeoffs” rather than the cause in this case. Here, key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

Question 543

For this situation—An Azure Function must retrieve its payment API secret without storing the secret value in a published deployment package.—which check provides the strongest verification?

  1. Send a harmless test request matching a managed web attack pattern and inspect its WAF log and blocked response without disrupting real users.
  2. Resolve the service's test hostname to its expected private address and verify one permitted client can connect while disallowed public access stays blocked.
  3. Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.
  4. Route synthetic supported application traffic through a pilot inspection policy and verify expected alerts while confirming trusted TLS behavior.

Explanation

Correct Answer

C:

Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging. It is the relevant test 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 web application firewall for HTTP request threats” would verify a different part of the system. To check this result, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

B:

That test concerns “use private endpoints where service data access must avoid public exposure”, not the requested outcome. To check this result, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

D:

This evidence addresses “understand Azure firewall premium inspection scope and tradeoffs” instead of confirming the repair. To check this result, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

Question 544

An Azure Function must retrieve its payment API secret without storing the secret value in a published deployment package. If the team does the following—"Commit a production API password in a public Git repository because the workload's Azure subscription already uses encrypted disks."—what could go wrong?

  1. Unapproved traffic can evade centralized inspection because packets never traverse the intended filtering service.
  2. Untrusted sources can reach protected service ports because the first matching high-priority permissive rule overrides intended restrictions.
  3. Authorized apps may lose access because hostnames still resolve to unreachable public addresses or their networks lack the private route.
  4. An exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at rest.

Explanation

Correct Answer

D:

An exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST. The shortcut is unsafe 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:

That consequence concerns “Unapproved traffic can evade centralized inspection because packets never traverse the intended filtering service”, which is a different failure. Here, an exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST.

B:

“Untrusted sources can reach protected service ports because the first matching high-priority permissive rule overrides intended…” does not describe the result of this shortcut. Here, an exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST.

C:

The alternative risk relates to “Authorized apps may lose access because hostnames still resolve to unreachable public addresses or their networks…”, not the stated mistake. Here, an exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST.

Question 545

An Azure Function must retrieve its payment API secret without storing the secret value in a published deployment package. Which action and validation evidence belong together?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

A:

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

B:

“use Azure key vault key operations” 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 linked action and check for “use application security groups and route tables for controlled network policy” would not resolve this case. 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:

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.

Question 546

An SC-900 learner considers: A developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. What is the most appropriate next decision?

  1. Group relevant Azure VM interfaces with application security groups and manage subnet routing through supported route tables for documented traffic paths.
  2. Keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations.
  3. Design separate Azure virtual network or subnet boundaries for workload tiers and apply intentional connectivity and access-control policies.
  4. Evaluate Azure Firewall Premium features such as intrusion detection and supported TLS inspection when justified by policy and application compatibility.

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. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity. To verify, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

Incorrect Answers

A:

“use application security groups and route tables for controlled network policy” is related to another task, not the failure shown here. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

C:

That choice concerns “segment Azure resources through virtual networks and subnets”, not the immediate requirement. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

D:

The proposed action addresses “understand Azure firewall premium inspection scope and tradeoffs” rather than the problem described. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

Question 547

A developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. Why does the recommended approach address this particular concern?

  1. NSGs filter traffic at subnet or network-interface boundaries using ordered allow and deny rules; a lower-priority rule may never be evaluated.
  2. A private endpoint gives a service a private IP connection path, but DNS and authorized private routing are necessary for clients to use it.
  3. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.
  4. Premium inspection features can analyze additional traffic content but depend on routing, certificate trust and policy coverage, and are not automatically applied to every session.

Explanation

Correct Answer

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. Key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity. This supports the decision to keep secrets such as API keys in Azure Key Vault and grant supported application identities only the required secret operations.

Incorrect Answers

A:

“apply network security group rules to subnet and nic traffic” describes another technical distinction. Here, key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

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. “use private endpoints where service data access must avoid public exposure” explains a different mechanism. Here, key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

D:

The principle behind “understand Azure firewall premium inspection scope and tradeoffs” is not the one being tested. Here, key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

Question 548

A developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. Which evidence best validates the proposed outcome?

  1. 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. Test allowed application traffic and denied management traffic through a lab NSG while reviewing effective security rules on the target interface.
  3. Run separate harmless simulations of volumetric request pressure and application-rule matches and confirm the relevant telemetry is attributed correctly.
  4. Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

Explanation

Correct Answer

D:

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. Read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging. It is the relevant test 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:

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 test concerns “use private endpoints where service data access must avoid public exposure”, not the requested outcome. To check this result, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

B:

The proposed check is relevant to “apply network security group rules to subnet and nic traffic”, but not sufficient here. To check this result, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

C:

This evidence addresses “choose layered network ddos and application waf controls” instead of confirming the repair. To check this result, read one test Key Vault secret using a permitted managed identity, reject a different workload identity and verify appropriate access logging.

Question 549

Consider this situation: A developer pushes a connection string containing a production password to a repository and assumes encrypted VM disks make it safe. A team member suggests: "Commit a production API password in a public Git repository because the workload's Azure subscription already uses encrypted disks." What is the main risk?

  1. An exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at rest.
  2. Authorized apps may lose access because hostnames still resolve to unreachable public addresses or their networks lack the private route.
  3. The application can still suffer service disruption from floods outside the WAF's filtering scope or injection attacks without HTTP inspection.
  4. Some business applications may fail connections or inspections may miss intended flows when certificate and route dependencies were ignored.

Explanation

Correct Answer

A:

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. An exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST. The shortcut is unsafe because key Vault separates protected secret lifecycle and auditability from application source code, but the application still needs a properly authorized identity.

Incorrect Answers

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. The alternative risk relates to “Authorized apps may lose access because hostnames still resolve to unreachable public addresses or their networks…”, not the stated mistake. Here, an exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST.

C:

“The application can still suffer service disruption from floods outside the WAF's filtering scope or injection…” can arise elsewhere, but it is not the most direct risk here. Here, an exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST.

D:

That consequence concerns “Some business applications may fail connections or inspections may miss intended flows when certificate and route…”, which is a different failure. Here, an exposed source repository can disclose credentials that remain usable until rotated regardless of storage encryption at REST.

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.

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