Microsoft SC-900 Dumps
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?
Explanation
Correct Answer
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
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.
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.
“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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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
- Microsoft SC-900 Practice Test 53 - 10 Questions (Last Reviewed 29-Sep-2026)
- Microsoft SC-900 Practice Test 54 - 10 Questions (Last Reviewed 28-Sep-2026)
- Microsoft SC-900 Practice Test 55 - 10 Questions (Last Reviewed 27-Sep-2026)
- Microsoft SC-900 Practice Test 56 - 10 Questions (Last Reviewed 26-Sep-2026)
- Microsoft SC-900 Practice Test 57 - 10 Questions (Last Reviewed 21-Nov-2026)