ATLASSIAN ACP-120 Exam Prep
Jira Administration for Cloud (Page 4 )

• To move all issues from version 1.1 to 1.2, use Merge (merge 1.1 into 1.2). This reassigns the issues to the target version.
• To remove 1.1 as an available option in Fix Versions, use Archive for version 1.1. Archived versions are no longer selectable for new issues.

• Low usage during the first three weeks
• Very high usage during the last week

• High availability: Keeps services running despite failures.
• High latency: Means slow response times; it is not a benefit.
• Load balancing: Distributes traffic across resources but does not specifically address scaling resources up and down.

Simple explanation

• The Azure VPN gateway to connect to
• Authentication settings
• Routes for networks that the client can access

yaml 
clusterIP: None

• CronJob: Runs Jobs on a schedule and normally does not need stable networking.
• Deployment: Manages interchangeable, stateless replicas and usually uses a regular Service.
• DaemonSet: Runs a Pod on selected nodes but does not inherently require stable Pod identities.

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

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

• Store privileged credentials securely
• Grant the consultant only the access needed
• Provide temporary or time-limited access
• Rotate passwords automatically
• Record or monitor administrator sessions

• TACACS+: Centralizes authentication and authorization, commonly for network devices, but does not primarily provide password vaulting and privileged-session control.
• SAML: Enables web-based federation and single sign-on, not privileged credential management.
• SSO platform: Reduces the number of passwords users need, but does not necessarily protect administrative credentials or control privileged sessions.
• Role-based access control (RBAC): Assigns permissions based on job roles, but does not by itself prevent password sharing or securely broker administrator access.

• Create Power Query parameters for the Azure SQL server/database—or at least the database name.
• Use the parameter in the PBIX connection.
• Publish the same PBIX separately to the relevant development, test, and production workspaces.
• Set each dataset’s parameter value in the Power BI service so it points to the corresponding Azure SQL database.

• Development dataset ? DevelopmentDB
• Test dataset ? TestDB
• Production dataset ? ProductionDB

• The same PBIX is used for every lifecycle stage.
• Each stage consumes data from its matching database.
• Deployment pipelines are not required.
• Azure SQL is a cloud source, so gateway administration is generally avoided.
• Only the parameter value differs between published datasets, reducing maintenance.

Flat organisation

• Few levels of management
• A wide span of control—managers supervise many employees
• Shorter communication channels
• More employee autonomy and quicker decisions
• Fewer formal promotion levels

Tall organisation

• Many levels of management
• A narrow span of control—managers supervise relatively few employees
• A clear hierarchy and reporting structure
• More formal supervision and communication channels
• More obvious promotion and career stages

• ADF: Automatic Document Feeder; a printer/scanner hardware component.
• USB: A short-range wired connection, not a protocol for accessing a remote shared folder.
• PCL: Printer Control Language; it describes how print jobs are formatted, not how files or printers are shared over a network.

• The target API uses HTTPS, so Mule must validate the server’s TLS certificate.
• The TLS configuration is set to None, meaning no custom truststore is configured.
• Mule therefore uses the JRE’s default truststore to determine whether the target certificate is trusted.
• If the issuing CA certificate is in that truststore, the TLS handshake can succeed.
• If it is absent—or the certificate is otherwise invalid—the request fails with a TLS/handshake error.

python 
def add_integers(a, b): 
    return a + b

• Uses def to define a function.
• Accepts two parameters, a and b.
• Uses return to send their sum back to the caller.
• Uses indentation to define the function body.

python 
result = add_integers(3, 4) 
result is 7

Question 3: AWS Storage Gateway File Gateway

• A: S3 bucket per user — S3 is object storage, not a traditional shared file system; mounting it requires extra tools and is less efficient.
• B: File Gateway — Provides a local file share using standard file protocols while storing files in Amazon S3. This preserves convenient local access and extends storage capacity.
• C: WorkSpaces and WorkDocs — Designed for virtual desktops and document collaboration, not large shared file storage.
• D: EC2 with EBS — EBS is attached to one EC2 instance and is not designed for direct multi-user file sharing.

• A. Number ? Decimal — Correct. Salesforce Number fields are represented in Apex as Decimal.
• D. Date/Time ? Datetime — This is correct conceptually, but “Dateline” is not an Apex type. If the option literally says “Dateline,” it is incorrect.
• E. Checkbox ? Boolean — Correct. A checkbox contains true or false.

• Number ? Integer — A Number field maps to Decimal, even when its scale is zero.
• Text Area ? List<String> — A text area maps to a single String, not a list.

• A single Construction Job can use multiple Machinery records.
• A single Machinery record may be used on multiple Construction Jobs.
• This is a many-to-many relationship, which Salesforce models using a junction object.
• The junction object can contain fields such as:

• Master-detail to Machinery
• Master-detail to Construction Job
• Date and cost fields

• Authentication: Verifies a user’s identity, such as username and password.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records connection and usage details, such as login time or session duration.

• CIA: Confidentiality, integrity, and availability are broad security objectives, not a specific RADIUS function.
• ACL: An access control list contains permit/deny rules on systems or network devices. RADIUS can support access decisions but is not itself an ACL.
• PEM: Privacy-Enhanced Mail is also associated with certificate and key encoding formats; it is unrelated to RADIUS’s primary purpose.

• B — AWS DataSync: Transfers data between storage systems, such as S3, file systems, and on-premises storage. It is not a marketplace or catalog for third-party datasets.
• C — Kinesis Data Streams and CodeCommit: CodeCommit is a source-code repository, not a third-party data provider. Kinesis is for streaming data ingestion.
• D — Kinesis Data Streams and ECR: ECR stores container images, not datasets. Kinesis does not provide access to ECR data as an external dataset source.

• The user authenticates with the external Identity Provider.
• Salesforce receives the SAML assertion.
• Salesforce uses attributes in that assertion—such as username, email, first name, last name, and profile/community information—to create the user during the first login.
• On later logins, Salesforce updates or uses the existing user record.

• On-the-fly provisioning is a general phrase; the Salesforce capability being tested is specifically JIT provisioning.
• Salesforce APIs would require a separate integration and provisioning process.
• Identity Connect is designed primarily to synchronize users from an identity directory, not to create users at the moment of their first SAML login.

• Coordinate and manage the assessment team
• Assign assessment activities
• Direct interviews, examinations, and tests
• Ensure the assessment follows the CAP

• Answer key: Lead Assessor — likely wrong
• CAP-based answer: C3PAO

• SAML: Enables federated authentication and single sign-on between the IdP and SaaS providers.
• OAuth tokens: Allow delegated application access; OAuth is not primarily the first step for employee SSO.
• Password vaulting: Stores or autofills multiple passwords but does not eliminate the separate credentials or provide true federation.

• 16 VMs: one failure loses 25 GB and 10 cores—only 6.25% of memory.
• 8 VMs: one failure loses 12.5% of memory.
• 4 VMs: one failure loses 25%.
• 1 VM: one failure loses the entire application environment.

• Equipment and hardware
• Facilities
• Inventory
• Backup media
• Supplies stored at an alternate or remote location

• Personal belongings of staff: Usually not organizational assets.
• DR line-item revenues: Revenue is a financial impact, not a physical asset.
• Cloud-based applications: These are primarily logical or information-processing assets, even though they depend on physical infrastructure.

• Generates a syslog message
• Shuts down the PoE port
• Places the port into error-disabled (err-disabled) state
• Frees the power allocation

• A device starting to draw power does not necessarily generate a syslog message.
• Monitoring does not pause data traffic while checking power.
• Drawing less than the configured minimum does not automatically mean the device has failed and should be disconnected.

• Separate accounts/domains create a strong administrative boundary between non-production and production.
• Separate projects provide distinct IAM boundaries, billing, quotas, service accounts, and resources.
• Developers can receive permissions in the development project without automatically gaining access to production.
• Production administrators can be restricted from development resources, supporting separation of duties and least privilege.

• A: Creates excessive project fragmentation without being required by the stated requirement.
• C: Keeps development and production under one account and does not clearly separate administrative duties.
• D: Uses one account and only two projects; it provides some project isolation but weaker organizational separation.

• Valor maior: mais aderência às instruções e aos detalhes descritos.
• Valor menor: mais liberdade criativa e resultados potencialmente mais variados.
• Valor excessivamente alto: pode causar artefatos ou imagens menos naturais.

• Aumentar o número de passos de geração: pode melhorar qualidade e refinamento, mas não é o principal controle de especificidade do prompt.
• MASK_IMAGE_BLACK: relaciona-se ao uso de máscara em geração ou edição de imagens, não à especificidade textual.
• Prompt strength: é mais associado à força do prompt em processos como image-to-image; nesta questão, o parâmetro diretamente ligado à aderência textual é o CFG scale.

• Batch processing, such as scheduled data transformations
• Streaming processing, such as continuously ingesting events

• Manipulating data with multiple languages: Mainly a benefit of Databricks and Spark.
• Real-time notebook collaboration: A workspace/notebook feature.
• Alerts for query failures: A Databricks SQL or job-monitoring feature.
• Distributing complex operations: Primarily a Spark compute capability.

• B. Data loss prevention (DLP): Helps prevent sensitive data from being copied, emailed, or exfiltrated. It is not the primary control for protecting a stolen laptop’s stored data.
• C. Operating system hardening: Reduces vulnerabilities by disabling unnecessary services and applying secure settings, but it does not necessarily protect the files if the disk is accessed directly.
• D. Boot security: Helps ensure the device starts only through trusted software or approved processes. It supports platform integrity but does not itself encrypt stored files.

• AWS Audit Manager continuously collects evidence from AWS services and helps assess whether workloads comply with regulatory frameworks and internal policies. It can produce audit-ready reports.
• AWS Config records resource configurations and evaluates them against compliance rules. For example, it can check whether encryption, logging, or access settings meet company requirements.

• Amazon Inspector identifies software vulnerabilities and unintended network exposure, not general policy or regulatory compliance.
• Amazon CloudWatch monitors metrics, logs, and operational events, but is not primarily a compliance assessment service.
• AWS CloudTrail records API activity for auditing and investigation. It supports compliance, but does not itself provide the structured compliance assessment capabilities of Audit Manager and Config.

• staff use the new system;
• transactions and reports are checked;
• problems are corrected;
• feedback is collected.

• Phased changeover: different parts or functions are introduced in stages, often according to a planned sequence.
• Pilot changeover: one representative department, branch or group acts as a test site before wider implementation.
• Parallel changeover: old and new systems operate at the same time.
• Direct changeover: the old system is stopped and the new one starts immediately.

1. Start with the Customer table.
2. Use Merge Queries and select the Address table.
3. Match Customer[Address ID] to Address[Address ID].
4. Use a Left Outer join so every customer is retained.
5. Expand only City, State/Region, and Country.

• Append adds rows vertically; it is for stacking similarly structured tables.
• Group By summarizes rows and does not retrieve address columns.
• Transpose swaps rows and columns and is unrelated to table relationships.

• D. Provide public endpoints to store and retrieve data

• E. Manage the infrastructure layer and the operating system

• Classifying data
• Configuring access permissions, such as IAM policies
• Selecting or configuring available encryption options, depending on the requirement

• ARP poisoning: Redirects or intercepts local network traffic; monitoring would typically show suspicious ARP changes or man-in-the-middle behavior.
• Jamming: Interferes with wireless or radio signals. It would affect connectivity, not usually show a server-specific overload.
• Kerberoasting: Attempts to obtain and crack Kerberos service-account hashes; it does not normally cause a system outage.

• Remote and global access: Employees can authenticate from anywhere, not just a specific location.
• Seamless login: The device can authenticate in the background, reducing repeated password or MFA prompts.
• Minimal equipment: It uses devices employees already have, rather than requiring separate hardware.

• Geotagging: Identifies location but is not a complete authentication method and can be spoofed.
• Smart cards: Can provide strong authentication, but require cards and often readers, adding equipment and user steps.
• Time-based logins: Restrict access by time but do not verify the user or device adequately.

• Regional leads — Customer Community Plus

• Capacity planners — External Identity

• Customer Community does not provide the enhanced reporting/dashboard access required by regional leads.
• An Identity license is generally for internal Salesforce identity use and does not fit the external capacity-planning users as well as External Identity.

• Snapshot: Captures a point-in-time state for rollback. It is not an independent running VM and does not protect against failure of the underlying host or storage.
• Convert to dynamic disks: Changes disk allocation behavior; it does not provide redundancy or high availability.
• P2V: Converts a physical machine into a virtual machine. That is a migration process, not an availability solution.

• Sending calls to available agents quickly
• Balancing interactions across agents
• Preventing calls from being handled manually one at a time

• Workforce Management: Forecasts demand and schedules enough staff; it supports wait-time reduction but does not directly distribute calls.
• Skill-based Routing: Routes calls based on agent skills and may improve the customer experience, but the question is asking about the core feature that distributes calls efficiently.
• IVR: Lets callers navigate menus and self-service options; it does not primarily assign calls to agents.

• A. Microsoft 365 group with Assigned membership
• C. Microsoft 365 group with Dynamic User membership

Why?

• Assigned membership: You explicitly add User1, User2, and User3.
• Dynamic User membership: Membership is automatically determined by a rule based on user attributes.

Why the other options are incorrect

• B and D: Security groups do not support the Microsoft 365 group expiration policy.
• E: Dynamic Device groups are intended for devices, not these users, and are also security groups.

• A. Implement retries with exponential backoff

• C. Reduce the frequency and/or size of requests

• B. Use PutRecord instead of PutRecords — PutRecord sends one record per call and does not remove the underlying throughput limitation. It may increase request overhead.
• D. Use Amazon SNS instead — SNS is not a direct fix for Kinesis shard throttling and changes the required streaming architecture.
• E. Reduce KCL consumers — KCL consumers read from Kinesis; they do not solve producer-side PutRecords throttling.

• A: Person Accounts cannot be merged directly with standard Contact records.
• C: There is no Account Setup option that automatically merges Person Account duplicates.
• D: Matching rules and duplicate rules can help identify or prevent duplicates, but they do not automatically merge Person Accounts. Also, relationship considerations do not change the basic merge capability.

• A vulnerability scanner automates discovery of known vulnerabilities and misconfigurations across systems. It can contribute to a supply-chain assessment.
• A penetration test actively attempts exploitation and is usually limited to an agreed scope.
• SCAP standardizes vulnerability and configuration assessment data; it is not the analysis itself.
• Illumination tool is not a commonly defined CompTIA Security+ term.

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

• Árvores de decisão: usam regras sequenciais, como “se característica X > valor, siga para este ramo”. São fáceis de visualizar e explicar. Atendem bem a problemas de classificação e regressão com alta interpretabilidade.

• Regressão linear: prevê um valor numérico contínuo, como preço, custo ou temperatura. Não é a escolha principal para classificar genes em categorias.

• Regressão logística: calcula a probabilidade de uma categoria. Pode atender à classificação, inclusive multiclasses, mas sua explicação costuma ser menos intuitiva que uma árvore para documentar decisões.

• Redes neurais: atendem a tarefas complexas, como imagens, texto e padrões não lineares. Porém, são menos interpretáveis, funcionando mais como uma “caixa-preta”.

• Data loss prevention (DLP): Helps detect or prevent unauthorized data transfers, but does not directly protect data on a stolen, powered-off laptop.
• Operating system hardening: Reduces vulnerabilities and attack surface, but does not adequately protect stored data if the device is stolen.
• Boot security: Helps prevent unauthorized operating systems or boot media from loading. It supports device security but is not the primary solution for protecting the data itself.

• Personally identifiable information (PII) detection

• Prompt Shields

• Self-harm content filtering addresses self-harm-related content.
• Violence content filtering addresses violent content.
• Neither protects customer PII or detects document-based prompt injection.

• 800 devices ? a scalable, centralized solution is needed.
• Four hardware/vendor classes ? the tool must handle different drivers and images.
• Two user groups ? it should allow different configurations for each group.
• “Distribute custom images” ? an imaging/deployment tool is required, not just a file-copy utility.

• Leadership and stakeholder commitment
• Business capability and skills
• Organizational culture
• Availability of resources
• Ability to manage and sustain change
• Impact of the proposed transformation

• How ready the organization is
• Which areas require urgent attention
• How difficult each issue may be to resolve
• Risks that could affect implementation

• A: Places the assessment in Phase B and refers vaguely to creating views; this is not the prescribed technique.
• B: An Implementation Factor Assessment and Deduction Matrix is not the primary TOGAF technique described for business transformation readiness.
• D: A Business Scenario helps identify requirements and stakeholder concerns, but it is not the main technique for assessing organizational readiness.