VMware 1V0-701 Exam Prep
VMware Certified Associate - Digital Business Transformation Exam (Page 2 )

• Reporting relationships
• Organizational structures
• Leadership styles
• Team maturity
• Individual and group behavior
• Communication and motivation

• Acquire Project Team: Focuses on obtaining the people needed for the project.
• Develop Project Team: Focuses on improving team skills, relationships, and performance.
• Manage Project Team: Focuses on tracking performance, resolving issues, and managing changes within the team.

• Disable default accounts: Default or unused accounts may have known usernames or predictable settings, making them targets. They should be disabled, removed, or securely configured.
• Remove unnecessary services: Every running service creates potential vulnerabilities. Removing services the server does not need reduces exploitable entry points.

• Add the server to the asset inventory: Important for asset management, but not a hardening step.
• Document default passwords: Default passwords should be changed or eliminated—not documented for continued use.
• Send server logs to the SIEM: Valuable for monitoring and detection, but generally performed as part of logging/monitoring configuration.
• Join the server to the corporate domain: May be necessary operationally, but does not itself harden the server.

• User2 is in Group1, so CA2 applies.
• CA2 targets Office 365.
• CA2 requires MFA OR an app protection policy.
• User2 has no app protection policy, but if User2 successfully completes MFA, the OR condition is satisfied.
• The device being noncompliant does not matter because CA2 does not require device compliance.
• CA1 applies only to Global Administrators. Unless User2 is also a Global Administrator, CA1 does not apply.

• Floating IP must be enabled on the load-balancing rule.
• Session persistence should normally remain None.
• The health probe determines which replica should receive traffic.
• Client-IP persistence is unnecessary and can cause connections from the same client to remain associated with a backend replica longer than intended.

• Q9 — Client IP session persistence: No
• Q10 — Floating IP: Yes

• MFA: Protects sign-in and authentication.
• Azure Key Vault: Protects deployment secrets and credentials.
• Answer: No (B).

• The users currently have Office 365 Enterprise E3 licenses assigned directly.
• Assigning Microsoft 365 Enterprise E5 through a group does not automatically remove their directly assigned E3 licenses.
• From the Licenses blade, you can select the E3 product and remove it from all assigned users in one operation. This requires less effort than editing 2,500 users individually.

• Identity Governance manages access reviews, entitlement management, and related governance—not bulk license removal.
• Set-AzureAdUser does not remove product licenses.
• Set-WindowsProductKey applies Windows product keys and is unrelated to Microsoft 365 licensing.

• Red team: Offensive security; attempts exploitation and simulates attackers.
• Blue team: Defensive security; monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team activities to improve defenses, but is not the best direct answer here.
• White team: Usually oversees or coordinates an exercise, including rules of engagement and scope.

• The load balancer provides the listener’s frontend IP address.
• The active SQL Server node must also respond to that same listener IP.
• Enabling Floating IP allows the listener IP to be preserved and handled correctly by the active replica.
• Without it, SQL connections may be sent to a node that cannot correctly claim the listener address.

• A health probe for the SQL Server port
• A load-balancing rule using the listener port
• Floating IP enabled on that rule

1. Start with the number of devices: 260 usable addresses.
2. Use the formula:

1. Test the host-bit values:

1. IPv4 has 32 total bits:

• /24: 254 usable — too small
• /23: 510 usable — sufficient
• /22: 1,022 usable — more waste
• /21: 2,046 usable — even more waste

• Red team: Simulates attackers and tests exploitability.
• Blue team: Defends, monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team activities to improve cooperation and defenses.
• White team: Manages and oversees the rules, scope, and authorization of the exercise.

• Bronze: Raw ingested data
• Silver: Cleaned, validated, and transformed data
• Gold: Business-level data for analytics, dashboards, and reporting

Box 1: No

• configure_azure_monitor() configures Azure Monitor and the OpenTelemetry pipeline.
• LangChain requires its own instrumentation or callback tracer, such as AzureAIOpenTelemetryTracer.
• You must pass the tracer to the LangChain execution configuration so chains, tools, prompts, and model calls become spans in Application Insights.

Box 2: Yes

text 
OTEL_SERVICE_NAME=customer-agent 
OTEL_SERVICE_NAME=invoice-agent

1. The original app version exists.
2. You create and publish a new version, so there are now two versions.
3. When you restore the previous version, Power Apps does not delete or overwrite the newer version. Instead, it creates another version based on the restored one.

• Original version
• Newly created and published version
• New version created by the restore operation

• Root path cost
• Port priority
• Port ID

text 
interface GigabitEthernet0/1 
 spanning-tree vlan 10 port-priority 64

• Interface number: Helps form the port ID but is not normally configured as the preference value.
• VLAN priority: Not used to select a preferred forwarding interface.
• Hello time: Controls how often BPDUs are sent; it does not select a preferred port.

• Admin access to the deployment pipeline
• Contributor access to the Development and Test workspaces
• Viewer access to the Production workspace

• Amazon EC2 instances — ???????? ?? ?? ??????? CPU, memory ??? instance size ???????? ???????
• AWS Lambda functions — memory configuration ?????????? ???????
• Amazon EBS volumes — volume type ?? size optimize ???? ???????
• ??????? ECS workloads — resource configuration ? cost optimization-?? ???????

• Memory ? compute usage ?????????? ???? custom code ????? ???? development ? maintenance ??????
• Cost allocation tags ???? ????? ??? ?????? ???? ??????? ???; inefficient resource ??????? ?? recommendation ???? ???
• CloudTrail resource ???? ?? API activity ??????, resource utilization ????

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

1. It examines the source MAC address and learns it on the incoming port.
2. It examines the destination MAC address.
3. If the destination MAC is already in the MAC/CAM table, it forwards the frame only through the associated port.
4. If the destination MAC is unknown, it performs unknown-unicast flooding:

• Response and resolution times
• Availability or uptime
• Performance targets
• Support obligations
• Penalties for failing to meet commitments

• SOW (Statement of Work): Describes the work, deliverables, scope, and tasks.
• MOA (Memorandum of Agreement): Documents a formal agreement about roles or responsibilities.
• MOU (Memorandum of Understanding): Records a general mutual understanding, often without detailed service metrics.

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

• Deterrent control: The signs warn people they may be filmed. This can discourage unauthorized activity because individuals know surveillance is present.
• Detective control: CCTV monitors and records activity, helping identify or investigate incidents after—or while—they occur.

• Preventive: Stops an incident from occurring; CCTV generally does not physically prevent access.
• Corrective: Restores systems after an incident.
• Directive: Tells people what they must do, such as a security policy.
• Compensating: An alternative control used when the preferred control cannot be implemented.

• Fine-tuning requires a properly formatted training dataset.
• For classification or instruction-style fine-tuning, examples are supplied in JSONL format.
• Each line represents one training example, typically containing the input prompt and the desired completion or label.
• The file must then be uploaded or made available to the Microsoft Foundry fine-tuning workflow.

• A: Prompt Flow is useful for prompt experimentation, but it is not required to start fine-tuning.
• B: You do not need to deploy the base model to an online endpoint before fine-tuning.
• C: Tracing supports observability and evaluation, but it does not prepare the fine-tuning job or dataset.

• UPS battery-backed outlets: Connect only essential devices needed during an outage:

• Surge-protector-only outlets: Connect nonessential devices, especially the printer. Printing does not need to continue while you are saving work and shutting down.
• UPS power source: Plug the UPS directly into a wall outlet.
• Surge protector power source: Plug it directly into a wall outlet as well. Do not normally plug a surge protector into the UPS, because that creates a daisy chain and can overload the UPS.

• No servers or database infrastructure to provision.
• Uses standard SQL.
• Supports formats such as JSON, CSV, Parquet, and ORC.
• You typically define the table structure with AWS Glue Data Catalog or Athena’s own schema definitions.
• Charges are generally based on the amount of data scanned, so partitioning and columnar formats can reduce cost.
• It does not copy the data into a separate database; it reads the files in S3 when you run a query.

• Accept: Acknowledge the risk and take no additional action.
• Mitigate: Reduce the likelihood or impact of the risk through controls.
• Avoid: Eliminate the activity or situation causing the risk.
• Transfer: Shift responsibility or financial impact to another party, such as through insurance or a contract.

• Amazon SageMaker — charges apply for compute, storage, and other resources used.
• AWS Config — generally charges for configuration recording and rule evaluations.
• Amazon CloudWatch — has a limited free tier, but many metrics, logs, alarms, and API usage can incur charges.

• Proxy server: Acts as an intermediary for requests, but does not necessarily provide an encrypted connection to the corporate network.
• NGFW: A firewall with advanced inspection and filtering capabilities; it may support VPNs but is not the remote-access solution itself.
• Security zone: A logical network grouping based on trust or security requirements, not a method for remote access.

• Atomicity: a write fully succeeds or does not appear.
• Consistency: table state remains valid.
• Isolation: concurrent operations do not corrupt one another.
• Durability: committed changes persist.

• Flexible schemas: common data lakes often support flexible or schema-on-read data.
• Open-source formats: common data lakes commonly use open formats such as Parquet.
• Scalable storage: cloud data lakes already provide scalable storage.

• JobTitle: User1 and User3 only
• UsageLocation: User1, User2, and User3

• For a user whose source of authority is Windows Server Active Directory, attributes such as JobTitle are synchronized to Microsoft Entra ID. You must change them in on-premises AD; editing them in Entra ID is not allowed or will be overwritten.
• UsageLocation is a cloud-managed attribute used mainly for licensing and service availability. It can be set or changed in Microsoft Entra ID, including for synchronized users.

• Extracted text and images
• Page numbers and bounding polygons for citation or grounding
• Structured tables, including tables that continue across multiple pages
• Document structure such as sections and figures

• Document Extraction: Extracts basic text and images, but does not provide the full layout and structural metadata required here.
• Azure Content Understanding in Foundry Tools: A broader content-analysis service, not the single built-in Azure AI Search skill expected by this question.
• GenAI Prompt: Can transform or interpret content but does not inherently produce reliable document geometry and page-level polygons.

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

• Suspended an operator who correctly refused to use unsafe equipment.
• Rewarded another operator for using the equipment despite the broken safety guard.

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

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

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

• The team should inspect its way of working during retrospectives.
• The team can identify root causes of delays and agree on process improvements.
• The leader facilitates the removal of impediments and provides support, but does not impose solutions.

• A: An impediment log can help track issues, but documentation alone does not resolve them.
• B: Directing the team toward solutions conflicts with agile empowerment and self-management.
• C: Adding impediments to the product backlog may incorrectly treat team problems as product features and delay resolution.

• AB’s own PPE: $100m
• CD’s PPE in its individual accounts: $50m
• Fair value uplift at acquisition: $40m
• Remaining useful life: 10 years
• Extra depreciation each year: $40m ÷ 10 = $4m
• Four years’ extra depreciation to 31 December 20X4: 4 × $4m = $16m
• Remaining fair value uplift: $40m - $16m = $24m

• Disabling a compromised account
• Blocking a malicious IP address
• Isolating an endpoint
• Creating or escalating an incident ticket

• Virus signatures: Primarily associated with antivirus or endpoint protection.
• Security agent deployment: Usually handled by endpoint-management or security-agent platforms.
• Vulnerability scanning: Typically performed by vulnerability-management tools.

Recommended process

1. Access each switch’s terminal.
2. Use help to identify available commands.
3. Use the MAC table command, such as:

text 
   show mac-address-table

1. Use VLAN information, such as:

text 
   show vlan

1. Use interface information, such as:

text 
   show ip interface brief

1. Record each device’s:

• C — Some risks cannot be eliminated.

• D — Accepting residual risk does not imply recklessness.

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

• Verifies the sender’s identity using their private key.
• Confirms the transaction was not altered after signing.
• Provides evidence that the signer approved or originated the transaction.

• Digital certificates: Bind an identity to a public key, but do not themselves prove that a specific transaction was signed.
• Encrypted passwords: Protect confidentiality or authentication, but generally do not provide transaction-level nonrepudiation.
• One-time passwords: Authenticate a user for a session or transaction, but usually do not provide durable proof of who authorized the electronic record.

• Defender for Servers is the Defender for Cloud plan that protects Azure VMs and generates security alerts that can be reviewed in Defender for Cloud.
• Azure Diagnostics extension collects guest OS monitoring data, but it does not onboard VMs to Defender for Cloud or provide Defender security alerts.
• Data connectors are used for Sentinel integrations.
• Azure Storage Analytics and workflow automation do not provide VM protection.

• Unsafe images: Requires image/content moderation before the image is processed.
• Hidden instructions embedded in images: These are indirect prompt injections contained in untrusted image content or extracted text, not necessarily in the user’s typed prompt.

• NTLM: Uses Windows challenge-response authentication and does not provide the normal web-based MFA redirect flow.
• Single Sign-On: Automatically reuses existing credentials; it is intended to avoid prompting, not to support an MFA workflow.
• Transparent: Intercepts the session without redirecting the user to a separate authentication page.

1. System prompts can authorize users — No

1. System prompts can reduce TPM consumption — Yes, with qualification

1. System prompts guide generative AI behavior — Yes

• Rights issue: Raises new equity from existing shareholders. It does not increase debt or gearing, so it is least likely to breach the covenant.
• Retained earnings: Also equity finance, but the amount available may be insufficient for the required $800 million.
• Private placement of a bond: Creates additional debt and would worsen gearing, increasing the risk of breaching the covenant.
• Bank overdraft: Also debt finance, usually short-term and potentially expensive; it would still increase financial risk and gearing.

• Build, measure, learn: Create something, assess real feedback or results, and adapt.
• Minimum viable product (MVP): Produce the smallest useful version to test assumptions and reduce uncertainty.
• Fail fast: Test ideas early so that unsuccessful approaches can be identified before significant time or cost is invested.

• Orders contains order-level information, such as the order date.
• Order Line Items contains the products, quantities, and line amounts associated with each order.
• Merging them on the order key, such as OrderID, places the order date alongside each line item. This allows you to calculate total order value and analyze it over time.
• Product attributes can remain in the Products table and be related to the resulting line-item table through ProductID.

• Merging line items with products addresses product attributes but does not first provide the order-level date and value needed for time analysis.
• DAX calculated columns or lists add unnecessary model complexity.
• Calculating order counts is not the first requirement and does not combine the required order and line-item data.

• Set credit quotas for an account or individual virtual warehouses.
• Define monitoring intervals.
• Trigger actions when usage reaches thresholds, such as sending notifications or suspending a warehouse.
• Help control unexpected warehouse spending.

• Account Usage: Provides historical usage and billing data; it does not enforce credit limits.
• Warehouse Limit Parameter: Not the Snowflake object used for account-wide credit controls.
• Credit Consumption Tracker: Not a standard Snowflake object.

• Unrestricted data mining: Data mining is not automatically a privacy violation. It becomes an issue when personal data is collected or used improperly.
• Identity theft: This is a possible consequence of inadequate privacy protection, but it is not the central focus of privacy regulations.
• Human rights protection: Privacy can be considered a human right, but this option is broader than the specific regulatory focus.
• Identifiable personal data: Regulations such as HIPAA focus directly on controlling the collection, use, disclosure, and protection of personal information.

• Vulnerability scanner: Identifies technical weaknesses in systems, applications, or devices.
• Penetration test: Simulates attacks to determine whether vulnerabilities can be exploited.
• SCAP (Security Content Automation Protocol): Uses standardized formats and protocols for automated vulnerability, configuration, and compliance checks.
• Illumination tool: Maps and analyzes broader supply-chain exposure and third-party risk.