Microsoft MB-335 Exam Prep
Microsoft Dynamics 365 Supply Chain Management Functional Consultant Expert (Page 27 )

• VM CPU, memory, disk, and network usage
• Storage transactions and latency
• App Service response time
• Database DTU or CPU utilization

• Azure Traffic Analytics analyzes network traffic flows and security patterns; it is not the general infrastructure metrics tool.
• Azure Activity Log records subscription-level control-plane operations, such as resource creation, deletion, or configuration changes.
• Azure Advisor provides recommendations about cost, security, reliability, performance, and operational excellence, but it is not the primary tool for investigating live metrics.

• DB1 (500 TB): Azure Data Box Heavy

• Virtual machines: Azure Migrate

• C series: CPU-optimized instances; not designed primarily for LLM training.
• G series: GPU instances generally optimized for graphics and some machine learning workloads, but not specifically large-scale model training efficiency.
• P series: Powerful GPU instances for ML training, but typically consume more energy than Trainium-based instances for suitable training workloads.

• CCTV system — Detective control: Cameras monitor and record activity, helping identify or investigate security incidents after—or while—they occur.
• Signs about being filmed — Deterrent control: The signs discourage people from attempting unauthorized or criminal activity because they know surveillance is present.

• Preventive: Stops an incident from occurring, such as a lock or access-control system.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: Provides an alternative control when the preferred control cannot be implemented.

• C — Some risks cannot be eliminated.

• D — Accepting residual risk does not imply recklessness.

• E — Most companies in this industry will say something similar.

• NIDS: Monitors network traffic for suspicious activity and network-based attacks targeting the application or its supporting services.
• HIPS: Protects an individual host by monitoring processes, files, and system activity. It can help secure the web server, but it is not focused specifically on the application’s network attack surface.
• SIEM: Aggregates and correlates logs; it does not directly prevent attacks.
• Honeypot: A decoy system, not the primary protection for a production web application.
• Certificate revocation list: Deals with certificate trust, not application exploitation.

• A: Configure security groups — Customers define inbound and outbound rules for resources such as Amazon EC2 instances.
• B: Classify company assets — Customers decide how their data and assets should be classified and protected.

• C: Amazon S3 is a regional service; customers select a Region, not individual Availability Zones for buckets.
• D: AWS manages the infrastructure and patching for Amazon DynamoDB.
• E: AWS manages the infrastructure used by AWS Lambda; customers do not select EC2 instances for Lambda functions.

• A: My Domain is required for many SSO configurations, but if SSO works, it is unlikely to be the cause of losing the target record.
• B: HTTP-POST is a valid SAML binding and does not inherently prevent redirection.
• D: An incorrect Federation ID generally causes authentication or user-matching failure—not successful login to the home page.

• SharePoint search: Finds documents based on search terms, but it does not reliably identify every 32-character account number for DLP enforcement.
• A hunting query in Microsoft 365 Defender: Used for security investigations, not for defining sensitive content in a DLP policy.
• Azure Information Protection: Uses classification and labeling; it does not automatically identify this specific account-number pattern unless configured with a matching sensitive information type.
• RegEx pattern matching: Best suited for structured identifiers with a known format, such as account numbers, employee IDs, or policy numbers.

• Resources that do not need internet access should remain on private network segments.
• Internet-facing access should be restricted to systems that require it.
• Access should be explicitly allowed rather than broadly exposed.

• A: A single administrator with access to core functions may violate least privilege if that access is broader than necessary.
• B: Inspecting traffic supports monitoring and defense, but does not itself limit privileges.
• C: Updating routing configurations supports availability and connectivity, not least privilege.

• Suspended an operator who refused to use unsafe equipment.
• Paid another operator a bonus for using it.
• Prioritised short-term productivity over employee safety.

• A — Management is not particularly concerned with managing risks.

• B — Employees will perceive that management does not care about health and safety risks.

• C — The factory’s safety record is likely to be poor.

• A — Correct: Flow Builder is declarative and visual, so administrators and other non-developers can participate in designing and improving business processes without writing Apex.
• D — Correct: Flow Builder provides visual debugging tools, allowing an admin to test paths, inspect variable values, and identify where a specific business case fails.
• E — Correct: A flow’s visual structure documents the logic and makes later maintenance easier than reading and updating custom Apex code.

• B — Incorrect: Flow debugging does not attach a debugger to live customer sessions. The admin uses Flow Builder’s debug functionality with test inputs; this is not live-session debugging and should not be used to monitor real customer transactions.

1. Clear principles and boundaries — Employees have freedom, but decisions must remain within clear organizational values, policies and limits.
2. High degree of freedom — Managers are trusted to make decisions rather than seeking continual approval from senior management.
3. Frontline customer responsibility — Customer-facing managers should be empowered to manage customer relationships and respond quickly to needs.
4. Transparent and ethical information — Information should be openly available and used honestly, supporting trust and informed decision-making.

• Tactics: The attacker’s overall goal, such as gaining persistence or exfiltrating data
• Techniques: The methods used to achieve that goal
• Procedures: The specific implementation or sequence of actions

• IP addresses and hash values: Useful indicators, but they can change quickly.
• Indicators of compromise: TTPs may help identify IOCs, but their main value is describing behavior.
• Tools: Attackers can replace tools or use legitimate administrative utilities.

• Reviewing security policies and standards checks whether controls are documented, not whether they work.
• Reviewing security logs may show that monitoring is occurring, but does not directly establish that preventive controls are effective.
• Analyzing technical security practices is broad and may assess implementation, but it is less objective than an actual controlled attack.

• Design/compliance effectiveness: policies, standards, and procedures
• Operational effectiveness: logs, records, and evidence that controls operate
• Technical security effectiveness: penetration testing or vulnerability testing

• Server provisioning
• Operating systems and runtime infrastructure
• Scaling
• Much of the maintenance and patching

• Thin clients reduce endpoint hardware requirements but do not specifically streamline code deployment.
• Private cloud provides dedicated cloud infrastructure but usually requires more management and expense.
• Virtual machines improve resource utilization, but administrators still manage the VMs, operating systems, and deployments.

sql 
CREATE PROCEDURE dbo.usp_CreateOrder 
AS 
BEGIN 
    SET NOCOUNT ON; 
    SET XACT_ABORT ON; 


    BEGIN TRY 
        BEGIN TRANSACTION; 


        INSERT INTO dbo.Orders (/ columns /) 
        VALUES (/ values /); 


        SET @OrderID = SCOPE_IDENTITY(); 


        COMMIT TRANSACTION; 
    END TRY 
    BEGIN CATCH 
        IF @@TRANCOUNT > 0 
            ROLLBACK TRANSACTION; 


        THROW; 
    END CATCH; 
END;

• BEGIN TRY contains the transactional work.
• SCOPE_IDENTITY() retrieves the identity generated by the INSERT; it belongs after the insert, not as the error-handling logic.
• COMMIT runs only if all statements succeed.
• BEGIN CATCH handles failures.
• IF @@TRANCOUNT > 0 prevents attempting a rollback when no transaction is active.
• ROLLBACK undoes partial changes.
• THROW re-raises the original error with consistent details for the application.
• SET XACT_ABORT ON ensures many run-time errors automatically terminate and roll back the transaction.

1. Find the subnet-mask increment in the octet where the prefix ends.
2. Identify the network address by finding the subnet boundary at or below the given IP.
3. The first usable address is network address + 1.
4. The broadcast address is one address before the next subnet.
5. The last usable address is broadcast - 1.

• 172.28.228.144/18

• 172.28.228.144/23

• Cloud architecture
• Data architecture
• Platform engineering
• Data engineering
• Provisioning and modernization

• Data protection is associated mainly with security and risk management.
• Data governance belongs to the governance perspective.
• Data science is not an AWS CAF capability.

• Install unauthorized or unapproved applications
• Access system areas normally restricted
• Add features unavailable in the default software
• Modify the device’s operating system

• SQL injection (SQLi): Attacks databases by inserting malicious SQL commands.
• Cross-site scripting (XSS): Injects malicious scripts into web pages viewed by users.
• Sideloading: Installs an application from outside the official app store, but it does not necessarily remove the phone’s operating-system restrictions.

• The product is already in production.
• The organization is examining the product’s functions and cost drivers.
• The objective is to reduce cost without reducing perceived value or required quality.

• Kaizen costing focuses on continuous, usually incremental, cost reductions during the manufacturing stage. It is not specifically the systematic examination of a product’s functions.
• Standard costing compares actual costs with predetermined standards; it is a control technique, not a product redesign method.
• Process innovation concerns developing significantly improved production processes, rather than analysing the product’s functions and value.

• Scheduling overlapping working hours for critical collaboration
• Assigning independent tasks that can proceed asynchronously
• Adding clear handoffs between offices
• Documenting decisions, questions, and required inputs
• Building appropriate time into the schedule for responses

• GPU: A failure may cause no video output, but the PC usually still powers on.
• RAM: Can prevent booting or produce error beeps, but fans and power indicators generally work.
• CPU: Can prevent startup or booting, but it usually does not cause a completely lifeless system.

• CSIRT: A team that responds to and manages security incidents.
• CVSS: A scoring system for rating the severity of vulnerabilities.
• SOAR: A technology platform for automating and coordinating security operations and incident response.

• 2000::/3 — Global unicast, used for publicly routable IPv6 addresses.
• FC00::/7 — Unique local, used for private internal addressing.
• FE80::/10 — Link-local, used only on the local network segment and not routed between subnets.

• 16GB RAM: A 64-bit OS is needed to use more than roughly 4GB effectively, but RAM capacity does not prove the CPU supports 64-bit operation.
• 500GB HDD: Storage capacity has no bearing on OS architecture.
• 1Gbps Ethernet: Network speed is unrelated to CPU architecture.

json 
"Resource": "arn:aws:s3:::bucket-name/*"

• A: Revoking or changing an instance profile does not reliably invalidate temporary credentials that have already been issued and may still be valid.
• B: Changing the EC2 security group does not necessarily stop the attacker from using the stolen credentials from elsewhere.
• C: Amazon Macie helps discover sensitive data; Object Lock prevents modification/deletion, not reads or downloads.

• Field name and label
• Data type
• Reference table
• Default value
• Whether the field is mandatory or read-only
• Field attributes and configuration

• A: Labels and translations are handled through documentation and translation-related records.
• C: Table relationships may be represented through reference fields, but this is not the primary description of the Dictionary.
• D: Spell-checking language data is unrelated to the System Dictionary.

• Custom domain: miami.weyland.com requires a paid App Service tier; Free and Shared are unsuitable.
• Two instances: Standard supports scaling to multiple instances.
• SSL: Standard includes SSL support.
• 12 GB storage: Basic provides only about 10 GB, so it does not meet the requirement. Standard provides substantially more storage.
• Cost minimization: Standard is the lowest tier among the choices that satisfies all requirements.

• Data loss prevention (DLP): Helps detect or prevent sensitive data from being copied or transmitted, but it does not primarily protect a stolen laptop’s stored data.
• Operating system hardening: Reduces vulnerabilities and attack surface but does not encrypt files if the device is stolen.
• Boot security: Helps ensure that only trusted software starts, but it does not fully protect the drive if an attacker accesses it offline.

• Honeypots: Decoy systems or services made to attract attackers. Legitimate users should not interact with them, so activity there is a strong indicator of malicious behavior.
• DNS sinkholes: Redirect requests for known malicious domains to a controlled internal system. This can reveal infected hosts attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens.
• CI/CD: Automates software development, testing, and deployment.
• Threat modeling: Identifies and analyzes potential threats before or during system design.
• Data obfuscation: Makes data harder to understand or interpret.

• Aggregation happens once, during the scheduled job.
• Dashboard users query a relatively small, precomputed table.
• Repeated users do not trigger expensive aggregations against the detailed sales table.
• Overwriting is appropriate because the summary is rebuilt for the reporting period.

• B: Structured Streaming is unnecessary for data that only needs daily refreshes and adds operational/compute overhead.
• C: A view recomputes the aggregation at query time, increasing latency and query cost.
• D: Delta caching may improve reads but does not replace the need to materialize the expensive aggregation, and cache availability is not the main design guarantee.

• Create a CodeCommit repository in the secondary Region.
• Use CodeBuild to run a Git mirror operation from the primary repository to the secondary repository.
• Use EventBridge to detect relevant repository events, such as a pull request being merged.
• Invoke a Lambda function, which starts the CodeBuild project.

• B: Amazon S3 is object storage, not a Git repository that developers can use as a CodeCommit remote.
• C: CodeArtifact is intended for packages and artifacts, not source-code repository mirroring.
• D: An AWS Cloud9 environment is not an appropriate automated replication mechanism and would require manual or persistent infrastructure management.

• Keep earlier prompt versions.
• Identify the last version that produced acceptable output.
• Restore it as a baseline.
• Make small, controlled changes—ideally one significant change at a time.
• Test the output after each change.

• A: Discards useful information about what worked.
• B: Large simultaneous changes make it difficult to identify the cause of problems.
• D: Accepts output that does not meet the requirements.

• Understating expenses and liabilities
• Overstating profit
• Misleading users of the financial information
• Potentially breaching integrity, objectivity, and professional competence and due care

1. Create or verify cost groups

1. Set up the item model group

1. Create the costing version

1. Enter or calculate item costs

1. Activate the standard costs

• Remote and global work: Access is based on the approved device, not a specific office or geographic location.
• Seamless login: Users may not need to repeatedly enter credentials on a recognized device.
• Limited equipment: It uses devices employees already have rather than requiring separate hardware.

• Geotagging: Restricts access based on location and may prevent legitimate remote work.
• Smart cards: Require issuing and managing additional physical equipment.
• Time-based logins: Limit access by time and do not provide a seamless authentication experience.

• AWS Network Firewall can inspect and block traffic across a VPC when traffic is routed through the firewall. A Drop action rule can deny traffic from the suspicious source IP.
• GuardDuty findings are sent to Security Hub.
• A Lambda function can be invoked when Security Hub receives a new GuardDuty finding, extract the source IP, and update the Network Firewall policy with a blocking rule.

• GuardDuty threat lists: Used to identify or increase the severity of findings; they do not directly block VPC traffic.
• AWS WAF: Protects supported web applications, such as CloudFront or Application Load Balancers. It does not provide general VPC-wide traffic blocking.
• GuardDuty suppression rules: Suppress or hide findings. They do not block the suspicious traffic.

Statement 1 — Correct

Statement 2 — Correct

• Code signing: Verifies the software’s authenticity and integrity; it does not hide the source code or prevent reverse engineering.
• Tokenization: Replaces sensitive data with tokens, mainly for protecting data such as payment information—not software logic.
• Blockchain: Provides a tamper-resistant record of transactions or data; it does not protect compiled code from analysis.

• Works across SaaS and internal applications: TOTP is widely supported by authentication systems and can be integrated into many applications.
• Device manufacturer agnostic: A hardware token or authenticator application can generate the code without depending on a specific computer or phone manufacturer.
• Offline capability: The code is generated locally using a shared secret and the current time; an internet connection or cellular service is not required.

• Username and password: May work offline but provides weaker authentication and does not meet the intended improvement in security.
• Biometrics: Can depend on device hardware, operating-system support, and enrollment mechanisms.
• SMS verification: Requires cellular connectivity and is vulnerable to threats such as SIM swapping.

• A Layer 2 switch checks the destination MAC address in its MAC address table (CAM table).
• If the destination MAC is unknown, the switch cannot select a specific outgoing port.
• It therefore performs unknown-unicast flooding, sending the frame out every other port in that VLAN.
• The frame is not sent back through the port where it arrived.

• MAC flooding: Overwhelms a switch’s MAC address table, potentially causing traffic to be broadcast.
• DNS spoofing: Provides false DNS responses to redirect users.
• ARP poisoning: Sends false ARP information to associate an attacker’s MAC address with another device’s IP address.

• B. Versioned configuration files — Infrastructure is defined in machine-readable files and tracked in version control, allowing repeatable provisioning and change history.
• D. Docker files — Assuming “Doctor files” is a typo for Dockerfiles, a Dockerfile declaratively defines how to build a container image and is commonly considered infrastructure/configuration as code.

• A. Cloned virtual machine images — These are prebuilt infrastructure artifacts, but cloning an image is not itself a code-based infrastructure definition.
• C. Change management database records — A CMDB records information about infrastructure; it does not define or provision that infrastructure.

• C: Develop the rule in the Rules Editor, define the events, match, and condition sections, then use the test rule feature. This directly validates the YARA-L rule without enabling it in production.
• A: UDM Search can help investigate data and refine filters, but it does not fully test YARA-L logic—especially complex event joins, match windows, and conditions.

1. Open the Microsoft Entra Connect wizard.
2. Select Configure.
3. Choose Customize synchronization options.
4. Authenticate when prompted.
5. On the Domain and OU filtering page, select:

1. Complete the wizard.

• Start-ADSyncSyncCycle only starts synchronization; it does not change which OUs are included.
• Manage federation configures federation settings, which are unrelated to OU filtering.
• Add-ADSyncConnectorAttributeInclusion concerns connector attributes, not selecting additional OUs for synchronization.

• Authentication — verifies who the user is.
• Authorization — determines what the authenticated user is allowed to access.
• Accounting — records session activity, such as login time and resource usage.

• CIA — confidentiality, integrity, and availability; core security objectives.
• ACL — access control list; rules that permit or deny traffic or access.
• PEM — Privacy Enhanced Mail, an older email security standard.

• 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.

• Fileless malware: Nothing in the command indicates malware executing only in memory.
• Living-off-the-land binaries: Mimikatz is a credential-access tool, not a normal system utility used for LOLBin abuse.
• Social engineering: The command shows technical credential abuse, not manipulation of an accountant.