You save $69.98
AZ-305 Premium Bundle
- Premium File 382 Questions & Answers
- Last Update: Nov 20, 2026
- Training Course 87 Lectures
- Study Guide 933 Pages
You save $69.98
Architecture review: Database resource diagnostics and Control-plane audit. Requirement A: A SQL database writes audit and performance diagnostics but the central workspace has only platform activity records. Requirement B: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. Which complete two-part proposal satisfies both constraints?
For requirement A, resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. For requirement B, the Activity Log records Azure Resource Manager control-plane events independent of guest agents. Verify both independently: SQL diagnostic records appear in the target workspace and can be filtered by database name; A denied deployment and a successful resource deletion appear with caller and operation name.
The mismatched half is Automated diagnostics policy; Control-plane audit instead needs: Route Azure Activity Log to a central Log Analytics workspace through diagnostic settings.
The option covers one requirement but substitutes WAF decision logs for Database resource diagnostics. The missing acceptance result is: SQL diagnostic records appear in the target workspace and can be filtered by database name.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. The Activity Log records Azure Resource Manager control-plane events independent of guest agents. The proposed steps (enable Application Gateway WAF diagnostics and send them to Log Analytics; use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings) address other capabilities instead of this required pair.
A security audit worries a compromised backup administrator could delete protected recovery points. The acceptance test is: A forbidden backup deletion or retention reduction is rejected during the configured protection period. Which design recommendation best satisfies both?
Immutable backup settings can prevent specified destructive operations against protected backups. The selected architecture is enable an appropriately configured immutable Azure Backup vault with supporting controls; confirm the result by checking that a forbidden backup deletion or retention reduction is rejected during the configured protection period.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. The relevant requirement is: A security audit worries a compromised backup administrator could delete protected recovery points.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. That is useful for Backup private endpoints (Backup workloads in restricted networks must avoid general public service access where supported). It does not meet the current Vault immutability requirement: A security audit worries a compromised backup administrator could delete protected recovery points.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. It does not solve the specified Vault immutability condition.
For the Workload identity federation requirement, the proposed architecture uses: Configure workload identity federation between the trusted job issuer and an Entra application or user-assigned identity. Why does that design fit?
Federated credentials exchange trusted external OIDC assertions for Entra access tokens. It is material here because a CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret.
Authentication strengths let Conditional Access require supported strong methods based on conditions. Federated credentials exchange trusted external OIDC assertions for Entra access tokens.
B2B collaboration supports guest principals and cross-organization access controls. That statement describes External B2B partner, while the question asks how Workload identity federation works: Federated credentials exchange trusted external OIDC assertions for Entra access tokens.
App-only permissions grant service principal operations without a delegated signed-in user. Federated credentials exchange trusted external OIDC assertions for Entra access tokens.
An App Service must accept requests only through the corporate private network. A deployment must satisfy this operational criterion: Corporate users connect using private DNS and public clients are rejected. Which plan is appropriate?
Private endpoints provide a private inbound path for supported App Service access. The selected architecture is use an App Service private endpoint with private DNS and access restrictions; confirm the result by checking that corporate users connect using private DNS and public clients are rejected.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. That is useful for NSG subnet filtering (A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall). It does not meet the current Private inbound App Service requirement: An App Service must accept requests only through the corporate private network.
VNet integration is principally an outbound feature; inbound private access requires other controls. Its design target is VNet integration App Service. The stated requirement instead concerns: An App Service must accept requests only through the corporate private network.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. It does not solve the specified Private inbound App Service condition.
A deployed API must rotate an external vendor credential without checking a new secret into Git. Identify the most suitable implementation for an outcome where credential rotation works without modifying committed application configuration.
Central secret retrieval separates sensitive credentials from source and build artifacts. The selected architecture is reference Key Vault secrets using workload identity from the application; confirm the result by checking that credential rotation works without modifying committed application configuration.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. Its design target is API Management gateway. The stated requirement instead concerns: A deployed API must rotate an external vendor credential without checking a new secret into Git.
Asynchronous projections can lag writes and need clear read-after-write expectations. The relevant requirement is: A deployed API must rotate an external vendor credential without checking a new secret into Git.
Failure handling isolates unhealthy dependencies and avoids request pileups. It does not solve the specified Key Vault app secrets condition.
For the Network Watcher diagnosis requirement, the proposed architecture uses: Use Network Watcher connection troubleshoot and IP flow verify where supported. Why does that design fit?
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. It is material here because a connectivity failure may be caused by either NSG rules, routing or the remote endpoint.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Network Watcher diagnostic tools identify effective network behavior and filtering decisions.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. Network Watcher diagnostic tools identify effective network behavior and filtering decisions.
VNet peering alone is not transitive and forwarding needs explicit architecture. It belongs to Peering nontransitivity. The stated architecture instead relies on: Network Watcher diagnostic tools identify effective network behavior and filtering decisions.
For Container Apps microservice, operations are closing a change that addressed: Several HTTP container services need autoscaling and revisions without management of a full Kubernetes control plane. Which post-change signal belongs in the acceptance record?
Container Apps provides managed container hosting and microservice scale with KEDA capabilities. Confirm using the measurable result: A new revision handles traffic and scales down when request demand is low.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. The distinguishing check is: A new revision handles traffic and scales down when request demand is low.
Encryption sets connect managed disk encryption to customer-owned keys. The VM disk encryption test checks disk configuration shows the designated key and encrypted state before production traffic; the relevant outcome is A new revision handles traffic and scales down when request demand is low.
Blue-green deployment preserves a prior known-good instance while testing a replacement. The offered observation would demonstrate App deployment blue-green: A failed health check returns traffic to the prior application version. The current validation is different: A new revision handles traffic and scales down when request demand is low.
A finance table must retain previous versions of individual business records for an audit query. An architecture board will approve a solution only if this outcome is demonstrated: An as-of query reconstructs the record before an approved change. What should be selected?
Temporal tables retain row history and support as-of queries independently of whole-database backups. The selected architecture is use SQL system-versioned temporal tables with appropriate retention and permissions; confirm the result by checking that an as-of query reconstructs the record before an approved change.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. It does not solve the specified SQL temporal tables condition.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. The relevant requirement is: A finance table must retain previous versions of individual business records for an audit query.
CMK encryption protects database data at rest while keys are managed under customer control. The current need is: A finance table must retain previous versions of individual business records for an audit query.
Architecture review: Network-flow telemetry and Immutable evidence archive. Requirement A: Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture. Requirement B: Auditors require tamper-resistant retention of exported logs that are rarely queried. Which complete two-part proposal satisfies both constraints?
For requirement A, virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. For requirement B, storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. Verify both independently: A blocked test connection is correlated with its source destination and flow disposition; A retained log blob rejects unauthorized deletion during its compliance retention window.
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. The other proposed action (configure Container insights for the supported AKS cluster logging and telemetry) addresses a different operation. Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search.
The option covers one requirement but substitutes Web transaction traces for Network-flow telemetry. The missing acceptance result is: A blocked test connection is correlated with its source destination and flow disposition.
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The proposed steps (instrument the app with Application Insights request and dependency telemetry; configure Container insights for the supported AKS cluster logging and telemetry) address other capabilities instead of this required pair.
The target environment adopts this approach for Blob soft delete: Enable appropriate Blob and container soft-delete features within retention. What property makes it suitable?
Soft delete retains recoverable deleted objects or containers during the configured period. It is material here because a developer accidentally deletes a container and the organization wants short-term recovery.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. Soft delete retains recoverable deleted objects or containers during the configured period.
Versioning preserves older object versions independently of current content overwrites. Soft delete retains recoverable deleted objects or containers during the configured period.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. That statement describes Cosmos autoscale, while the question asks how Blob soft delete works: Soft delete retains recoverable deleted objects or containers during the configured period.
Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways. The acceptance test is: Private IP traffic flows between the peered VNets with appropriate NSG permissions. Which design recommendation best satisfies both?
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. The selected architecture is use VNet peering or global VNet peering under the supported region topology; confirm the result by checking that private IP traffic flows between the peered VNets with appropriate NSG permissions.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. It does not solve the specified VNet peering condition.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. That is useful for Front Door WAF edge (A public application must block common HTTP attacks before traffic reaches regional origins worldwide). It does not meet the current VNet peering requirement: Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. The relevant requirement is: Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways.
Please check your mailbox for a message from support@examlabs.com and follow the directions.