Salesforce CRT-101 Exam Prep
Certification Preparation for Administrator (Page 49 )

• Service Cloud focuses on customer service and support.
• Knowledge: Used for a knowledge base of articles to assist agents and customers.
• Entitlements: Define service levels/SLA for handling cases.

• Campaigns and Opportunities/Quotes are typically part of Sales Cloud (marketing and sales functionalities, respectively).

• DB1 (500 TB): Azure Data Box Heavy

• Virtual machines: Azure Migrate

• Espionage: Stealing confidential information, often for a competitor or foreign entity.
• Data exfiltration: Unauthorized removal or transfer of data.
• Nation-state attack: A cyberattack sponsored or conducted by a government.
• Shadow IT: Unapproved technology or services used outside IT oversight.

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

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

• Early units show relatively large time savings.
• Later units still take less time, but the reduction becomes progressively smaller.
• The curve therefore becomes flatter as production approaches 256 units.

• B: The reduction is not constant; learning normally diminishes over time.
• C: Time does not reduce at an increasing rate.
• D: A steady state may eventually be reached, but the question concerns the first 255 units while learning is still occurring.

• Disable high concurrency: This changes session-sharing behavior but does not provide dedicated compute or true workload separation.
• Modify the number of executors: Adjusts resources within a Spark job; it does not isolate bronze and silver processes.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

1. Install a Cassandra-compatible ODBC driver.
2. Configure a data source name (DSN), if required.
3. In Power BI Desktop, select Get Data > ODBC.
4. Choose the configured DSN and connect.

• Microsoft SQL Server database: Connects to SQL Server, not Cassandra.
• OLE DB: Requires a compatible OLE DB provider; this is not the standard choice for Cassandra in Power BI.
• OData: Requires Cassandra data to be exposed through an OData service, which is not the normal direct connection method.

• Business risks
• Potential financial, operational, legal, or reputational impact
• How governance reduces risk to organizational objectives
• How much risk the organization is willing to accept

• Packet capture: Collects and analyzes network traffic; it does not describe the scan type.
• Privilege escalation: Attempts to gain higher permissions after obtaining access.
• System enumeration: Identifies systems, services, or resources, but is not specifically defined by the lack of credentials.
• Passive scan: Observes traffic without actively probing systems. A vulnerability scan is generally an active assessment.

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

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

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

• A business-hours greeting
• An after-hours greeting
• A holiday greeting

• Weekday evenings/nights
• Saturdays and Sundays

1. Auto attendant 1

1. Auto attendant 2

• NAT traversal: Helps WAN Edge, vSmart, and vManage devices discover how to reach one another through NAT.
• Initial orchestration: Authenticates and introduces devices when they first join the SD-WAN fabric.
• Connection brokering: Provides information that allows devices to form their required control connections, after which the vBond is generally not in the data path.

• WAN Edge: Forwards user traffic and forms secure tunnels.
• vSmart: Controls the overlay control plane and distributes routes and policies.
• vManage: Provides centralized management, configuration, and monitoring.

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

• Behavioral and anomaly detection
• Threat intelligence integration
• User and entity behavior analytics
• Automated response actions, often through SOAR integration

• Virus signatures: Associated primarily with antivirus or endpoint protection.
• Security agent deployment: Usually an endpoint-management or EDR function.
• Vulnerability scanning: Typically performed by vulnerability-management tools, though a SIEM may integrate their results.

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

• Self-signed certificate — Causes a certificate trust warning, not incorrect name resolution.
• Nameserver record — A DNS record problem would usually affect multiple users, unless only this computer uses a different DNS server.
• IP helper — Relays certain network services, commonly DHCP, between subnets; it does not normally determine website name resolution.

• Existing expected ROI: 15%
• New project ROI: 14%
• Cost of capital: 12%

• Project return = 14%
• Cost of capital = 12%
• It earns 2% more than the cost of capital, so it should increase shareholder value.

• BCP (Business Continuity Plan): è più ampio e mira a mantenere le funzioni essenziali dell’organizzazione durante un’interruzione. Il DRP è una componente più specifica del BCP.
• Communication plan: stabilisce come comunicare con dipendenti, cittadini e altre parti interessate, ma non ripristina i sistemi.
• IRP (Incident Response Plan): gestisce la risposta iniziale a un incidente di sicurezza, come un attacco informatico, non principalmente il recupero da un disastro fisico.

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.

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

• Complete MFA, or
• Securely change their password

• Identity Protection: evaluates user and sign-in risk and can trigger remediation.
• Privileged Identity Management (PIM): manages temporary, just-in-time access to privileged roles; it does not automatically require password changes for risky sign-ins.

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

• Existing measures
• Relationships
• Calculated columns
• Tables and fields
• Existing transformations in the model

• SharePoint folder: Reconnects to the source files. You would likely need to recreate the model and measures.
• Power BI dataflows: Primarily provide reusable data preparation and storage, but they do not automatically provide the existing semantic model and measures.
• Excel workbook: Connects directly to the source file and would also require rebuilding the model and measures.

1. CALCULATE
2. AND
3. FILTER

DAX 
Transaction Category = 
CALCULATE( 
    MAX('Transaction Size'[Size]), 
    FILTER( 
        'Transaction Size', 
        AND( 
            Sales[Sales Amount] >= 'Transaction Size'[Minimum], 
            Sales[Sales Amount] <= 'Transaction Size'[Maximum] 
        ) 
    ) 
)

• FILTER examines the rows in the Transaction Size table.
• AND ensures the sales amount falls between the category’s minimum and maximum values.
• CALCULATE evaluates the result in the modified filter context and returns the matching category.