VMware 2V0-31.21 Exam Prep
Professional VMware vRealize Automation 8.3 (Page 4 )

• Technical platform interfaces: Important for integration and interoperability, but they should support—not drive—the architecture.
• Scalability of the network: Valuable as the organization grows, but a scalable solution is ineffective if it does not meet business or security needs.
• Development methodologies: Relevant to implementation, but they do not define the organization’s fundamental security requirements.

• The ERSPAN source is the device or interface whose traffic is being copied.
• The ERSPAN destination is the device receiving the encapsulated copy and forwarding it to the traffic analyzer.
• The local monitor session number is locally significant. Therefore, the source and destination do not need matching session IDs such as 47 or 48.
• The erspan-id identifies the ERSPAN stream and must correspond between the source and destination configuration.

• Employees can work from any location, including remote sites and offices worldwide.
• Login can be relatively seamless after the device is registered.
• It does not require distributing additional physical authentication equipment.

• Geotagging: Identifies location, but location alone is not a strong authentication method and may prevent legitimate remote access.
• Smart cards: Provide strong authentication but require card readers and physical cards, increasing equipment and management requirements.
• Time-based logins: Typically involve one-time codes that users must enter, making the experience less seamless and potentially requiring a token or authenticator app.

• Required response time
• Resolution time
• Availability or uptime
• Support hours
• Performance targets
• Consequences if targets are missed

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes the responsibilities and commitments between parties.
• MOU (Memorandum of Understanding): Documents a general mutual understanding or intent, often before a formal agreement.

• Which batches and markets are affected
• Whether the deficiency affects product quality, efficacy, or patient safety
• Whether the issue is an ongoing manufacturing problem
• Whether immediate containment or distribution suspension is needed

• A — Withdraw the product: may be necessary, but is premature before assessing the risk.
• B — “Dear Dr.” letter: may be appropriate later, depending on the risk.
• C — Notify global authorities: may become mandatory, but the scope and urgency depend on the assessment.

• CPU: Number of virtual CPUs and, where applicable, CPU reservations.
• Memory: Amount of memory and memory reservations.

• Network interface: Usually configured through the VM or workload networking configuration.
• PCI devices: Specialized hardware and not a standard VM Class resource in this context.
• Storage: Typically selected through storage policies or the VM’s storage configuration.

• Microservices: An application design approach that divides software into small services; it does not specifically reduce the number of operating systems.
• Containerization: Uses isolated containers that share the host OS kernel—best match.
• Virtualization: Creates separate virtual machines, and each typically requires its own guest OS, so it does not minimize OS instances as effectively.
• Infrastructure as code: Automates deployment and management of infrastructure; it does not describe the architecture being used.

• Document feeder: A scratch, dirt, or debris on the feeder glass or rollers can create a line on every scanned image.
• Pickup rollers: Move paper through the printer; they would not normally create a scanner-only line.
• Corona wire: Affects toner charging and would cause defects on printed output.
• Drum assembly: Also affects printed pages, so faxes and computer print jobs would show the line too.

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

• Run the backup with WITH CHECKSUM
• Store the backup on an SMB network share

sql 
BACKUP DATABASE DB1 
TO DISK = '\\FileServer\SqlBackups\DB1_full.bak' 
WITH CHECKSUM;

• DMS does not create the SQL Server backups for you.
• You must provide a valid full database backup.
• You must continue taking transaction log backups while the source database remains online.
• The full backup and subsequent log backups must be available in the SMB share that DMS can access.
• WITH CHECKSUM enables backup checksum validation, helping detect backup corruption.

• What information each stakeholder needs
• When and how often it should be communicated
• Which format or channel should be used
• Who is responsible for communicating it

• A: The team should not decide stakeholder communications without first checking the established plan and CEO’s needs.
• B: An executive summary may be appropriate, but choosing a solution before reviewing the plan is premature.
• D: The stakeholder engagement plan addresses how to engage stakeholders, but this is primarily a communication planning issue.

• The connected switch
• The switch’s port/interface
• Device and port descriptions
• Sometimes VLAN or management information

• IKE: Establishes security associations for IPsec VPNs.
• VLAN: Defines logical network segmentation; it does not identify a physical switch port.
• netstat: Displays local network connections and statistics, not the upstream switch and port.

• Product recall: Premature before confirming a violation or assessing risk.
• Notify the regulatory authority: May be required later, especially if the discrepancy affects safety or compliance, but first investigate and verify the facts.
• Inform production: Not the initial regulatory assessment step; production may become involved if a packaging or manufacturing error is identified.

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

• ?? ?? ?? ??
• ?? NFS ?? SMB ?? ??
• ?? ???? ???
• ?? IP ??? ???? ?? ???
• ??? ?? ???? ?????

• B: ????? NFS ? Snowball Edge? ?? ?? ? AWS? ?? ? S3
• D: ????? NFS ? ????/Direct Connect ? File Gateway ? S3

• A PostToolUse hook for file writes under src/api/ that runs the linter.
• A separate PostToolUse hook for API/data processing that normalizes payloads to snake_case.

• Tokens: Individual units of text processed by a model, such as words, subwords, or characters.
• Models: Systems that learn patterns and generate predictions or outputs.
• Binaries: Data represented using the binary number system, not semantic representations.

• Note the question number before leaving—for example, Question 38.
• Use the exam’s question navigator or Back/Previous button to return to that number.
• If you close or refresh the page, your position may not be saved, depending on the site. Reopen the page and select the question number again.
• Avoid using the browser’s Back button if it causes the exam page to reload; use the exam’s built-in navigation instead.

• Wireshark captures packets and allows you to examine their contents, potentially revealing usernames and passwords sent without encryption.
• Netcat creates network connections and can send or receive data, but it is not primarily a packet-analysis tool.
• Nessus scans for known vulnerabilities and configuration issues; it generally would not prove that credentials are visible in transit.
• Nmap performs network discovery and port/service scanning, not detailed packet-content inspection.

• Matching hashes: The software is likely unchanged.
• Different hashes: The software or its contents have been modified.

• Encryption: Protects confidentiality, not primarily integrity.
• Baselines: Document expected configurations and support comparison, but hashing is more directly suited to verifying file integrity.
• Tokenization: Replaces sensitive data with tokens and is unrelated to software tampering.

• A is valid:

apex 
  for (Account theAccount : AccountList) { 
      // process theAccount 
  }

• D is conceptually valid, using an index:

apex 
  for (Integer i = 0; i < AccountList.size(); i++) { 
      Account theAccount = AccountList[i]; 
  }

• B is invalid because for(AccountList) is not valid loop syntax.
• C is invalid because each item is an Account, not a List.

• B. Conditional access policies

• D. Additional authentication factors

• Disciplinary actions: Punish users but do not prevent credential-based attacks.
• More regular account audits: Useful for finding inactive or excessive accounts, but less direct for stopping unauthorized logins.
• Content filtering: Primarily controls web or email content, not authentication.
• Review of permissions: Reduces privilege but may not stop unauthorized account access.

1. The specific table — for example, incident
2. The parent table — for example, task
3. The wildcard table — *, which applies broadly

• Accept: Acknowledging the risk and choosing not to take additional action.
• Transfer: Shifting the risk or financial consequences to another party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or access restrictions.
• Avoid: Eliminating the activity that creates the risk.

• Box 1: No — The rule requires user.department to equal Engineering. Engineer does not match, so User1 is not in AU1. Admin1 cannot reset User1’s password.
• Box 2: No — Admin1’s role is scoped to AU1 and cannot manage users outside that AU.
• Box 3: Yes — Admin2 is a Global Administrator and can reset User3’s password.

• Operating profit is affected because transfer price determines internal sales revenue.
• Return on investment (ROI) is affected because ROI depends partly on operating profit.
• Sales revenue is affected because the division records revenue from transferring its output.
• Cost of components purchased is not affected by the transfer price. These are input costs paid to external suppliers and are based on the supplier’s price.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or financial impact to another party, such as through insurance or a contract.
• Mitigate: Reduce the likelihood or impact using controls, such as firewalls, training, or backups.
• Avoid: Eliminate the activity that creates the risk.

• Reduce the training data: Usually makes overfitting worse.
• Add hyperparameters: Hyperparameters already control training; simply adding them does not solve the problem. Proper tuning could help, but that is not what the option states.
• Increase training time: More training can worsen overfitting if the model is already memorizing the training data.

• File policy in Microsoft Defender for Cloud Apps: Can detect activity involving files, but it is not designed specifically to investigate risk from departing or deleted users.
• Access review policy in Microsoft Entra: Reviews whether users should retain access to resources; it does not detect historical document downloads.
• Alert policy in Microsoft Defender for Office 365: Primarily handles alerts for email and collaboration threats, not insider-risk investigations involving departed users.

• A — Technical review by business owner: A business owner may approve the business impact, but a technical review is normally performed by technical personnel.
• C — Cost-benefit analysis after implementation: Cost-benefit analysis should occur before implementation to support the approval decision.
• D — Business continuity testing: This can be appropriate for major changes, but it is primarily part of business continuity and disaster recovery planning—not a universal change-management activity.

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

• Escape to host: A virtualization attack where code escapes a guest VM and accesses the host system. Nothing in the scenario mentions virtualization.
• Browser extension: Can redirect or manipulate web-browser traffic, but not normally database-server traffic.
• Valid accounts: Describes using stolen or compromised credentials, not redirecting network traffic.
• Process injection: Injecting malicious code into a legitimate database or networking process could allow an attacker to alter how that process handles outgoing traffic.

• Plenum: Describes a fire-resistant cable jacket rating, not a transmission medium or speed.
• Ethernet: Describes a networking technology; Ethernet can use copper or fiber, so the term alone does not identify the fastest cable type.
• DAC (Direct Attach Copper): Uses copper and is typically intended for short-distance, high-speed connections in data centers.

• Two-part tariff pricing: $10 per unit
• Dual pricing: $20 per unit

Two-part tariff pricing

Dual pricing

• Division X, the seller, is credited with the market price: \(\$20\)
• Division Y, the buyer, is charged the marginal cost: \(\$10\)

• Response and resolution time frames
• Availability or uptime requirements
• Performance targets
• Support obligations
• Penalties for failing to meet requirements

• SOW (Statement of Work): Defines the project’s scope, tasks, and deliverables.
• MOA (Memorandum of Agreement): Describes cooperation and responsibilities between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, usually without detailed enforceable service targets.

• Measurement bias: Errors in how features or labels are measured, such as unreliable camera data or inconsistent labeling.
• Observer bias: A human evaluator’s subjective judgment influencing observations or labels.
• Confirmation bias: Favoring information that supports an existing belief.

• A single summarized value, such as total annual sales
• Progress toward a defined target or goal
• Whether performance is below, near, or above the target

• Table: Displays detailed records or summarized rows, but not goal progress visually.
• Stacked Bar: Compares multiple categories and their parts.
• Donut: Shows how a total is divided among categories, not progress toward a target.

• Deterrent control: The signs warning that people may be filmed can discourage unauthorized or malicious activity. They do not directly stop the action; they influence behavior.
• Detective control: CCTV records or monitors activity so security personnel can identify events or investigate them afterward.

• Preventive: Stops an incident from occurring, such as access control.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: An alternative control used when the preferred control is not feasible.

• Domínios personalizados.
• Armazenamento suficiente.
• Instâncias dedicadas.
• Balanceamento de carga.
• Menor custo entre os planos que atendem a tudo.

• /27 (255.255.255.224)

• /26 (255.255.255.192)

• /25: Creates only 2 subnets, not 3
• /28: Provides only 14 usable hosts per subnet

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

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:

• FTP — Transfers files using a client/server model and supports authentication. It uses separate control and data connections.
• TFTP — A very simple file-transfer protocol with no authentication and minimal features. Commonly used to transfer router or switch configuration files and IOS images.
• SCP — Securely copies files over SSH. It provides encryption and authentication.
• SFTP — Also transfers files securely through SSH, but provides more file-management capabilities than traditional SCP.
• HTTP/HTTPS — Primarily web protocols, but can also download files; HTTPS encrypts the session.

• TFTP = simple, unauthenticated file transfer
• FTP = file transfer with authentication, but not inherently encrypted
• SCP/SFTP = secure file transfer using SSH

• Disable high concurrency: Changes workspace-wide behavior and is not the targeted way to isolate these workloads.
• Modify the number of executors: Adjusts capacity and performance, but does not provide workload isolation.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• Distinct values = 69

• Unique values = 4

• An Adj-SID does not necessarily need manual configuration.
• It can often be dynamically allocated by the router, although manual configuration may also be possible.
• The adjacency information is advertised through the IGP, such as IS-IS or OSPF.

• It is identified by an Adj-SID.
• It represents a particular adjacency of a node.
• Its meaning is generally local to the advertising node; unlike a Node-SID, it is not a globally reusable instruction across the network.

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

• Design Studio > Emails ? create an email-template folder
• Design Studio > Landing Pages ? create a landing-page-template folder
• Add the relevant assets to each folder
• Right-click the folder and choose Share Folder
• Select the destination workspaces

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

• Due diligence: Investigating and evaluating a third party before entering into or continuing a business relationship.
• Attestation: An independent party provides assurance about an organization’s claims or controls. A SOC 2 examination is an example of an attestation engagement, but the analyst requesting and reviewing the report is performing due diligence.
• Internal audit: Reviews the organization’s own internal controls.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.