Question 780
Workload context: A bank exposes multiple back-end APIs to partner developers with quotas, versioning and a consolidated developer gateway. The implemented remedy is: Place Azure API Management in front of the APIs using proper product subscriptions, API versions and policies. Which ongoing practice most specifically prevents recurrence of this failure: Partners invoke backend URLs directly and bypass requested quotas.?
- Review gateway policies, API revisions and partner access after backend releases.
- Regression-test gateway policy order and key claims after API registration changes.
- Review Dapr component scopes, secret stores and service identity as applications evolve.
- Monitor origin health and WAF false-positive patterns after deploying rules.
Explanation
Correct Answer
A:The key follow-up control is: Review gateway policies, API revisions and partner access after backend releases. It avoids recurrence of the scenario in which: Partners invoke backend URLs directly and bypass requested quotas. It addresses: There is no API gateway governing public partner traffic consistently.
Incorrect Answers
B:Regression-test gateway policy order and key claims after API registration changes would not review gateway policies, API revisions and partner access after backend releases.
C:Reviewing Dapr component scopes, secret stores and service identity as applications evolve would not review gateway policies, API revisions and partner access after backend releases.
D:Monitoring origin health and WAF false-positive patterns after deploying rules would not review gateway policies, API revisions and partner access after backend releases.
Question 781
A solution architect is reviewing a workload: A public API must reject untrusted JWT access tokens and enforce per-client rate limits before traffic reaches compute backends. The observed incident is: Invalid tokens and request bursts reach an otherwise healthy API backend. Which architecture choice most directly removes the identified weakness?
- Use an API frontend to accept validated commands into a durable Service Bus queue, with independent scalable workers.
- Place Azure API Management in front of the APIs using proper product subscriptions, API versions and policies.
- Design Azure Front Door with origin groups, routes and WAF policy as appropriate.
- Use supported API Management policies for JWT validation and throttling at the inbound processing stage.
Explanation
Correct Answer
D:This option addresses the actual design defect: API gateway inbound identity and traffic governance controls were not applied. The correction is: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. Confirm the outcome with: Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
Incorrect Answers
A:Using an API frontend to accept validated commands into a durable Service Bus queue, with independent scalable workers would not meet the need for supported API Management policies for JWT validation and throttling at the inbound processing stage.
B:Placing Azure API Management in front of the APIs using proper product subscriptions, API versions and policies would not meet the need for supported API Management policies for JWT validation and throttling at the inbound processing stage.
C:Designing Azure Front Door with origin groups, routes and WAF policy as appropriate would not meet the need for supported API Management policies for JWT validation and throttling at the inbound processing stage.
Question 782
An architect proposes this change: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The workload context is: A public API must reject untrusted JWT access tokens and enforce per-client rate limits before traffic reaches compute backends. Which evidence would most directly validate the change?
- Post a test command, observe fast 202/acknowledgment and eventual idempotent worker completion.
- Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
- Test an approved subscription key and reject an over-quota or unauthorized partner call.
- Send requests to defined paths and confirm origin selection and WAF blocking in logs.
Explanation
Correct Answer
B:The acceptance test is specific: Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections. Its purpose is to establish that the proposed architecture works: Use supported API Management policies for JWT validation and throttling at the inbound processing stage.
Incorrect Answers
A:Post a test command, observe fast 202/acknowledgment and eventual idempotent worker completion would not address the need for submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
C:The alternative test targets: Place Azure API Management in front of the APIs using proper product subscriptions, API versions and policies. The scenario's actual proposed remedy is: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. Verify that one by: Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
D:Sending requests to defined paths and confirming origin selection and WAF blocking in logs would not address the need for submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
Question 783
During architecture troubleshooting, a team reports: Invalid tokens and request bursts reach an otherwise healthy API backend. Context: A public API must reject untrusted JWT access tokens and enforce per-client rate limits before traffic reaches compute backends. Which underlying design mistake explains the observed behavior most precisely?
- Global application entry routing and edge filtering were not implemented.
- There is no API gateway governing public partner traffic consistently.
- API gateway inbound identity and traffic governance controls were not applied.
- Application processing and frontend request lifetime are tightly coupled.
Explanation
Correct Answer
C:The recorded behavior follows from: API gateway inbound identity and traffic governance controls were not applied. The appropriate mitigation would be: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. Verify with: Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
Incorrect Answers
A:The alternative diagnosis “Global application entry routing and edge filtering were not implemented” does not match the observed symptom: Invalid tokens and request bursts reach an otherwise healthy API backend. Context: A public API must reject untrusted JWT access tokens and enforce per-client rate limits before traffic reaches compute backends. The recorded behavior follows from: API gateway inbound identity and traffic governance controls were not applied. The appropriate mitigation would be: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The evidence instead supports “API gateway inbound identity and traffic governance controls were not applied”.
B:The alternative diagnosis “There is no API gateway governing public partner traffic consistently” does not match the observed symptom: Invalid tokens and request bursts reach an otherwise healthy API backend. Context: A public API must reject untrusted JWT access tokens and enforce per-client rate limits before traffic reaches compute backends. The recorded behavior follows from: API gateway inbound identity and traffic governance controls were not applied. The appropriate mitigation would be: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The evidence instead supports “API gateway inbound identity and traffic governance controls were not applied”.
D:The alternative diagnosis “Application processing and frontend request lifetime are tightly coupled” does not match the observed symptom: Invalid tokens and request bursts reach an otherwise healthy API backend. Context: A public API must reject untrusted JWT access tokens and enforce per-client rate limits before traffic reaches compute backends. The recorded behavior follows from: API gateway inbound identity and traffic governance controls were not applied. The appropriate mitigation would be: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The evidence instead supports “API gateway inbound identity and traffic governance controls were not applied”.
Question 784
The design change is: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The original failure was: Invalid tokens and request bursts reach an otherwise healthy API backend. Which ongoing control best prevents recurrence of the same root cause?
- Review gateway policies, API revisions and partner access after backend releases.
- Regression-test gateway policy order and key claims after API registration changes.
- Monitor queue age and retry backlog separately from frontend latency.
- Monitor origin health and WAF false-positive patterns after deploying rules.
Explanation
Correct Answer
B:This is an ongoing protection specific to the fault: Regression-test gateway policy order and key claims after API registration changes. The recurrence risk is: API gateway inbound identity and traffic governance controls were not applied. It should be checked using: Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
Incorrect Answers
A:The alternative diagnosis “Review gateway policies, API revisions and partner access after backend releases” does not match the observed symptom: The design change is: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The original failure was: Invalid tokens and request bursts reach an otherwise healthy API backend. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Regression-test gateway policy order and key claims after API registration changes. The recurrence risk is: API gateway inbound identity and traffic governance controls were not applied. The evidence instead supports “Regression-test gateway policy order and key claims after API registration changes”.
C:The alternative diagnosis “Monitor queue age and retry backlog separately from frontend latency” does not match the observed symptom: The design change is: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The original failure was: Invalid tokens and request bursts reach an otherwise healthy API backend. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Regression-test gateway policy order and key claims after API registration changes. The recurrence risk is: API gateway inbound identity and traffic governance controls were not applied. The evidence instead supports “Regression-test gateway policy order and key claims after API registration changes”.
D:The alternative diagnosis “Monitor origin health and WAF false-positive patterns after deploying rules” does not match the observed symptom: The design change is: Use supported API Management policies for JWT validation and throttling at the inbound processing stage. The original failure was: Invalid tokens and request bursts reach an otherwise healthy API backend. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Regression-test gateway policy order and key claims after API registration changes. The recurrence risk is: API gateway inbound identity and traffic governance controls were not applied. The evidence instead supports “Regression-test gateway policy order and key claims after API registration changes”.
Question 785
A design workshop has this requirement: A global retail API needs HTTP path routing, TLS offload and web attack filtering before requests reach regional applications. Operators currently observe: A client lands on one failed regional endpoint because no global HTTP front end exists. Select the ONE design remedy that best addresses the root cause.
- Use GitHub Actions with approved workload identity federation, scoped Azure RBAC and environment protection rules.
- Use an API frontend to accept validated commands into a durable Service Bus queue, with independent scalable workers.
- Design Azure Front Door with origin groups, routes and WAF policy as appropriate.
- Use supported API Management policies for JWT validation and throttling at the inbound processing stage.
Explanation
Correct Answer
C:This option addresses the actual design defect: Global application entry routing and edge filtering were not implemented. The correction is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. Confirm the outcome with: Send requests to defined paths and confirm origin selection and WAF blocking in logs.
Incorrect Answers
A:The alternative diagnosis “Use GitHub Actions with approved workload identity federation, scoped Azure RBAC and environment protection rules” does not match the observed symptom: A client lands on one failed regional endpoint because no global HTTP front end exists. This option addresses the actual design defect: Global application entry routing and edge filtering were not implemented. The correction is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. The evidence instead supports “Design Azure Front Door with origin groups, routes and WAF policy as appropriate”.
B:The alternative diagnosis “Use an API frontend to accept validated commands into a durable Service Bus queue, with independent scalable workers” does not match the observed symptom: A client lands on one failed regional endpoint because no global HTTP front end exists. This option addresses the actual design defect: Global application entry routing and edge filtering were not implemented. The correction is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. The evidence instead supports “Design Azure Front Door with origin groups, routes and WAF policy as appropriate”.
D:The alternative diagnosis “Use supported API Management policies for JWT validation and throttling at the inbound processing stage” does not match the observed symptom: A client lands on one failed regional endpoint because no global HTTP front end exists. This option addresses the actual design defect: Global application entry routing and edge filtering were not implemented. The correction is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. The evidence instead supports “Design Azure Front Door with origin groups, routes and WAF policy as appropriate”.
Question 786
The planned architecture is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. Workload context: A global retail API needs HTTP path routing, TLS offload and web attack filtering before requests reach regional applications. Which acceptance test demonstrates that the required behavior works?
- Submit a wrong-audience JWT and excessive valid requests, confirming the gateway returns expected rejections.
- Run a signed workflow from the authorized branch and ensure an unapproved ref cannot obtain Azure deployment access.
- Send requests to defined paths and confirm origin selection and WAF blocking in logs.
- Post a test command, observe fast 202/acknowledgment and eventual idempotent worker completion.
Explanation
Correct Answer
C:This observation directly verifies the intended design: Send requests to defined paths and confirm origin selection and WAF blocking in logs. The architecture being tested is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. The original symptom was: A client lands on one failed regional endpoint because no global HTTP front end exists.
Incorrect Answers
A:That observation pertains to a separate failure: Invalid tokens and request bursts reach an otherwise healthy API backend. Its cause is: API gateway inbound identity and traffic governance controls were not applied. It does not confirm the result of this design. The direct proof would be: Send requests to defined paths and confirm origin selection and WAF blocking in logs.
B:The alternative test targets: Use GitHub Actions with approved workload identity federation, scoped Azure RBAC and environment protection rules. The scenario's actual proposed remedy is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. Verify that one by: Send requests to defined paths and confirm origin selection and WAF blocking in logs.
D:That observation pertains to a separate failure: Client HTTP requests frequently time out because processing runs synchronously for several minutes. Its cause is: Application processing and frontend request lifetime are tightly coupled. It does not confirm the result of this design. The direct proof would be: Send requests to defined paths and confirm origin selection and WAF blocking in logs.
Question 787
The customer states: A global retail API needs HTTP path routing, TLS offload and web attack filtering before requests reach regional applications. An incident reveals: A client lands on one failed regional endpoint because no global HTTP front end exists. What cause best accounts for this evidence?
- Deployment trust relies on long-lived secrets instead of constrained OIDC federation.
- Application processing and frontend request lifetime are tightly coupled.
- API gateway inbound identity and traffic governance controls were not applied.
- Global application entry routing and edge filtering were not implemented.
Explanation
Correct Answer
D:This is the failure mechanism rather than an incidental symptom: Global application entry routing and edge filtering were not implemented. It accounts for: A client lands on one failed regional endpoint because no global HTTP front end exists. The architectural repair is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate.
Incorrect Answers
A:Deployment trust relies on long-lived secrets would not address the need for global application entry routing and edge filtering were not implemented.
B:Application processing and frontend request lifetime are tightly coupled would not address the need for global application entry routing and edge filtering were not implemented.
C:API gateway inbound identity and traffic governance controls were not applied would not address the need for global application entry routing and edge filtering were not implemented.
Question 788
Workload context: A global retail API needs HTTP path routing, TLS offload and web attack filtering before requests reach regional applications. The implemented remedy is: Design Azure Front Door with origin groups, routes and WAF policy as appropriate. Which ongoing practice most specifically prevents recurrence of this failure: A client lands on one failed regional endpoint because no global HTTP front end exists.?
- Monitor queue age and retry backlog separately from frontend latency.
- Review federated subject claims and repository environment approvals after workflow changes.
- Regression-test gateway policy order and key claims after API registration changes.
- Monitor origin health and WAF false-positive patterns after deploying rules.
Explanation
Correct Answer
D:This is an ongoing protection specific to the fault: Monitor origin health and WAF false-positive patterns after deploying rules. The recurrence risk is: Global application entry routing and edge filtering were not implemented. It should be checked using: Send requests to defined paths and confirm origin selection and WAF blocking in logs.
Incorrect Answers
A:Monitoring queue age and retry backlog separately from frontend latency would not monitor origin health and WAF false-positive patterns after deploying rules.
B:Reviewing federated subject claims and repository environment approvals after workflow changes would not monitor origin health and WAF false-positive patterns after deploying rules.
C:Regression-test gateway policy order and key claims after API registration changes would not monitor origin health and WAF false-positive patterns after deploying rules.
Question 789
A solution architect is reviewing a workload: A microservice fleet must share mutable non-secret feature settings with dynamic refresh without redeploying all workloads. The observed incident is: App teams copy environment values into every deployment image and cannot change them centrally. Which architecture choice most directly removes the identified weakness?
- Use Azure Key Vault references in App Service settings with a managed identity authorized to read the referenced secrets.
- Use Azure App Configuration feature management with supported targeting or percentage filters.
- Use Azure App Configuration with labels and controlled application refresh integration.
- Use GitHub Actions with approved workload identity federation, scoped Azure RBAC and environment protection rules.
Explanation
Correct Answer
C:The evidence (App teams copy environment values into every deployment image and cannot change them centrally.) identifies the following cause: Application configuration lacks a managed centralized service and refresh mechanism. The design that removes it is: Use Azure App Configuration with labels and controlled application refresh integration. The acceptance check is: Change a feature setting and verify subscribed app instances obtain the updated version as designed.
Incorrect Answers
A:The evidence (App teams copy environment values into every deployment image and cannot change them centrally.) identifies the following cause: Application configuration lacks a managed centralized service and refresh mechanism.
B:Using Azure App Configuration feature management with supported targeting or percentage filters would not meet the need for Azure App Configuration with labels and controlled application refresh integration.
D:Using GitHub Actions with approved workload identity federation, scoped Azure RBAC and environment protection rules would not meet the need for Azure App Configuration with labels and controlled application refresh integration.
Question 790
An architect proposes this change: Use Azure App Configuration with labels and controlled application refresh integration. The workload context is: A microservice fleet must share mutable non-secret feature settings with dynamic refresh without redeploying all workloads. Which evidence would most directly validate the change?
- Enable the feature for test users and confirm the configured population sees the expected rollout behavior.
- Change a feature setting and verify subscribed app instances obtain the updated version as designed.
- Run a signed workflow from the authorized branch and ensure an unapproved ref cannot obtain Azure deployment access.
- Rotate a test secret in Key Vault and verify the app resolves the new value after supported refresh behavior.
Explanation
Correct Answer
B:This observation directly verifies the intended design: Change a feature setting and verify subscribed app instances obtain the updated version as designed. The architecture being tested is: Use Azure App Configuration with labels and controlled application refresh integration. The original symptom was: App teams copy environment values into every deployment image and cannot change them centrally.
Incorrect Answers
A:The alternative test targets: Use Azure App Configuration feature management with supported targeting or percentage filters. The scenario's actual proposed remedy is: Use Azure App Configuration with labels and controlled application refresh integration. Verify that one by: Change a feature setting and verify subscribed app instances obtain the updated version as designed.
C:That observation pertains to a separate failure: A copied client secret in repository secrets must be rotated after accidental exposure. Its cause is: Deployment trust relies on long-lived secrets instead of constrained OIDC federation. It does not confirm the result of this design. The direct proof would be: Change a feature setting and verify subscribed app instances obtain the updated version as designed.
D:The alternative test targets: Use Azure Key Vault references in App Service settings with a managed identity authorized to read the referenced secrets. The scenario's actual proposed remedy is: Use Azure App Configuration with labels and controlled application refresh integration. Verify that one by: Change a feature setting and verify subscribed app instances obtain the updated version as designed.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests