Nutanix NCP-US-6.5 Exam Prep
Nutanix Certified Professional - Unified Storage (Page 2 )

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

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

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

• Due diligence: Researching and evaluating a third party before entering or continuing a business relationship.
• Internal audit: Evaluates controls within the organization itself.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A formal statement or report—such as a SOC 2 report—provided by an independent party about an organization’s controls.

• Record changes — a flow can start when a record is updated or otherwise changes.
• Schedules — a flow can run at a specified date/time or on a schedule.
• Record inserts — a flow can start when a new record is created.

• Subflows are reusable flow components called by another flow; they are not normally trigger types.
• Record views do not generally initiate a Flow Designer flow.

• A script of cloud CLI commands: IaC because the commands can be saved, reviewed, versioned, and rerun consistently.
• Manually run curl commands: Not necessarily IaC; they are manual actions unless organized into an automated script.
• A sequence of REST requests passed to an API: Could represent automation, but the wording does not explicitly say they are stored and executed as reusable code.
• Commands entered into a cloud console: Manual operation, not IaC.

CIMA P3 topics

• IT governance and systems strategy
• Systems development and implementation
• Change and project governance
• Strategic and business risk

• A — Plan for new systems: The committee should help identify and prioritise systems requirements and ensure planned systems support organisational needs.
• D — Consider competitive issues: New information systems may affect Y’s competitive position, service quality and efficiency. These strategic implications should be considered.
• E — Ensure the system meets company goals: This is a key governance responsibility. The committee should ensure the project remains aligned with Y’s objectives and delivers business value.

• B — Develop new systems: Detailed system development should be performed by IT specialists and project teams, not the steering committee.
• C — Manage the project: The project manager should handle day-to-day project management. The steering committee should provide oversight, challenge and key decisions, rather than manage daily activities.

• A. IDS attack signatures: An IDS mainly detects suspicious network traffic. It is not the best control for scanning uploaded documents.
• C. Load balancer: Distributes traffic among servers and can improve availability, but does not specifically detect malware.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection. It may inspect web requests, but malware scanning of PDF files is not its primary function.

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

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

• Guest access: Controls external users invited into your teams as guests. It is not the primary setting for restricting federated communication by domain.
• Messaging policy: Controls messaging features, such as chat or message editing, rather than which organizations users can communicate with.
• Org-wide Teams settings: Contains broad Teams-wide configuration, but domain-based external communication is configured under External access.

• terraform apply
• terraform destroy

• Authentication: Verifies who the user is.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records login activity and resource usage.

• CIA: Confidentiality, integrity, and availability—the core security objectives.
• ACL: Access Control List; rules that permit or deny traffic or access.
• PEM: A format and standard commonly associated with encoded certificates and keys.

• Static IP address: Not needed if the workstation already has network connectivity.
• Subnet mask: Incorrect subnetting would usually prevent local communication, including pinging the server.
• Default gateway: Primarily affects communication outside the local network; it does not normally prevent finding an internal domain controller.

• Base table — the table containing common inherited fields
• Parent table — the table directly extended by the child
• Other tables in the hierarchy

1. Yes — Microsoft Foundry provides a secure, governed environment for building and managing generative AI applications and agents. It brings together models, data, tools, evaluation, deployment, and monitoring.

1. Yes — Foundry is designed for enterprise workloads and supports scaling AI applications as usage grows. Scalability comes from the underlying Azure services and managed infrastructure.

1. Yes — Foundry can be used in solutions involving image recognition and computer vision. Applications can use vision-capable models and Azure AI vision capabilities for tasks such as image analysis, object detection, and OCR.

• SOSL searches text across objects and is not appropriate for selecting Account table columns.
• describeSObjects() provides metadata about objects and fields, but it does not itself build or execute the query.
• Dynamic Schema binding supports runtime determination of object and field information, which is required here.
• REST API is unnecessary because this is being implemented in Apex.

• A — Capacity: The system must handle all current records and anticipated future records. A system that cannot cope with volume will quickly become ineffective.
• C — Accuracy: Academic records are critical, so the new system must be at least as accurate as the existing system and comparable systems. Poor accuracy could cause serious administrative and reputational problems.
• D — Integration: Linking with the university’s financial systems supports consistency and avoids duplicate data entry, especially for registration, deregistration and fee-related transactions.

• B — Parallel running: This is a useful implementation and risk-control technique, but it is not an essential feature of the system itself. It may also be expensive and time-consuming.
• E — Internet access for all information: This creates significant confidentiality and security risks. External access might be needed for selected services, but unrestricted access to all information is not essential and would be inappropriate for student records.

• O File Gateway fornece uma interface de compartilhamento de arquivos usando protocolos como SMB ou NFS.
• Os usuários continuam acessando os arquivos localmente, aproveitando a baixa latência e o cache local.
• Os dados são armazenados de forma durável no Amazon S3, enquanto os arquivos acessados com frequência permanecem em cache no ambiente local.
• Isso amplia a capacidade de armazenamento sem exigir a substituição completa da infraestrutura existente.

• A: Montar buckets S3 diretamente não oferece uma experiência de compartilhamento de arquivos local tão adequada.
• C: Amazon WorkSpaces fornece desktops virtuais, não é uma solução principal de armazenamento compartilhado.
• D: Um volume EBS pertence a uma instância EC2 e não deve ser compartilhado diretamente entre vários usuários como um sistema de arquivos comum.

• D — Value analysis: Correct. It examines an existing product to identify ways of reducing its cost while still providing the required functions, quality and reliability.
• E — Kaizen costing: Correct. It involves making continuous, small improvements and cost reductions while the product is already in production.

• Functional analysis: It is not limited to minimizing the cost of the originally defined functions. It examines what functions are required and how they can be provided at the lowest overall cost.
• Value engineering: Usually applies to the design and development of a new product, rather than being a fundamental redesign of existing organisational processes. That description is closer to business process re-engineering.
• Target costing: The target cost is generally established during the product development stage, before production begins. It is not continuously reset while the product is in production.

• COE: Identifies the Center of Excellence, such as Payroll or Benefits.
• Topic Detail: Classifies the HR service within its COE; it does not identify the catalog item.
• Template: Supplies default values or case configuration.
• Record Producer: Represents the catalog item that employees use to submit the request and create the case.

• New investment: $536,500
• Resulting NPV: $0

• Security
• Availability
• Processing integrity
• Confidentiality
• Privacy

• Whether controls are suitably designed, and
• Whether they operated effectively over a period of time

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

• A. IDS attack signatures: An IDS primarily detects suspicious network activity; it is not the best control for scanning uploaded documents for malware.
• C. Load balancer: Distributes traffic among servers and improves availability, but does not inspect files for malware.
• D. WAF: Protects web applications against attacks such as SQL injection and command injection. It may help secure the upload function, but malware scanning is the key requirement here.

• Shared capacity

• Fabric capacity — F SKUs

• Fabric trial capacity

• Existing Power BI Premium — P SKUs

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

• state preserves the client’s original context, such as the specific idea URL the user requested.
• The portal sends that value in the OAuth authorization request.
• Salesforce returns it after authorization, allowing the portal to redirect the user to the original idea rather than the Ideas home page.

• How quickly the vendor must respond to incidents or requests
• Availability or uptime requirements
• Resolution time targets
• Performance expectations and penalties for failing to meet them

• SOW (Statement of Work): Describes the work, deliverables, scope, and schedule.
• MOA (Memorandum of Agreement): Documents an agreement in which parties commit to specific responsibilities.
• MOU (Memorandum of Understanding): Records a general intention to cooperate; it may not be legally binding.

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

• B — AWS DataSync: Transfers data between storage systems. It is not a marketplace or integration service for third-party datasets.
• C — Kinesis Data Streams and CodeCommit: CodeCommit stores source code, not third-party analytical datasets. Kinesis is for streaming data, not retrieving datasets from repositories.
• D — Kinesis Data Streams and ECR: Amazon ECR stores container images, not third-party datasets.

• B — Notify affected business units: Notification should follow an initial determination of scope and impact; otherwise, the organization may communicate incomplete or inaccurate requirements.
• C — Assess noncompliance risk: Risk assessment requires understanding the regulation’s requirements first.
• D — Inform senior management: Management should be informed, but with a clear summary of the regulation’s impact, risks, and recommended actions.

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

• Each team’s Bedrock workflow uses a separate IAM service role.
• The role’s Amazon S3 permissions can be limited to only that team’s customer folder or objects.
• This enforces least privilege and prevents one team’s Bedrock application from accessing another team’s data.
• Access is enforced by AWS permissions, not by asking users to provide a customer name in each request.

• A single role with broad S3 access does not provide team-level isolation.
• Asking teams to specify a customer name is not an access-control mechanism.
• Redacting data does not prevent unauthorized access.
• A bucket policy alone is insufficient unless it explicitly enforces the required team-role restrictions.

• The server accepts unauthenticated image uploads, which creates an opportunity for an attacker to upload a malicious script disguised as an image or using an unexpected file type.
• A web shell is a malicious script placed on a web server that gives an attacker remote command execution through web requests.
• The suspicious process and outbound connection to a low-reputation IP are consistent with the attacker using the web shell to execute commands or establish communication with command-and-control infrastructure.

• Worm: Usually self-propagates across multiple systems; the scenario focuses on the upload page.
• Cryptocurrency mining: Possible, but there is no indication of resource-intensive mining activity or insider involvement.
• Rootkit Trojan over RDP: The evidence points to the vulnerable upload functionality, not an exposed RDP service.

• Where to find the TiMOS runtime image
• Which configuration file to load
• The IP address and related settings for the CPM management Ethernet port

• A: User authorization is configured in the router’s security configuration, not primarily in the BOF.
• C: Hardware initialization is performed by the boot process and system software.
• D: The system date and time are configured separately, often through NTP or CLI settings.

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

• The message came from the claimed sender (authentication)
• The message was not altered (integrity)
• The sender cannot easily deny sending it (non-repudiation)

• Attackers can send unsigned phishing emails.
• Attackers may compromise a legitimate account and send signed malicious emails.
• Users may still be tricked by a validly signed message.

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

• A — .gitignore: Controls Git tracking; it does not configure Copilot exclusions.
• B — copilot.ignore: This is not the standard GitHub Copilot Business exclusion mechanism.
• D — Renaming files: Adding _no_copilot has no recognized effect.

• Packet loss
• Latency
• Jitter
• Call quality by user, device, network, location, or building

• Teams Usage Report: Shows adoption and usage statistics, not detailed call-quality metrics.
• Teams Device Usage Report: Reports which devices are being used and how, but does not provide detailed packet-loss analysis.
• Microsoft Network Testing Companion: Helps assess network readiness before deployment, but it is not the primary tool for analyzing packet loss from actual Teams calls.

• Matching hashes: The software likely has not changed.
• Different hashes: The software was modified or corrupted.

• Encryption: Protects confidentiality by making data unreadable; it does not primarily detect changes.
• Baselines: Define an approved system or configuration state, but they are not the specific integrity mechanism here.
• Tokenization: Replaces sensitive data with substitute values.