Microsoft AZ-801 Exam Prep
Configuring Windows Server Hybrid Advanced Services (Page 2 )

• Connection Security Rules (IPsec) are separate from inbound file-sharing rules. You don’t need an IPsec rule on Server3 to access SMB shares.
• File shares are allowed by inbound firewall rules on the destination. If Server1 has an inbound SMB rule (SMB-In) that permits traffic on port 445, Server3 can connect as long as authentication/permissions succeed.
• If there’s an Isolation-type connection security rule on Server1, it would apply only if the traffic must be authenticated via IPsec. In this scenario, the SMB-In rule suffices.

• On Server1: run Get-NetFirewallRule -DisplayName "SMB" to confirm SMB-In is enabled.
• Test connectivity to the SMB port: Test-NetConnection -ComputerName Server1 -Port 445.
• Ensure Server3 is domain-joined (if an Isolation rule exists, it will still allow domain-joined machines).

• The issue involves a P2S connection from Computer1 to access AppSvr2 in another VNet. Re-downloading and reinstalling the VPN client ensures the latest VPN profile/routes are applied for cross-VNet access.
• The other options are not correct fixes for P2S cross-VNet reachability: routing via GatewaySubnet isn’t how P2S routes are configured, and service endpoints don’t establish inter-VNet VPN connectivity.

• Third-party attestation: Provides independent validation, but is typically periodic and performed by an external party.
• Penetration testing: Simulates attacks to identify exploitable vulnerabilities; it does not primarily track compliance.
• Vulnerability scans: Identify technical weaknesses, but do not provide a detailed review of procedures or compliance activities.

Manager role

DAX 
Country[Manager] = USERPRINCIPALNAME()

• Sales
• Human Resources

CFO role

• See sales for all countries
• See no Human Resources data

• Do not restrict the Country table or Sales table.
• Apply a filter to Human Resources that always returns false, such as:

DAX 
FALSE()

• B. Deploy to a SageMaker endpoint: This is needed for SageMaker-hosted models, not for a model intended to be used directly in Amazon Bedrock.
• C. Register with SageMaker Model Registry: SageMaker Model Registry is unrelated to invoking custom models in Bedrock.
• D. Grant access in Bedrock: Access permissions may be necessary, but they do not replace the required provisioned capacity.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

• True positive: The scan reports a vulnerability that really exists.
• False positive: The scan reports a vulnerability that does not exist.
• True negative: The scan correctly reports no vulnerability.
• False negative: The scan fails to detect a vulnerability that is actually present.

• Crowd-sourced evaluation: Requires recruiting and managing many evaluators.
• Human-worker evaluation: Provides human judgment but requires coordination, labeling instructions, and quality control.
• RLHF: Is a training and alignment process, not simply a low-overhead model comparison method.
• Automatic model evaluation: Quickly evaluates outputs using predefined toxicity or quality metrics with minimal manual effort.

apex 
for (Account updatedAccount : Trigger.new) { 
    AccountTriggerHelper.notinyxternalSystem(updatedAccount.Id); 
}

• Too many callouts: The callout occurs asynchronously in the future method, and each future transaction can perform its permitted callouts.
• Too many SOQL queries: The SOQL query is inside the future execution, not repeatedly in the trigger transaction.
• Callout from triggers not supported: Direct callouts from triggers are prohibited, but the trigger delegates the callout to asynchronous Apex, which is the correct pattern.

• CBWFQ (Class-Based Weighted Fair Queuing): Creates traffic classes and assigns each class a guaranteed bandwidth or queueing treatment.
• PQ (Priority Queuing): Uses multiple queues with strict priority. Higher-priority queues are serviced before lower-priority queues, making it useful for delay-sensitive traffic—but it can starve lower-priority traffic.

• FRTS: Traffic shaping for Frame Relay; it controls the transmission rate rather than selecting packets during congestion.
• CAR: Polices traffic by rate, typically dropping or remarking packets that exceed a limit.
• PBR: Policy-Based Routing; it selects forwarding paths and is not a QoS queueing mechanism.

• Malware or malicious software
• Command-and-control tools
• Internet surveillance and intrusion software

• ITAR: A U.S. regulation controlling defense-related articles and services; it is not the international arrangement described.
• Palermo Convention: Focuses on transnational organized crime and related protocols, not export controls for cyber weapons.
• GDPR: European data-protection and privacy legislation.

• CHAP: Uses a challenge-response exchange, so the password is not directly transmitted.
• IPsec: Provides authentication, integrity, and encryption for IP communications.
• EAP: An authentication framework that supports stronger methods, such as certificates or token-based authentication.

• A static IP gives the surveillance system a predictable local address, so users can reliably reach it on the LAN.
• However, a static IP does not block internet-based login attempts. If the router exposes the device through port forwarding, attackers could still reach it.
• Port mapping normally exposes an internal service externally, so A is a poor choice as written.
• Subnetting alone also does not block traffic; it would require routing/firewall rules.

• Recovery Services vault — stores Site Recovery configuration and recovery metadata.
• Hyper-V site — represents the on-premises Hyper-V environment.
• Azure virtual network — the target network where the replicated VM will run after failover. Since Azure VMs already use the same virtual network, that VNet can be selected as the target.
• Storage account or managed-disk target, depending on the ASR configuration and portal version.
• Provider/agent on the Hyper-V server — enables replication from Hyper-V to Azure.

• PC A: 192.168.1.10/24
• PC B: 192.168.2.10/24

• Both PCs have a correct default gateway
• A router or Layer 3 switch connects the subnets
• Routing and firewall rules allow the traffic

• A — Securing information assets: This is the responsibility of management and operational/security teams.
• B — Validating protection: Correct. The auditor checks whether controls—such as access restrictions, encryption, retention, and handling procedures—match the asset’s classification.
• C — Ensuring alignment with regulations: Management and legal/compliance functions typically establish classification requirements; the auditor may assess compliance but does not primarily define alignment.
• D — Defining classification levels: This is a management responsibility based on business needs, risk, and regulatory obligations.

• Undefined or blank values
• Relationship matching problems
• Duplicate or conflicting keys
• Errors when querying the model

• Normalize all values to upper- or lowercase in the source query or Power Query.
• Add an index or surrogate key when values that differ only by case must remain distinct.

• IRR assumes that interim cash flows can be reinvested at the project’s own IRR. This may be unrealistic, especially when the IRR is very high.
• MIRR assumes reinvestment at a specified rate, usually the company’s cost of capital or another realistic reinvestment rate.

• B: MIRR does not specifically favour projects with long payback periods.
• C: MIRR and IRR can rank competing projects differently.
• D: MIRR is not always higher than IRR; it may be higher or lower depending on the cash flows and reinvestment rate.

• Microsoft manages the physical datacenter, hardware, and virtualization.
• You manage the virtual machine’s operating system, installed software, configuration, and data.
• You choose the VM size, storage, networking, and scaling options.

• SaaS: You consume a complete application managed by the provider, such as Microsoft 365.
• PaaS: You deploy applications without managing the underlying operating system or VM infrastructure, such as Azure App Service.

• A. Continue using the current system: It will eventually fail and offers no recovery strategy.
• B. Virtualize the entire system: Correct. A VM can preserve the old OS, application, settings, and dependencies while running on newer physical hardware.
• C. Containerize the application: Containers generally share the host OS kernel and are not suitable for preserving an entire incompatible legacy OS.
• D. Clone the disks to USB: A disk clone may provide backup or temporary recovery, but it does not solve hardware compatibility or provide a reliable long-term platform.

• User-generated content: precisa ser coletado, filtrado, anonimizado e rotulado.
• Moderation logs: podem conter dados inconsistentes, informações pessoais e decisões que precisam ser revisadas.
• Content moderation guidelines: são regras ou orientações, não dados diretamente utilizáveis para medir o comportamento do modelo.

• Third-party enterprise application with embedded AI: The provider manages most security controls. The customer mainly manages users, data, and configuration.
• Application using an existing third-party FM: The customer controls the application and its inputs/outputs, but the provider controls the underlying model and infrastructure.
• Fine-tuning a third-party FM: The customer has additional responsibility for training data, data protection, and model behavior, but still depends on the provider’s base model and platform.
• Building and training a model from scratch: The customer controls the model, training data, application, deployment, and many security safeguards. This creates the greatest security ownership.

• Deterministic approve/reject results
• Strict adherence to predefined rules
• Consistent, reproducible outcomes
• Auditability and regulatory compliance

1. Discovery tries the SSH probe first.
2. SSH fails.
3. Discovery tries SNMP, which succeeds.
4. Discovery records SNMP as the preferred service for that IP.
5. Future discoveries try SNMP first.

• Classification identifies the type of device, such as a server, router, or printer.
• Credential affinity remembers which credentials work for a device.
• MID Server affinity associates a device or network with a particular MID Server.
• IP service affinity specifically controls the preferred discovery protocol or service.

• The S3 bucket as an origin for static content
• The Application Load Balancer (ALB) as an origin for dynamic content
• An Amazon Route 53 alias record pointing the application domain to CloudFront

Why this works

• Static data: CloudFront caches objects from S3 at edge locations, reducing latency for users worldwide.
• Dynamic data: CloudFront forwards requests that require application processing to the ALB. It can also maintain persistent connections and use the AWS global edge network to improve delivery performance.
• One domain: CloudFront behaviors can route different path patterns to different origins—for example, /static/* to S3 and other paths to the ALB.

Why the other options are incorrect

• Global Accelerator is designed primarily for accelerating traffic to applications with endpoints such as ALBs, not for caching S3 content.
• Using separate domains or splitting static and dynamic traffic adds unnecessary complexity.
• CloudFront already provides the required global edge distribution and caching, so combining it with Global Accelerator is unnecessary here.

• One network address
• Two usable host addresses—one for each router
• One broadcast address

• Router A: 10.2.1.1
• Router B: 10.2.1.2

• Managerial: policies, standards, risk management, governance
• Operational: procedures carried out by people, such as training, incident response, and backups
• Technical: firewalls, encryption, access-control systems
• Physical: locks, guards, cameras

• Label applied does not automatically exclude a file from Copilot.
• Encryption/usage rights determine whether Copilot can access the file’s content.
• If the user has no permission under Label2, File3 should be unavailable to Copilot for that user.
• File3’s label might be inherited by derived content only if File3 was actually processed and contributed by an authorized user; it should not be treated as contributing merely because it exists in the source set.

• Storage usage of files stored in Microsoft Teams: SharePoint site usage report

• Number of active users per team: Microsoft Teams usage report

1. SharePoint site usage report
2. Microsoft Teams usage report

• Future costs — Only costs occurring in the future can be affected by the investment decision. Past costs are sunk and irrelevant.
• Incremental costs — These are additional costs caused by choosing the investment. They are relevant because they differ between alternatives.
• Cash flows — Capital investment decisions are based on future cash inflows and outflows, usually discounted to present value.

• Committed costs have already been agreed or incurred and generally cannot be changed by the decision.
• Unavoidable costs will arise regardless of which option is selected, so they do not affect the choice.

Correct reasoning

• Create storage5 as a General-purpose v2 (StorageV2) account.
• Configure Blob object replication from storage5 to an existing compatible storage account.
• The destination must support object replication—typically another StorageV2 or premium block blob account.
• Blob versioning must be enabled on both accounts.
• Blob change feed must be enabled on the source account.
• The accounts must meet Azure’s object-replication requirements, including being in supported regions and having compatible configuration.

Correct sequence

1. Merge Sales_Region with Sales_Manager using an inner join

1. Merge Region_Manager with Manager using an inner join

1. Merge Sales_Region and Region_Manager using a right join as a new query

• A — Increased call deflection: o KCS disponibiliza conhecimento reutilizável para clientes e agentes, ajudando a resolver dúvidas sem abrir ou continuar chamadas.
• C — Reduced issue resolution time: os representantes reutilizam artigos e soluções já documentadas, acelerando o atendimento.
• E — Optimized use of resources: o conhecimento compartilhado reduz retrabalho e melhora o uso dos recursos da equipe.

• Accept terms of use
• Enter a temporary code or credentials
• Provide basic registration information

• Enterprise authentication — Authenticates organizational users, often with centralized identity services; it is not specifically designed for temporary guest access.
• Ad hoc network — A temporary device-to-device network, not an authentication process.
• WPA3 — A wireless security standard. It protects Wi-Fi access but does not provide the web-based temporary access workflow described here.

• Help the team identify the root causes of delays.
• Empower the team to improve its workflow and practices.
• Facilitate removal of impediments.
• Avoid directing the team toward a solution without its involvement.
• Protect quality and sustainable delivery rather than simply accelerating everything.

• A: An impediment log may help, but merely recording problems does not empower the team to solve them.
• B: Directing the team to solutions conflicts with self-management.
• C: Adding impediments to the product backlog may incorrectly treat internal obstacles as product features and delays their resolution.

• Enforce organizational rules, such as allowed regions or required tags
• Audit resources for compliance
• Deny noncompliant deployments
• Aggregate compliance results across subscriptions

DAX 
Blue Sales = 
CALCULATE( 
    [Total Sales], 
    KEEPFILTERS('Product'[Color] = "Blue") 
)

• CALCULATE evaluates [Total Sales] after applying an additional filter.
• 'Product'[Color] = "Blue" restricts the calculation to blue products.
• KEEPFILTERS ensures the existing filter context is preserved. For example, filters for year, region, or customer remain active. If Color is already filtered, the blue condition is applied as an intersection rather than replacing the existing filter.
• Avoid ALL, because it removes filters and would not maintain the existing context.

• Honeypots: Decoy systems or services designed to attract attackers. Legitimate users should not access them, so activity there is a strong indicator of compromise.
• DNS sinkholes: Redirect malicious or suspicious DNS requests to a controlled destination. This can identify infected systems attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it is not an attacker-detection method.
• CI/CD: Automates software development, testing, and deployment.
• Threat modeling: Identifies potential threats and weaknesses before or during system design; it does not directly detect an active infiltrator.
• Data obfuscation: Makes information harder to understand, but does not identify attackers.

• Prevention costs: Avoiding defects, such as staff training and improved product design. The company has invested in these.
• Appraisal costs: Detecting defects before products reach customers, such as inspection and testing. The planned batch sampling has not been implemented.
• Internal failure costs: Correcting defects found before delivery.
• External failure costs: Dealing with defects after delivery, such as refunds, replacements, complaints and lost sales.

• Sales process: Controls which Opportunity Stage values are available.
• Record type: Associates the appropriate sales process with a business scenario and controls available picklist values.
• Page layout: Controls which fields are displayed and whether they are required or read-only.

• Energy Market Team 1 ? Record Type 1, Sales Process 1, Page Layout 1
• Energy Market Team 2 ? Record Type 2, Sales Process 2, Page Layout 2
• Services/Installation Team ? Record Type 3, Sales Process 3, Page Layout 3

• Which host first communicated with the suspected malicious source
• Whether that host initiated suspicious traffic or merely received it
• Which other hosts show evidence of infection, such as connections from the originating host
• Which hosts have no related suspicious activity and are therefore clean

• An outbound connection to a suspicious external address
• A downloaded or executed malicious file
• Later lateral connections from that host to other internal systems
• Firewall logs showing the direction and timing of the traffic

• The CSV contains the external users’ email addresses.
• The bulk invitation feature supports inviting many guest users in one operation.
• Each invited user becomes a guest account in contoso.com.

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Moving the risk’s financial impact to a third party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or employee training.
• Avoid: Eliminating the activity that creates the risk.

• A: It allows for branching and merging...

• C: It allows multiple engineers to work against the same code and configuration files and manage differences and conflicts.

• B: Build automation and infrastructure provisioning are handled by CI/CD and automation tools, not by version control alone.
• D: User Stories and backlogs are managed by project-management tools.
• E: Version control stores and tracks code, but it does not itself ensure that developers write effective unit tests.

• miami.weyland.com requires a custom domain, which is not available in the Free tier.
• Two instances require a tier that supports scaling out. Standard supports multiple instances.
• SSL support is available in Standard.
• 12 GB of storage exceeds the storage limit of the Basic tier in the older Azure pricing model used by this question.
• Standard provides sufficient storage and features while being cheaper than higher tiers—though higher tiers are not listed here.

• Free/Shared: insufficient features for custom domains, SSL, and multiple instances.
• Basic: supports some production features, but its storage capacity is insufficient for the required 12 GB.

• 10.2.1.0 — network address
• 10.2.1.1 — usable host
• 10.2.1.2 — usable host
• 10.2.1.3 — broadcast address

• contoso.onmicrosoft.com
• contoso1.onmicrosoft.com

• onmicrosoft.com domains: Maximum of five per tenant.
• Custom domains: Domains that your organization owns and verifies in Microsoft 365.

• SAS (Serial Attached SCSI):

• SSD (solid-state drive):

• Share of overall contribution: part of the organization’s total contribution is allocated to the supplying division.
• Dual pricing: the supplying division may record a higher transfer price while the receiving division records a lower price, with central accounts absorbing the difference.
• A centrally imposed price range: this may allow the transfer price to be set above variable cost, helping the supplying division recover fixed costs.